A07

• Input: Source artifacts, instruments, transformations, results, and revisions.
• Operation: Assign stable identifiers; freeze run inputs; record derivation and digest; append revisions with explicit supersession rather than silently replacing history.
• Output: Reproducible version graph and certified run manifest.
• Scope conditions: Versioned knowledge artifacts and evaluations where reconstruction matters.
• Failure conditions: Mutable files masquerade as immutable; links/digests are absent; supersession is incomplete.
• Predicted effect: Compared with ordinary versioned folders, impact analysis and exact-run reconstruction will succeed more often.
• Measurement: Reconstruction success, affected-record recall, and silent-divergence count.
• Implementation test: A new operator reconstructs a sampled run and identifies all descendants of a superseded record.
• Decision rights: Maintainer issues IDs; run operator freezes; owner declares supersession.
• Uncertainty handling: Missing lineage is explicit.
• Verification: Digest check and lineage traversal.
• Provenance: This is the core operation.
• Implementation cost: Registry and append discipline.
• Limitations: Current implementation violates aspiration. Direct: governance rules. Inference: comparative prediction.