Atlas node · Learning / Systems · active documentation system

machine-docs

Runbook and field-manual layer for shared fabrication tools, written so maintenance becomes teachable rather than hidden.

Repository →

What care leaves behind

machine-docs is a way of making maintenance visible after the person who knows the trick has left the room. It turns repair, setup, calibration, and caution into shared material instead of private memory.

A machine culture is shaped by what it writes down and what it lets stay unsaid. The runbook becomes a form of care when it lowers the cost of entering the tool, asking for help, and noticing risk before damage arrives.

Safety notes, fabrication pipelines, audit playbooks, and machine-care procedures make the work transferable. The documentation is not a wrapper around the practice; it is one of the practice's surfaces.

The claim is not full institutional coverage. It is a working argument for maintenance as curriculum, tied to the procedures and examples that can be publicly shown.

What it is

machine-docs is a documentation system for machine stewardship, safe operation, maintenance habits, and training pathways. It treats operational literacy as cultural and pedagogical work rather than background labor.

What it lets people do

It lets operators, learners, and maintainers enter shared fabrication tools through repeatable runbooks instead of rumor, memory, or gatekeeping.

What is public now

  • Project repo Current README, safety notes, fabrication pipelines, and audit playbooks.
  • Source evidence already surfaced The public repo already supports runbook and machine-care claims.

Evidence status

Status: active documentation system. Public source material is already strong, but the page still needs one current machine-care photo or calibration proof paired with the relevant runbook excerpt.

Next proof object: One redacted machine-care photo paired with the exact runbook or maintenance flow it belongs to.

What remains unresolved

  • The page should not imply full coverage of every machine or institutional approval.
  • A current public example would make the maintenance-as-curriculum claim more concrete.
  • Safety language should stay tied to documented procedure, not broad compliance claims.

Methods surfaced

Proof objects

  • Project repo documentation Status: public. README, safety notes, fabrication pipelines, and audit playbooks are already public.
  • Machine-care photo + runbook excerpt Status: needed. Still needed to show one current public example of maintenance-as-curriculum.
  • Syllabus A teaching-facing companion where prompts, policies, and examples need durable structure.
  • Memory Engine Helps scene systems stay explainable even when final images or polished docs are still missing.
  • repair-studio Pairs documentation practice with maintenance and care practice.

Source trail

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next

  • Open Syllabus — See the curriculum archive layer that shares its transfer goals.
  • Open systems-atlas — See how documentation practice becomes infrastructure method.