Documentation as Infrastructure
Clickable schema. Select any box to open a short case-study popup and implementation cues.
Tip: Use
Tab
to focus nodes,
Enter
to open,
Esc
to close.
One-page schema
Problem → Functions → Principles → Outcomes
Core Claim
Documentation is not a record of work.
It is infrastructure for judgment across time.
(click for examples)
When Absent
Infrastructural Functions
Design Principles
Hindsight distortion
Policy oscillation
Technical debt
Blame diffusion
Reasoning Externalization
Captures judgment while it is still forming
Preserves uncertainty, alternatives, assumptions
Temporal Bridging
Keeps decisions interpretable through turnover
Enables revision instead of oscillation
Traceability
Links outcomes back to the decisions that produced them
Prevents opaque accumulation of complexity
Accountability Without Dogma
Responsibility without requiring infallibility
Trust emerges from explainability over time
Document while reasoning is live
(not post-hoc)
Preserve judgment, not just output
Favor context over coherence
Treat records as living infrastructure
Documentation allows systems to argue with themselves over time (without relying on memory).
Popups are local to this file (no trackers, no external JS). You can customize the case list in the
CASE_DB
object.
Title
Subtitle
Close
What it means
Why it fails without docs
Case studies
Implementation cue