Why is this page running?

The chain

Running artifact

this pagebuilt 2026-08-30

Implementation mandate

M-0001 · BUILDBuild the Authority Trace

Authorised by

D-0001 · CONSTITUTIONALPublish the Authority Trace

Root source

FA-0.1Founding Authority 0.1

Decided by

foundera human, acting as founder-steward

Built by

claude-opus-5a replaceable agent, holding BUILD authority and no capability to publish

Deploy authority

not held by this mandatepublishing requires a separate mandate, so the thing that builds cannot release itself

Authority expires

2026-10-31T00:00:00Zafter which this mandate authorises nothing

What was checked — and what was not

One list. The articles a machine could not decide are not moved to a footnote, greyed out, or dropped. They carry the same weight as the ones that held, because the gap between what is written and what was verified is the honest part of this report.

• ● R-HUMAN-AUTHORITY ENFORCED

  held: Authority originates with founder, a human.

• ● R-SOURCE-HIERARCHY ENFORCED

  held: D-0001 (CONSTITUTIONAL) resolves to FA-0.1, which permits that class.

• ● R-TYPED-MANDATE ENFORCED

  held: M-0001 is a well-formed BUILD mandate under D-0001.

• ● R-TYPED-MANDATE/class ENFORCED

  held: BUILD is granted by D-0001.

• ● R-SOURCE-HIERARCHY/window ENFORCED

  held: Authority is current: 2026-08-30T00:00:00Z to 2026-10-31T00:00:00Z.

• ○ R-SCOPE ENFORCED

  open: The declared scope is coherent, but no changed paths were supplied, so nothing was evaluated against it. This is not a pass. Run with the working tree — `ours check M-0001 --changed` — to decide it.

• ● R-BUILD-DEPLOY ENFORCED

  held: BUILD authority does not carry release capability.

• ● R-ROLLBACK ENFORCED

  held: Reversal declared, with residue: None at build time. At release this changes: once the page is public anyone may have read it, and that cannot be undone. M-0001-RELEASE carries that residue.

• ● R-TRUTHFUL-STATUS ENFORCED

  held: States are distinct and recognised: authority DRAFT, decision DRAFT, mandate DRAFT.

• ● R-SOURCE-HIERARCHY/digest ENFORCED

  held: Every recorded source digest matches its file.

• ○ R-NO-FICTIONAL-OWNERSHIP CHECKED

  open: No public surface exists yet, so this check had nothing to scan. It becomes meaningful at M-0001, when the first page is published. Reporting it as PASS would claim a verification that did not run.

• ○ R-CHECKABLE-CLAIM INTERPRETED

  open: Whether every number, date and absolute quantifier in the sources is supported by what its source actually says. Provenance can be required structurally; accuracy is confirmed by a named human. No confirmer is recorded for this run.

• ○ R-SCOPE/runtime INTERPRETED

  open: Whether an implementation stayed inside its envelope at runtime. Kernel 0.1 validates the declared scope but does not sandbox execution, so the envelope is advisory to the agent rather than enforced.

• ○ R-WEAKEST-LAYER DECLARED

  open: Weakest real enforcement layer: AUTOMATED_GATE. Every gate above can be removed by the founder without notice, so no gate here is beyond one person's reach.

9 held 5 open — no machine can decide them 0 refused

There is deliberately no combined total. A single number would say the constitution was verified, when what was verified is the part of it a machine can decide.

Every article, and how it is actually held

The constitution requires that no article be untagged. ENFORCED means a check blocks the action. INTERPRETED means a named human decides. DECLARED means it is written down and nothing yet holds it.

What is not true yet

Stated here rather than left for someone to discover.

• There are no members. No membership has been issued, legally or otherwise. Nobody has ratified anything on this page.
• No member institution exists. Authority here is one person's, and the page says so at the top rather than in a footnote.
• Nothing here is beyond that person's reach. The weakest real enforcement layer is AUTOMATED_GATE — every check above runs in a pipeline the founder can delete without notice. It is not tamper-resistant and is not described as such.
• The scope envelope is advisory. The kernel validates what a mandate declares it may touch; it does not sandbox the agent that carries it out.
• Nobody outside this project has reviewed it. The comprehension review has not run. If five readers cannot answer who authorised this and how to reverse it, that is recorded as a failed test rather than as feedback.

Verify this without trusting us

The bundle embeds its own sources and their digests. The verifier re-derives every hash from those bytes and re-walks the chain. It needs no account, no network, and no copy of this repository — copy it to an empty directory and it still answers.

git clone https://github.com/radosukala/ours
cd ours && pnpm install

pnpm ours check M-0001      # re-run every check above
pnpm ours export M-0001     # write a self-contained bundle
pnpm ours verify exit/bundle-M-0001.json

Then break it. pnpm test runs the denial suite. Most of those tests are refusals, and each asserts the reason rather than merely the rejection — a test checking only that something failed would pass against a kernel that refused everything.

How to reverse it

Remove the route and the build output. No record the page reads is modified by this mandate.

What a reversal would not undo: None at build time. At release this changes: once the page is public anyone may have read it, and that cannot be undone. M-0001-RELEASE carries that residue.

A change that declares "revert the commit" while dropping data is making a false statement in a document whose purpose is truthfulness. So a destructive mandate that claims to leave nothing behind is refused by the kernel, not caught in review.