metadata-provides-extensible-lifecycle-governance
IN derived (depth 4)
Node metadata is simultaneously the universal extension mechanism for network state (carrying all structured lifecycle properties with consistent audit tracking) and the active governor of truth propagation behavior across both read and write paths — retracted and stale nodes are skipped in propagation and staleness checking respectively, driven by the same metadata fields.
Summary
Node metadata serves double duty in the system: it is the general-purpose store where all lifecycle information lives (retraction status, staleness, challenges, access controls), and it also actively controls how truth propagates through the network. When a node is retracted or stale, the same metadata fields that record that fact also cause the propagation engine to skip it, meaning the bookkeeping layer and the reasoning engine are tightly coupled through a single mechanism rather than maintained separately.
Justifications
SL — Metadata is not merely storage — it both defines extensible state and actively constrains system behavior, making it the unifying mechanism for state management and lifecycle governance.
Antecedents (all must be IN):
- network-state-is-extensible-and-consistently-tracked — Network state management is both extensible (metadata carries all lifecycle state — retraction flags, stale reasons, challenges, access tags, supersession — as a universal key-value mechanism) and consistently tracked (every mutation maintains the audit log and dependents index simultaneously), ensuring new state dimensions can be added without compromising existing consistency guarantees
- metadata-governs-lifecycle-across-read-and-write-paths — Node lifecycle state carried in metadata actively governs both mutation behavior (retracted nodes skipped during truth propagation, sticky retraction surviving recompute) and inspection behavior (staleness checking skips OUT nodes, compact surfaces stale reasons) — a single metadata mechanism controls the system's complete operational surface.
Dependents
These beliefs depend on this one:
- defeat-reversals-are-lifecycle-governed — All outlist-based defeat reversals (challenge, kill-switch, supersession) operate within metadata-enabled lifecycle governance — every reversal produces not just a truth-value change but a fully governed lifecycle transition with metadata-tracked state (retraction flags, stale reasons, access tags), ensuring reversals are first-class lifecycle events rather than bare truth flips.
- metadata-enables-lifecycle-governance-beyond-binary-truth — Node metadata enables lifecycle governance capabilities that transcend the binary IN/OUT truth model: extensible metadata provides structured lifecycle state (retraction flags, stale reasons, access tags, supersession markers) that actively governs both read and write paths, while staleness information is preserved and surfaced in compact output despite having no dedicated truth state in the TMS data model.