├── manifest.json obligation, period, counts ├── records/ sealed disclosure events ├── trajectory/ per-relationship summaries ├── certificates/ registry certificate IDs └── reconciliation.json bundle vs registry check
In build as part of the issuance path: a dated bundle of sealed records answering one obligation — reconciled against the registry so every record in it stays independently verifiable. Export to counsel, a regulator, or an insurer without a data-room excavation.
We do not certify compliance, and nothing here is legal advice. We make your compliance provable — by you.
The duty classes below recur across the companion-AI statutes (California, New York, Oregon, Washington). Each one reduces to a record type the chain already produces.
| Duty class | What you must prove | The records that prove it |
|---|---|---|
| AI-status disclosure | Shown, to this user, this session, before substantive interaction | Per-session sealed disclosure-event records, timestamped |
| Periodic re-notification | Cadence held across every long session | Session-cadence telemetry + sealed reminder-fired events |
| Crisis protocol operation | Detection ran; the referral actually fired, dated | Trigger-event + referral-delivery records, sealed at capture time |
| Referral reporting | The reported annual number is accurate | Append-only, de-identified referral ledger, registry-reconciled |
| Anti-dependency duties | A negative, proven over months | The per-relationship trajectory record — longitudinal, contemporaneous, typed |
| General defensibility | Reconstruct any user's disclosure/referral history, credibly | Sealed, third-party-verifiable records — dated at capture, not for litigation |
Duty classes are descriptive, not legal analysis. Obligations vary by statute and change; consult counsel for your obligations.