YaOS / Platform / Developer Experience / Coding Harness / Governance
Governance
Governance
How the harness is owned, released, reviewed and improved.
Ownership
The harness should have one named DRI, with contributors across engineering. “The AI team owns it” is too vague for something with organization-wide blast radius.
Release channels
| Channel | Use |
|---|---|
| dev | Active harness development and experimental adapters. |
| candidate | Validated release tested on pilot repos. |
| stable | Default for production engineering repositories. |
Cadence
| Every harness PR | Self-check + harness eval comparison. |
| Weekly | Review repeated agent/reviewer failures. |
| Fortnightly | Promote recurring issues into lint/rule/skill. |
| Monthly | Remove obsolete instructions; inspect context size. |
| Quarterly | Revalidate major agent adapters and current tool behavior. |