-
Notifications
You must be signed in to change notification settings - Fork 0
Conformance
spec/CONFORMANCE.md is the normative authority. This page is the orientation.
The specs use RFC 2119 / RFC 8174 keywords — MUST, SHOULD, MAY — in all capitals, so a claim can be checked rather than interpreted.
Every requirement has an identifier that must be cited when claiming or disputing conformance:
GTS-1.1 … GTS-1.5 task state
GPS-2.1 … GPS-2.5 permission
GOP-3.1 … GOP-3.5 orchestration
GOS-0.01 … GOS-0.17 constitutional laws
Within a major version these IDs are stable and their meaning never changes. Retired IDs are never reused.
| Level | Name | Requires |
|---|---|---|
| L1 | Core | all GTS-1 + GPS-2 — the minimum that prevents the worst failures |
| L2 | Full | L1 + all GOP-3 |
| L3 | Governed | L2 + GOS-0 (laws 01, 02, 15, 16, 17 minimum) |
An implementation that satisfies some requirements of a level must not claim that level. It may describe itself as partially conformant and enumerate what is unmet.
The suite runs 18 automated checks. It does not cover everything, and the spec says so explicitly:
-
✅ Machine-verified — deny-by-default, irreversible⇒human, append-only attempts,
done_whenenforcement, handoff notes, loop guard, honest failure, and more. -
⚠️ Attestation required — GTS-1.5 (external audit log), GPS-2.2 (call ordering), GPS-2.4 (audit completeness), GPS-2.5 (grant-editing path), and the GOS-0 organisational laws. These are properties of how you integrate, not provable by an in-process test. -
⚠️ Not yet automated — GOP-3.2 (routing by fit) and GOP-3.5 (human-visible close). Open items.
Claiming automated coverage the suite does not have would violate the project's own honest-failure law (GOS-0.16). The gaps are published deliberately.
Publish: the level, the spec version, your suite result, an attestation for every
"Acme Agents is Genesis Governance OS L2 (Full) conformant against CONFORMANCE 2.0. Automated: 18/18. Attested: GTS-1.5, GPS-2.2, GPS-2.4, GPS-2.5, GOP-3.5. Unmet: none."
Semantic versioning. A MINOR bump may add SHOULD/MAY requirements or new automated coverage. Adding a new MUST, or promoting a SHOULD to MUST, requires a MAJOR bump.
→ See also: Reference Implementation
Genesis Governance OS · an open standard for accountable multi-agent systems · GTS-1 GPS-2 GOP-3 GOS-0
Start
The standards
Verify
Project