Concept only · not implemented
Legal version management
A design sketch for admins. Version publishing is done by developers today; there is no admin tool yet.
Current draft versions
| Document | Version | Status |
|---|---|---|
| Terms of Service | 0.1.0-draft | Draft · awaiting counsel |
| Privacy Notice | 0.2.0-draft | Draft · awaiting counsel |
| AI Companion & Emotional Wellness Disclosure | 0.1.0-draft | Draft · awaiting counsel |
| Safety and Crisis Disclaimer | 0.1.0-draft | Draft · awaiting counsel |
| Electronic Signature Consent | 0.1.0-draft | Draft · awaiting counsel |
Proposed workflow
- Counsel drafts or edits a document; changes are classified as material or minor.
- An authorised admin publishes a new immutable version (material = new major number).
- Users who signed an older major version are asked to review and re-consent before continuing.
- Each acceptance is appended as a server-side consent event; prior events are never edited.
- Admins can retrieve a user's consent history under access control and retention policy.
Proposed consent_events fields: user_id, document_slug, document_version, signed_at (server UTC), choices, typed_name, minimal evidence metadata (no IP or device fingerprint unless counsel authorises). Built in this development copy: sign-in, append-only consent records with server time and account ID set by the database, immutable registered versions with SHA-256 content fingerprints, own-records retrieval. Not built: admin publishing tool, admin retrieval, retention policy.