Skip to main content
The employee schema workflow accepts structured_provenance, default false. Normal mode preserves all 172 rollback assertions and the qualification artifact. Diagnostic mode accepts only source 5c7c08e23a3d410bdbdc066f5c4dd2776fbeabd7. It binds the exact trusted control checkout, all five fixture hashes and the probe hash, applies the full frozen schema to an owned disposable database, and runs only the separate two-statement rollback probe. Original fixtures and assertions stay unchanged. The receipt contains SQLSTATE, fixed provenance categories, booleans and ordinals 22/23. Names resolve against the disposable catalog. Known categories additionally require an exact frozen private relation/constraint pair; unknown provenance remains redacted. Raw SQL, exception messages, details, context, row values and names are never published. Commands suppress raw database output and emit only parsed bounded records. Version 2 adds guardCategory. A known category requires SQLSTATE 23514, empty structured names, an exact whitelisted static message and the innermost matching function frame. Only the fixed category is published. Unknown or oversized diagnostics remain unclassified; contradictory serialized records are rejected. Catalog categories are unchanged. Empty structured names alone establish no catalog binding or particular guard origin. A guard category is a static source-signature match, not a catalog constraint or schema qualification. The probe checks its classifier with synthetic inputs inside the same rollback transaction before collecting the two actual records. Exact owned cleanup must succeed. The separate employee-provenance artifact is diagnostic evidence. Command success means two records and cleanup were collected; schemaQualified and assertionsQualified remain false. It establishes no 172 PASS, native/provider readiness, production application or delivery. Never retry old failed attempts; a new diagnostic requires reviewed new behavior and fresh exact control/source binding.