Skip to main content

Trust Lifecycle

The trust lifecycle spans creation, maturation, correction, consumption, and retirement of trust artifacts.

Lifecycle domains

Event lifecycle

StateDescriptionConsumer visibility
receivedAwaiting validationNone
acceptedPassed policy checksNone until materialized
materializedSignals writtenIndirect via scores
supersededReplaced by correctionUpdated outcomes only
retractedWithdrawn by producer/registryExcluded from new lookups
rejectedTerminal validation failureNone

Correction events link forward via corrects_event_id. Retraction events link via retracts_event_id.

Signal lifecycle

Signals become active when materialized from accepted events. Over time:

  1. Decay — influence weight diminishes per context policy (e.g., exponential half-life for repayment signals).
  2. Supersession — newer contradictory signals adjust polarity.
  3. Expiration — ephemeral signals (promotional badges) reach expires_at and leave active set.

The intelligence engine MUST recompute scores when signal state changes.

Context score lifecycle

Context scores are derived artifacts, not source records:

PhaseBehavior
BootstrapThin-data band until minimum signal threshold
ActiveRegular refresh on new events
StaleFlagged when no fresh signals within context TTL
SuppressedSubject or registry blocks consumer visibility

Report lifecycle

PhaseDurationNotes
GeneratedPoint-in-time snapshotIncludes generated_at
VerifiableDefault 90 daysVerify URI confirms integrity
ExpiredAfter TTLReturns PTI-4042 on verify

Consumers SHOULD NOT treat expired reports as current truth without regeneration.

Identity lifecycle

  • Merged identities redirect all lookups to survivor pti_id.
  • Erased identities trigger cascade deletion per governance policy.

Consent grants bind consumer, context, and purpose. Withdrawal suppresses restricted fields on subsequent lookups within policy SLA (typically 24 hours).

Operational SLAs (informative defaults)

TransitionTarget SLA
Event → materialized signal< 5 minutes (async)
Retraction → lookup exclusion< 1 hour
Erasure → lookup block< 24 hours
Score refresh after materialization< 15 minutes