Before
Authority precedes action
Consequential permission must already exist outside the worker seeking to act.
Constitutional rule
Governance · public overview
Decide before.Bound during. Prove after.
ANANS separates capability from consequential permission. Authority comes from outside the worker seeking to act; ambiguous or missing authority does not become permission; released claims leave evidence that can be inspected afterwards.
01 / Core rule
Ability is not permission. Success is not authority.
02 / Principles
Govern the authority boundary, not the model’s confidence.
A stronger model, a successful prior run, or a compelling rationale cannot manufacture consequential permission.
During
Ambiguity fails closed
Missing, expired, or out-of-scope authority produces refusal rather than silent widening.
Bounded principle
After
Evidence survives the decision
Released governance claims include reviewable evidence sufficient to inspect the admitted claim.
Public proof exists
03 / Public relation
The worker remains downstream of purpose and permission.
The public model is deliberately minimal.
EXTERNAL PURPOSE + CONSEQUENTIAL AUTHORITY
↓
GOVERNANCE DECISION
↓
BOUNDED ACTION
OR REFUSAL
↓
REVIEWABLE EVIDENCE
CAPABILITY != AUTHORITY
REFUSAL IS A VALID OUTCOME04 / Released evidence
Public verification is release-specific.
The current containment-proof repository publishes a bounded released claim and the evidence required to inspect it. A released proof does not turn the public repository into a specification for unreleased ANANS machinery.
Claim
Narrow and versioned
The current release is tied to a specific bounded claim and version.
Verifier
Minimum necessary surface
The verifier exists to reproduce the released claim, not to disclose future proof-development strategy.
Non-claims
Bound the interpretation
The release explicitly excludes broader conclusions not supported by its evidence.
05 / Disclosure boundary
Public evidence is not public development.
ANANS publishes what is necessary to inspect an admitted public claim. Unreleased implementation details, internal test strategy, development artifacts, credentials, and non-public project material remain private by default.
- Public proof repositories are evidence membranes, not development workspaces.
- A future proof is not described publicly before its evidence and disclosure gate are earned.
- Public release material should minimize unnecessary reconstruction or substitution of unreleased implementation.
- Nothing on this page grants execution, deployment, spending, or publication authority.
06 / Non-claims
Governance evidence is not production certification.
The public claim remains bounded to the released evidence.
- ANANS is not represented here as production-ready.
- The public proof does not establish non-bypassability of every private execution path.
- Local validation does not establish unattended production reliability.
- The governance layer does not authorize itself or grant workers new consequential permissions.
07 / Contact