A.3 Auditable Transformation

A.3.1 The Capability

Make consequential transformations reconstructable and detect silent loss. Record who changed what, then verify that the transformed artifact retained the required semantics.

A.3.2 When This Stack Earns Its Keep

Reach for it where:

A.3.3 The Composition

The Auditable-Transformation stack: a sanctioned mutation is marked, recorded, covered, read back, and gated on fidelity A single solid load-bearing chain runs top to bottom. A sanctioned mutation enters. MARK attaches actor and action. EMIT persists a structured record. COVER detects any mutation that escaped attribution. READ reconstructs the transformation history. The FIDELITY GATE checks that the transformed artifact retained its required semantics. Every link is required: attribution without completeness is a partial history, completeness without readable provenance proves only that records exist, and provenance alone cannot show the product survived. No dashed enhancement in this stack. SANCTIONED MUTATION MARK actor · action EMIT persist a structured record COVER every mutation accounted for? READ reconstruct history FIDELITY GATE did semantics survive? load-bearing (required) the full chain is required Solid path: the load-bearing composition. This joins causal legibility to product fidelity — broader than logging.
Figure A.3-1. The auditable-transformation composition. A sanctioned mutation flows through MARK (attach actor and action) to EMIT (persist a structured record); COVER detects any mutation that escaped attribution; READ reconstructs the transformation history from the records; a FIDELITY GATE checks that the transformed artifact kept its required semantics. Solid path: the load-bearing composition.

A.3.4 Constituent Moves

Table A.3-1.
MoveRole
MARKAttach identity and context to the mutation.
EMITPersist a structured record.
COVERDetect mutations that escaped attribution.
READReconstruct the transformation history.
FIDELITYCheck that the transformed artifact retained its required semantics.

A.3.5 Why These Travel Together

Attribution without completeness produces a persuasive but partial history—convincing exactly where it is silent. Completeness without readable provenance proves only that records exist. And provenance alone cannot establish that a transformation preserved the product.

The stack must therefore establish both causal history and product fidelity: How did this artifact reach its current state, and did the transformation preserve its required semantics?

Mechanisms: provenance stamping · attribution coverage · fidelity gate

© James C. Davis, 2026–present