- Home
- Maintain and repair
Domain ExpertIntegrator
Planned
Service framework
Keep evidence with every maintenance action
Separate symptoms from causes, preserve configuration state and verify the robot before returning it to use.

Maintenance workflow
Inspect→Capture evidence→Isolate→Repair or update→Verify→Record
| Area | Purpose | Start here |
|---|---|---|
| Routine maintenance | Detect wear, looseness, contamination and drift before failure | Routine maintenance |
| Diagnosis | Read states and logs, reproduce symptoms and isolate one subsystem | Diagnosis |
| Common faults | Follow evidence-led triage by subsystem | Common faults |
| Repair | Restore a known configuration with appropriate parts and records | Repair |
| Updates | Apply versioned software or firmware with a tested rollback | Updates |
Before service, make the robot safe against unintended motion and stored energy. After service, repeat the affected acceptance checks and record parts, revisions, commits, configuration changes and results.
Current scope
These pages define the documentation and verification structure. Procedures remain planned until tested against an identified hardware revision and release.