Method note

Assumption Ledger

An assumption ledger names what a system is relying on before those dependencies disappear into habit. It keeps technical, ethical, and pedagogical claims from hardening into invisible facts.

Typical ledger questions

• What has actually been measured, and what is only expected?
• What conditions would break this claim?
• What requires a more careful public boundary because people, rooms, or private infrastructure are involved?
• What proof object would move this from promising to field-tested?

Where it matters in the fleet

• MOARkNOBS-42 uses it to separate bench-tested control behavior from broader reliability claims.
• Human-Buffer uses it to keep perception, bias, retention, and refusal visible.
• homeauto and systems-atlas need it because private topology should never be mistaken for public method.

Public rule

When uncertainty matters, name it. Hidden dependencies make projects look stronger than they are and harder for others to learn from safely.