Specifications
Status: Accepted · Version: 0.1 · Stage 0
These documents are the normative product contract. An earlier sketch used a shorter list (onboarding through audit log). This catalogue replaces that sketch.
| ID | Document | Decides |
|---|---|---|
| TITIP-001 | Product principles | The five rules every repository must follow |
| TITIP-002 | User and identity | Account, session, and what “the owner” means |
| TITIP-003 | Trusted contacts | Invitation, acceptance, verification, removal |
| TITIP-004 | Asset inventory | What may be recorded, and the category list |
| TITIP-005 | Vaults | Lifecycle, recipient scope, prohibited payloads |
| TITIP-006 | Life check | Presence cycle and the meaning of inactive |
| TITIP-007 | Escalation | State machine, reminders, grace, return to active |
| TITIP-008 | Release policy | Evidence, candidates, holds, simulation vs real |
| TITIP-009 | Recipient verification | Identity, disclosure, scoped access, expiry |
| TITIP-010 | Audit trail | Which mutations must be explainable |
| TITIP-011 | Privacy and deletion | Collection, purpose, deletion, residency intent |
| TITIP-012 | AI assistance | Preparation only; prohibited decisions and inputs |
Prototype use cases UC-01 through UC-06 are in plans/prototype.md. They exercise these specs. They do not weaken them.
Normative language
- Must / must not: binding. Runtime behaviour that conflicts is a defect.
- Should: binding unless a spec records an exception.
- May: optional.
Undefined behaviour is not an invitation for a repository to choose. Open the question here first.