Method note

Documentation as Interface

Documentation is not only what remains after the work. In this practice, it is one of the interfaces people use to enter, operate, repair, refuse, or inherit a system.

What documentation carries here

• Operating steps, failure recovery, and maintenance habits.
• Consent language, retention boundaries, and refusal paths.
• Teaching transfer: how a tool, scene, or lesson survives beyond one operator.
• Source trails showing where the live implementation truth actually lives.

Projects that surface the method

• machine-docs turns machine care into a public runbook and teaching object.
• live-rig treats setup and recovery as part of the scene system, not backstage residue.
• Syllabus keeps prompts, policies, and pathway structure portable across courses and workshops.
• Human-Buffer makes consent and privacy legible through workshop materials and interface logic.

Reader path

When an Atlas page says a repo is the source of truth, that is part of the interface too. The public site carries claims and proof objects. The repo carries the live build details.