This document defines how TSMM treats lifecycle state, because trust systems do not live in a magical present tense.
| Stage | Description |
|---|---|
| Issuance or onboarding | Authority, artifact, or profile enters valid circulation |
| Delegation | Authority is granted or propagated within defined bounds |
| Activation | A previously staged object becomes usable |
| Suspension | Temporary restriction is applied pending review or remediation |
| Revocation | Validity is withdrawn |
| Expiry | Validity ends due to time bounds |
| Remediation | Defects are corrected and posture is re-evaluated |
| Archival | Object is retained for record, audit, or evidence purposes |
Lifecycle events may apply to:
Delegation should not be treated as permanent inheritance. It should remain bounded by scope, purpose, policy, and revocation conditions.
Suspension is useful when a system has reason to doubt current posture but lacks enough information for permanent revocation.
Revocation should change what effects the system allows. A revoked authority that still produces live effects is a zombie credential problem.
Remediation should be modeled explicitly because many trust failures are corrected rather than terminal.
Issue artifact -> delegate authority -> verify state -> allow effect
| |
| v
| suspend authority
v |
detect defect -> remediate -> reassess -> restore bounded effect
model/lifecycle/trust-object-lifecycle.yamlschemas/tsmm-lifecycle.schema.json