YaOS / Platform / Developer Experience / Coding Harness / Architecture
Architecture
Architecture
How the human-facing YaOS docs, machine-facing harness and repository adapters fit together.
Engineering Docs (HTML)
│ explains
▼
YaOS Coding Harness (Git)
│ syncs / distributes
▼
Project Repository + .harness/project.yaml
│ instructs
▼
Claude / Codex / Antigravity / Cursor / Copilot
│ validated by
▼
Hooks + Tests + CI + Evals
Human vs machine content
| Layer | Format | Purpose |
|---|---|---|
| YaOS docs | HTML | Explain concepts, onboarding, governance and operating model. |
| Project configuration | YAML | Declare profiles, commands, risk and protected paths. |
| Agent contract/rules/skills | Markdown + scripts | Machine-consumed instructions and procedures. |
| Enforcement | Code/config | Deterministic lint, type, architecture, security and test gates. |
Context loading model
Always loaded: compact operating contract
↓
Repository map + project.yaml
↓
Path/profile rules only when relevant
↓
Skills only when a task needs them
↓
ADRs / references only for a decision
↓
CI and linters consume zero prompt tokens