GovernedAI
Verifiable evidence for agentic AI execution · sealed receipts only.
Public Ledger

How this publication is governed

A publication that defines the operating doctrine for governed AI decisions must itself be governed by the same doctrine. This page is that recursion made explicit.

Constitutional principle

Recursive doctrine: the publication that governs AI decisions is itself governed by the doctrine it publishes. Every claim on this site that lives long enough to matter will produce a receipt that survives it.

Council operating model

This publication operates under OptimaX AI Governance v2.2, sealed 2026-03-31. The review model separates drafting, adversarial review, audit, research, and authorization responsibilities. Public pages describe the control objective; role internals remain counsel-vetted.

The hardest invariant: review authority is separated from deployment authority. Public claims are published only when the evidence path can be inspected without exposing private implementation detail.

How a claim becomes a published page

  1. Builder draft. The Builder produces a draft using the prompt-OS (versioned, signed, schema-bound prompts) under a session anchor that names role, invariants, disclosure tier, and forbidden behaviors.
  2. Adversary pass. The Adversary attempts to break the claim — find the most credible reason it is wrong, the cleanest factual error, the most quotable embarrassment.
  3. Auditor review. The Auditor (separate model, separate context) reviews against full document parity. Findings are recorded with severity P0–P3.
  4. Sovereign sign. The Sovereign reads, signs, and authorizes. Sealed RFCs are version-bumped.
  5. Disclosure-tier check. The build pipeline refuses to publish a Tier 1+ phrase on a Tier 0 page, atomically.
  6. Receipt. An RDL entry is logged before the artifact ships. Tree hash is computed.

Disclosure governance

Three disclosure tiers govern what appears where:

TierAudienceWhat appears
Tier 0Public — this siteCategory language, architectural framing, doctrine, conformance results, contestation procedure
Tier 1Strategic counterparties under mutual NDAArchitectural summary at higher resolution; reference documents under counsel sign-off
Tier 2Pilot-LOI counterpartiesImplementation specifics, integration interfaces, source review
Tier 3Sealed integration partnersFull system access under signed master agreement

The disclosure-tier rendering contract is software-enforced. Tier 1+ phrases (specific cryptographic constructions, restricted implementation details, threshold values, claim-bearing patent language) cannot publish to Tier 0 routes. The build fails atomically. Sovereign override is a first-class, logged, expiring event.

Amendment process

This publication's governance is itself amendable. Doctrine changes follow Decision Class D3:

Builder draft → Auditor adversarial review with full document parity → Adversary break-attempt → Sovereign sign → version bump → ratification at quarterly review. The most recent amendment is the Document-Parity Rule, proposed 2026-05-01 after a detected review-coverage gap and scheduled for ratification into AI Governance v2.3 at the 2026-06-30 quarterly review.

Contestation

Anyone can contest a published claim, registry entry, or conformance score. Routing: contest@governedai.ai. See the corrections policy.

Agreement is not validation
Tier 0 · RDL-012 · 2026-05-13 No receipt, no governed decision.
Sealed RDL-012 · 2026-05-13