world-model-ledger
world-model-ledger
The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY in this skill are to be interpreted as described in BCP 14 (RFC 2119, RFC 8174) when, and only when, they appear in all capitals.
A persistent world model for a coding agent, backed by SQLite. It records what the agent learns about a codebase — entities (symbols / files / modules / real-world referents), the interactions between them, and the constraints that should hold — and, for every interaction and constraint, how sure we are it exists, how sure we are it is correct, whether it has been validated, and what evidence backs it.
The defining rule, enforced as an invariant: code-observed relationships are not ground
truth. A file sighting can drive observed_conf to 1.0 while normative_conf stays 0 and
status stays unverified. Only oracle evidence — a passing test, CI, a doc, a human — raises
normative confidence. See references/confidence-model.md for the epistemics and
references/schema.md for the data model. The design rationale is in
docs/superpowers/specs/2026-07-01-world-model-ledger-design.md.