For CHROs · Confidential memory
The people office, with memory it can defend.
Compensation history, succession context, sensitive conversations, and confidential commitments — held in tenant-isolated executive memory, role-scoped, never used for shared training.
The shift
From firefight to operating rhythm.
Two columns. Left: the day the role runs today. Right: the day Helm Office runs for the role.
Where the office strains
Drag- Comp decisions made over months reconstructed from a thread and a memory.
- Succession context lives with one or two people; loss is a single point of failure.
- Sensitive conversations with the principal sit in personal notes apps.
- Investigations and exits create paper trails that are never quite complete.
- DEI commitments tracked in a deck no one updates after Q1.
The people office on Helm
Cadence- Atlas holds comp history, succession plans, and sensitive context — role-scoped, audit-visible to the CHRO only.
- Verdict captures rationale for hires, exits, and comp moves at the moment they're made.
- Signal drafts sensitive replies in your voice; nothing leaves without approval.
- Ledger tracks people commitments to closure — review cycles, promotions, retention plans.
- Beacon delivers a confidential CHRO briefing the morning before the board people committee.
Sample artifact
A succession note, held only for the CHRO.
Atlas memory is role-scoped: only the CHRO and explicitly shared co-pilots can read this entry. The audit log records every access.
Succession brief — VP Finance bench
Atlas · restricted · CHRO onlySnapshot
Confidential commitments
Access trail
Closing recommendation
The CHRO stack
Where confidential people work belongs.
A short list, not the full catalog. The modules this role will actually open every day.
Atlas
Role-scoped memory for succession, comp history, sensitive context, and prior conversations.
Verdict
Decision log for hires, exits, comp moves — rationale captured at the moment.
Signal
Drafts sensitive replies in your voice. Sends require explicit CHRO approval.
Ledger
People commitments tracked to closure — promotions, reviews, retention plans.
Beacon
Confidential CHRO briefing before people committee and board people sessions.
Security posture
Tenant isolation, encrypted tokens, no shared model training, full audit log.
What people and legal will ask
The procurement conversation for the people office.
Who in my org can read confidential people entries?
+
Only the role you assign. Sensitive memory is restricted to the CHRO unless explicitly shared with a chief of staff or assistant. Every access is logged.
Is anything from Helm used to train shared AI models?
+
No. Customer data is not used to train shared models. Ever. Per-workspace data encryption keys keep tenants strictly isolated.
Can we route confidential PHI or regulated employee health data through Helm?
+
Not today. Helm Office is not HIPAA-eligible and does not currently offer a BAA. We will not market as HIPAA-eligible before that work is complete.
What happens on offboarding?
+
Workspace deletion triggers a 30-day soft-delete window followed by full erasure across primary and backup stores. Token revocation propagates to the connected provider in one click.
For the people office