Governance Responsibility Matrix
Purpose
This matrix prevents standards from overlapping in confusing or harmful ways. When two standards seem relevant, use this file to decide which one owns the decision.
Ownership
| Question | Owning standard | Supporting standards |
|---|---|---|
| Where does this live in the workspace? | WGS | PPS, SFDS |
| Should this project exist, and what is success? | PPS | WGS |
| How is a standard written and matured? | SFDS | WGS |
| How is a desktop application released? | DRS | PPS, ARHS, AAMHS, NeonInk |
| How should a CLI behave in automation? | CTS | PPS, ARHS, AAMHS |
| How should a local service or workspace infrastructure component run? | SIS | WGS, PPS, CTS, AAMHS |
| How is a website documented and deployed? | WDS | NeonInk, PPS |
| How is a dataset described and validated? | DDS | AAMHS, ARHS, AAS |
| How is an agent task recorded or handed off? | ATS | WGS |
| How is an evaluation run recorded? | AAS | DDS, ATS |
| What hashes must accompany a release artifact? | ARHS | DRS, CTS, SIS, WDS, DDS |
| How is archive preservation integrity proven? | AAMHS | DDS, DRS, CTS, SIS, ARHS |
| How is semantic UI language expressed? | NeonInk | WDS, DRS, SESM |
| How is SVG metadata embedded and validated? | SESM | NeonInk, AAMHS |
| How are application-as-data records represented? | AADR | SFDS, WGS |
Collision Rules
- WGS owns location and registration, not the internal rules of every project.
- SFDS owns the shape of standards, not the domain policy inside each standard.
- PPS owns project intent before implementation, not release readiness.
- DRS, CTS, SIS, WDS, and DDS own project-class delivery rules.
- ARHS owns minimum release-artifact hash requirements; it does not replace release, deployment, dataset, or archive readiness standards.
- AAMHS owns archive preservation integrity records; it may include ARHS hashes but adds preservation manifests, validation records, signature policy, and known gaps.
- NeonInk can support any visual interface, but it does not decide release, deployment, or workspace policy.
- ATS records agent work; it does not decide project scope.
- AAS records analysis credibility; it does not replace DDS provenance, ATS task history, or the decision standard that uses the analysis.
Tone Rule
When in doubt, prefer the standard that reduces ambiguity for the next maintainer. The point is not to win jurisdiction. The point is to leave fewer mysteries behind.
:::note Cross-references This matrix names PPS, DRS, CTS, SIS, WDS, DDS, ATS, AAS, ARHS, AAMHS, NeonInk, SESM, and AADR. Only WGS (position 10) and SFDS (position 11) have been built out as documentation slices so far; the rest are left as plain standard-name references pending their own documentation passes. :::