Evidence record
Multi-agent operations architecture
Every published claim on this page was checked by running the command shown. Claims that did not pass were withdrawn before publication; their count is stated below and the full record is available on request.
Measured 2026-08-23 · figures expire with the next publish run; the site is rebuilt from one figures ledger.
Research artifact · published claims
| Claim | How it was checked | Status |
|---|---|---|
| The roster is 8 charter files covering 7 distinct seats, with 1 retired role kept in the archive — one role carries two profiles, which is why 8 files map to 7 seats. Together they run to 1,231 lines and 134,477 bytes, and every data-office seat carries an identical section headed "Closing a task (MANDATORY, tool-enforced)". | ls -1 <roster>/*.md | wc -l → 8 ; grep -h '^name:' <roster>/*.md | grep -v '{{' | sort -u | wc -l → 8 declared names, two of which name the same role (a full role card and a lighter orchestrator card) → 7 distinct seats ; ls -1 <roster>/_archive/ → 1 retired role, date in the filename ; cat <roster>/*.md | wc -lc → 1231 134477 ; grep -nE '^#{1,3} ' over the data-office charters → the same spine in each | published |
| Written doctrine is 16 operating rules held in the operating memory, inside an index of 37 entries — 16 rules, 14 project-state records, 6 references and the standing brief. Three of the sixteen have mechanical enforcement; the rest are conventions that depend on being read at session start. | ls -1 <memory>/feedback_*.md | wc -l → 16 ; ls -1 <memory>/reference_*.md | wc -l → 6 ; ls -1 <memory>/project_*.md | wc -l → 14 ; grep -cE '^- \[' <memory>/index → 37 | published |
| The publish pipeline is 6 stages, each with one writable root, and a hard tool-call cap on the five worker stages — audit 40, fix 60, secure 15, package 40, verify 50 — for 205 calls allocated per project before the work starts, under an execution plan carrying 9 non-negotiable guardrails and a stop rule that freezes a project after two consecutive verify failures. | sed -n '/Per-project pipeline/,/Stop rule/p' <plan> → the six stages with scope, cap and gate ; grep -cE '^[0-9]+\. ' over the guardrails section → 9 | published |
| The written identity policy runs to 8 sections and defines the forbidden identifier classes; the gate turns it into machine work — 43 denylist patterns across 5 categories (11 topology, 5 identity, 16 content-legal, 6 disclosure, 5 tone), run as one of 7 checks that must all exit 0 before anything leaves the clean-room. | grep -cE '^## ' <policy> → 8 ; grep -oE 'def check_[a-z_]+' <the gate program> | sort -u | wc -l → 7 ; AST count over every pattern list in the gate's pattern module → 11 / 5 / 16 / 6 / 5 = 43 | published |
| The gate was tested before it was trusted: a fixture seeded with deliberate leaks returned 0 pass / 6 fail against the six checks the gate carried that morning, with every seeded item named by category, and a clean fixture returned 6 pass / 0 fail, exit 0. The self-test also re-verified the fix for 2 defects in the gate itself — a silent skip when one scanner was absent, and a skip-not-fail mode — one turned into a hard failure and one forced to run rather than skip, both re-verified. | grep -nE 'RESULT: (PASS|FAIL)' <the gate self-test record> → dirty fixture FAIL 0/6 ; clean fixture PASS 6/0 ; sections 3 and 4 record the two gate defects and their re-verification, section 5 the path that still warns rather than fails | published |
| The verifier failed its own author. On the first case study of the publish week it returned a verdict of FAIL — 6 claim-level mismatches and 2 imprecisions, including a handler count that appeared four times in published copy and was wrong by three, and the finding that the audit stage's own stated counting command did not reproduce the audit stage's own number. | sed -n '1,40p' <the verifier's verdict record> → VERDICT: FAIL ; build PASS ; gate FAIL 4/2 ; identity PASS ; style PASS ; claim-by-claim FAIL — 6 mismatches, 2 imprecisions | published |
| The same standard is applied to the estate's own published packages rather than reporting a clean sheet: the day's end-to-end harness reads 15 pass / 1 fail, and three of those rows are fresh installs of the published releases, each installed from the index and then run — those three pass; the one failure is the harness's check that the version the published site states for one package matches the index, because the live site predates this run, and it is published as it stands. | the end-to-end harness record for 2026-08-23, run of 18:59 → 15 pass / 1 fail, its three fresh-install rows passing against the published releases; the harness keeps one record per date and overwrites it, so the figure quoted is that date's record as it stands, at the timestamp its own header carries | published |
| The recon that produced this week's plan ran as 10 parallel read-only investigations — 7 audit seats plus 3 planning lenses — feeding one orchestrator. | the plan's verified-facts section names the 7 read-only audit seats and the 3 planning lenses | published |
12 claims tested · 8 published · 4 withdrawn before publication. Full evidence record available on request — king.hippopotamus@yahoo.com.
Author approval — 2026-08-23, hash 4ff473a2