0-3-3-understand-committed-data

name	0.3.3-understand-committed_data
description	[0.3.3] database state resulting from successfully completed transactions; constitutes the visible universe for read_c

understand-committed_data

CALL NUMBER: deep_isolation_level.committed_data DEFINITION: database state resulting from successfully completed transactions; constitutes the visible universe for read_committed queries

Invoke this skill to understand committed_data down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP/SWI-Prolog consistency gate): every reference below resolves.

THE RELATIVE ROOT (the import cone, by lib)

CONSUMERS (what needs this)

commit_visibility_boundary, committed, read_committed, write_lock_held_until_commit

---

Projected from the database transaction isolation and concurrency control KB (217 concepts / 124 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.

(leaf — this is an actual skill.)