machine-docs

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

• Documentation as Interface This project is one of the clearest embodiments of the method.
• Evidence Before Polish A maintenance photo plus runbook excerpt can do more than a polished summary.

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.

Related Fleet Projects

• 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

• Project repo — Implementation truth.
• Legacy note — Short lineage marker.
• Last reviewed: 2026-05-15

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.