[Deicyde]

Release-affecting (per site/ops/brain_release_authority.py): ships only through the Brain release and promotion path. Files: AGENTS.md, CONTRIBUTING.md. Every other file in this PR is release-neutral. AGENTS.md and CONTRIBUTING.md are currently classed release-affecting by site/ops/brain_release_authority.py; a separate PR makes them neutral. Nothing in wiki/src, wiki/scripts, site or brain reads either file, and this PR changes no Worker, asset or release bytes.

Problem

Production has served an immutable Brain release since 2026-10-04, but every status doc still says it isn't deployed, and nothing in Git records the promotion.

• Live selector: https://wikilean.jackmccarthy.org/assets/brain/current.json names release sha256:8305822b0083…, manifest fa645b2ba956…, audited_at 2026-10-04T17:25:04Z, with no previous_* fields. The manifest's release.json gives profile brain-offline-replay-v1, authority commit 2eb31baa (the PR Unblock finalize and P1B: coverage checker, semantic-diff evidence cap, activation CI git shim, promoter toolchain #43 merge), and offline pack sha256:294b1fc7….
• On main 37b7036d, README.md:7-16 says the stack "remains inactive in production" and that current.json returns 404, and its four-facts table (README.md:107-112) says No / No / No. docs/ROADMAP.md:160-175 (queue "updated 2026-09-26") says the selector is absent; P1A is "NOT ACTIVATED" (:232) and P1B "NO PRODUCTION" (:279). docs/BRAIN-RELEASE-RUNBOOK.md:3-5 and :471 say activation is blocked, and :341 still shows the first-activation form, which now fails on purpose. docs/BRAIN-SQLITE-HANDOFF.md:3 points at the 2026-09-19 checkpoint.
• The canary failure, the attempt 20261004T172504Z-8305822b0083-27c7c461cb (journaled manual_intervention_required, reconciled 2026-10-08), and the rollback situation are not recorded in Git; the first two appear only in PR Canary: never advertise text/html, so Cloudflare's HTML rewrites cannot break the frozen-bytes check #44's body. git grep -E '8305822b|fa645b2b|294b1fc7' 37b7036d finds nothing.
• CLAUDE.md:61 and wiki/README.md:141 list plain npm run deploy as the deploy command. With assets.directory ./public (wiki/wrangler.jsonc:8-9), that replaces the live selector and the whole asset tree.
• Other stale facts: the ROADMAP status log ends at 2026-08-06. The P2 propose-then-approve box is unchecked although docs/propose-then-approve.md:3 says "FULLY LIVE (2026-08-06)", and the revisions-migration box is unchecked although wiki/migrations/0004_p1_loop.sql:47-49 shipped it. ROADMAP.md:927 says 87 CI commands, but scripts/ci-python.sh has 90 run_check lines. README.md:137 and CONTRIBUTING.md:140 ask readers to vote on a proposal that became Wikidata property P14534 on 2026-06-17. README.md:30 links site/out_w3c/, which is gitignored and not published (/out_w3c/ returns 404). CLAUDE.md:133-134 points Lean work at wikifunctions/lean/, which doesn't exist. HANDOFF.md:18-22 describes memory notes the memory directory doesn't hold. docs/research-plan.md:20,23 still lists pipeline_runs and /stats as unbuilt.
• Mission operations: across all 778 /<slug>/history pages, the newest ai-moderate:review revision is from 2026-09-17 09:05 UTC, while wp-update re-pins keep posting daily through 2026-10-13. /stats still shows 7 new runs in total, and the last ai-create revision is from 2026-07-03.

Change

• New docs/BRAIN-ACTIVATION-2026-10-04.md. It holds publicly checkable facts plus the journal's reconciliation record: the selector and release.json identity fields, a timeline, the Web Analytics canary failure and PR Canary: never advertise text/html, so Cloudflare's HTML rewrites cannot break the frozen-bytes check #44's fix, the attempt and its 2026-10-08 reconciliation (journal final_state deployed_reconciled, Worker deployment 499ba4bf…, version 63b11a7e…) with the reconcile caveat for future attempts, rollback (no previous_*, so Cloudflare deployment history is the version source, and the release canary can't verify a rollback to the pre-selector Worker), and the constraints from PR Releases survive release-neutral merges to main; pin-only edge diffs aggregate (semantic-diff/v3) #45's release-neutral rule (no reviewed main can re-promote this release, so any future promotion needs a new build; the bundle verifies only with 2eb31baa's tooling; every Worker change needs a new release; no plain npm run deploy). It ends with an Operator must fill table for the values only the journal holds; host, receipt-root and backup details stay in the private journal.
• README. The status section is now dated October 2026. It says the release has been live since 2026-10-04 and its attempt was reconciled on 2026-10-08, gives 2026-10-13 numbers (778 articles, 37,936 statements, 27.9% formalized, 14.1% partial) with links to /about and /stats, records P14534's creation date, fixes the W3C/RDF links, and corrects the four-facts table.
• ROADMAP. A "Waiting on Jack" list at the top: decisions only, each with evidence and options, no recommendations. The Brain queue is updated. In P1B, the bundle-step boxes are checked for release A, because the promoter at 2eb31baa refuses --execute without a verified activation bundle. The host-context authorization and provisioning boxes, and P1C's approval box, stay open with a "pending the journal" note, since the promotion alone doesn't show what was approved. P1C's promotion box is marked partial. The P2 revisions-migration and propose-then-approve boxes are checked. Stale P0-R lines that said no full replay release existed are annotated. Also: 90 CI commands, and status-log entries for 2026-08-18 (Bridge v3.1 factorial, join effect null, p=0.65), 2026-08-24, 2026-09-21, 2026-10-04, 2026-10-08, and 2026-10-13 (no review revision since 2026-09-17: the review step runs but has failed on every article since 2026-09-18; newtags never switched on).
• Brain docs. Runbook header, status lines and Deploy banner updated; the rollback section now says the operator Mac (the example laptop path can't run it) and adds the Cloudflare deployments list fallback. BRAIN-SQLITE-HANDOFF.md points at the activation record. Stale status and deploy lines fixed in site/ops/README.md, brain/authority/README.md, and wiki/README.md. The host-context authorization is still described as needing Jack's approval, matching ROADMAP's open P1B box.
• CLAUDE.md / AGENTS.md (identical except the title). Production deploys go only through the promoter, with a warning about plain npm run deploy. newtags is not a running job. Note on the nightly host. Wikifunctions lines fixed. Full Brain REST route list. Manual D1 migration procedure for the out-of-sync remote tracking (headers of 0009-0012); new files stay idempotent, except a documented ALTER TABLE … ADD COLUMN migration that is verified after applying. Memory and handoff pointers fixed. No hard invariant was removed or weakened.
• Other files. CONTRIBUTING.md: Human-at-boundaries moderation (the nightly resolver decides only its three deterministic rules; everything else waits for a patroller) and P14534. docs/wikidata_property_proposal.md: status banner (created 2026-06-17; 115 statements on 2026-10-13; how the live property differs from the draft). Its seed note now says each tag was merged into Mathlib by a maintainer after Mathlib CI, replacing "≥2 human reviewers incl. a maintainer", which the bot's settle gate never guaranteed. docs/research-plan.md: refreshed instrumentation inventory and an RQ status table (no analyses yet). manage/README.md: untracked artifacts, current formalize limits, 03:20 schedule. HANDOFF.md: memory claim.

How tested

• Every live value was read on 2026-10-13 with read-only GETs: the selector and release.json (its SHA-256 equals manifest_sha256), /about, /stats, the HTTP status of each /api/brain/* route, /mcp (405 JSON vs 200 HTML with Accept: text/html), /wikilean.ttl (200), /out_w3c/ (404), /wikifunctions (200), /api/articles (778), all 778 article history pages (4,302 revisions), and the Wikidata API (P14534 entity, first revision, proposal-page revisions, and a SPARQL count of 115 statements). PR facts come from the bodies of Prepare SQLite migration pack and stage replay releases #35-Releases survive release-neutral merges to main; pin-only edge diffs aggregate (semantic-diff/v3) #45.
• Code facts were checked at 37b7036d and, where relevant, 2eb31baa and bf6b4e4a: brain_release_authority.is_release_neutral for every touched path, _check_recovery_checkout, the activation-bundle schema versions on both sides, the --execute bundle requirement, brain-canary.py's required arguments, routes in brain-api.ts/brain-edits.ts, the 9 MCP tools, and the migration headers.
• No relative Markdown link in the touched files is broken. diff CLAUDE.md AGENTS.md shows only line 1.
• An independent adversarial review checked every claim against the same saved evidence and the code. Its findings are fixed: an untested re-promotion workaround was removed, approvals the promotion can't prove are left unchecked, the /wikilean.ttl description was corrected, and inferred statements about the nightly are worded as inference.
• Docs only; no tests are affected. CI covers the rest.

Risks

• Docs only. The two release-affecting files above change no bytes the Worker or a release reads. They do make main non-neutral relative to any release built before this merges. main is already non-neutral relative to the live release (PR Releases survive release-neutral merges to main; pin-only edge diffs aggregate (semantic-diff/v3) #45 changed brain/tools), so nothing changes today.
• The activation record states what is publicly verifiable, plus the reconciliation outcome and candidate Worker IDs, which are marked as coming from the deployment journal. Where something is inferred, the text says so, and the remaining journal-only values are left blank for the operator.

What Jack must do

• Fill the "Operator must fill" table in docs/BRAIN-ACTIVATION-2026-10-04.md from the deployment journal: the event-chain hash, approval texts, full baseline, bundle and dry-run IDs, the predeploy Worker version ID, and the public-release source-policy record.
• Work through the decisions in the new "Waiting on Jack" list at the top of docs/ROADMAP.md.

[Deicyde]

Review status: merged in 5fb12e02; follow-ups remain

Update 2026-10-15: merged at 1969a165 (the head checked on 2026-10-14), together with #60's archive. Three items from that check are now on main and need a follow-up docs PR:

• docs/BRAIN-ACTIVATION-2026-10-04.md:190-192: the canonical-host, other-receipt-root and backup rows say "recorded in the private deployment journal", but the promoter's journal records none of these. They should say the value is still to be filled in by the operator.
• docs/BRAIN-ACTIVATION-2026-10-04.md:187: baseline release ID bfcfc912… has no cited source (PR Releases survive release-neutral merges to main; pin-only edge diffs aggregate (semantic-diff/v3) #45 cites only manifest 8328d804…). Cite its source or drop it.
• README.md:111: "wiki/src is unchanged on main since" the 2026-10-04 promotion is no longer true; wiki: stop storing flags.ip_hash; scrub legacy unsalted values #46, wiki: security headers on Worker responses + report-only CSP #47, wiki: /about describes the Human-at-boundaries moderation policy #55 and wiki: describe the Brain snapshot echo as what releases actually carry #62 changed wiki/src.
• Also still open from the check: a host-context row in the operator table, the deploy notes' hotfix wording, and the 2026-10-13 ROADMAP entry's /stats figures.

Original review (2026-10-14)

Independent adversarial review of 74d66832: a defect reviewer with skeptics, a design reviewer with a devil's advocate, and an arbiter.

Verdict: this is the right PR, and the activation record and status corrections check out. The last commit, though, records approvals that were never given, and the reconcile steps fail as written.

Required before merge

• Restore the forward-looking host-context gate at docs/BRAIN-RELEASE-RUNBOOK.md:139-141 and :471-472, site/ops/README.md:111-113 and brain/authority/README.md:421-423, and add a host-context row to the operator table. Commit 74d6683 changed "still needs approval" to "approved", but nothing records that approval and this PR's ROADMAP leaves the box open.
• In docs/BRAIN-ACTIVATION-2026-10-04.md:89-99, state the intent-match conditions (same worktree and Node binary, untouched wiki/node_modules, unchanged wiki/wrangler.jsonc, local main containing Canary: never advertise text/html, so Cloudflare's HTML rewrites cannot break the frozen-bytes check #44), drop the detached-2eb31baa route, and reconcile before pulling wiki: GET /api/version + npm run deploy refuses + narrower agent wrangler rules #54. The promoter's checks fail both listed routes.
• Four docs present the attempt's open state as current fact. Point them to the activation record, because only the operator journal knows.
• ROADMAP 2026-10-13 entry: say the review step runs every night and fails every article with no new tokens (Operations runbook and review-outage diagnosis #56). The current hedge understates the outage.
• Reword the migration "hard invariant". SQLite can't make ADD COLUMN idempotent, so any future column migration would break it.
• Deploy notes: mark the hotfix path as open (Waiting item 9). As written, they settle a decision that is still yours.
• Fix CONTRIBUTING.md:39, README.md:112 and the PR body's "separate PR" claim. The first overstates the resolver, the second goes stale once queued Worker PRs merge, and no separate PR exists.

Decisions for the maintainer

• Worker-only hotfix path: promoter-only (what these docs now say), or a separate Worker-only procedure (wiki: GET /api/version + npm run deploy refuses + narrower agent wrangler rules #54 is being reworked into a plain refusal).
• Should the options-only Waiting list sit at the top of ROADMAP?
• Add AGENTS.md and CONTRIBUTING.md to NEUTRAL_FILES?

Merge order: fix, merge #53 and then #60, merge before building release B, and reconcile before pulling #54.

Fixes are in progress; this comment will be updated.

Posted by the WikiLean PR swarm (lead); updated 2026-10-15.

[Deicyde]

Status review (2026-10-14): 🔧 Fix before merge

Most claims check out against main and production, and this PR changes no Worker or release bytes. The headline status, though, is out of date.

Fix before merge

• The 2026-10-04 promotion attempt is not open. The deployment journal records a final_state of deployed_reconciled at 2026-10-08T06:58:30Z. Yet docs/BRAIN-ACTIVATION-2026-10-04.md (around lines 85-98 and 144) and docs/ROADMAP.md ("No reconciliation is recorded as of 2026-10-13", Waiting Migrate the Wikifunctions verification project to Deicyde/wikifunctions #1, Immediate queue item 1) still treat it as open.
  • Update the text and drop those queue items. The same status also appears in README.md (~lines 17-19), docs/BRAIN-RELEASE-RUNBOOK.md (~lines 7-8 and 483), site/ops/README.md (~lines 110-111), docs/BRAIN-SQLITE-HANDOFF.md (line 4) and elsewhere in docs/ROADMAP.md (~lines 250, 487 and the 1285 status-log entry).
  • Fill the "Operator must fill" table from the journal, keeping host and backup locations out of this public repo.
  • Promotions are no longer blocked.
• Still worth documenting for future attempts: reconcile also requires the checkout's wiki/wrangler.jsonc and the Node/Wrangler toolchain to match the intent byte for byte. So don't change wrangler.jsonc or the toolchain between P1C execute and a clean final_state.

Nits

• The new hard invariant can't always hold. "Keep new files idempotent (CREATE … IF NOT EXISTS, as 0009–0012 are)" (AGENTS.md/CLAUDE.md ~line 118) is impossible for ALTER TABLE … ADD COLUMN in SQLite, and wiki: serve wp-update the whole drifted set (cap 1000) instead of attempt stamps #63's 0014 already breaks it. Reword it to allow documented, non-idempotent ADD COLUMN migrations that are checked after applying.
• The PR body says a separate PR makes AGENTS.md and CONTRIBUTING.md release-neutral. No such PR exists. Meanwhile this PR adds dated, volatile status to AGENTS.md, so every future refresh of it will be release-affecting.
• ROADMAP checks two P1B boxes beyond what the evidence records: the shadow nightly, and the freeze box ("with the approved Git, Node, npm, and Python executables") while the approval box is still open.

Cross-PR wording

• wiki: GET /api/version + npm run deploy refuses + narrower agent wrangler rules #54: if it merges, npm run deploy is no longer plain wrangler deploy. Settle the deploy-policy wording together with wiki: GET /api/version + npm run deploy refuses + narrower agent wrangler rules #54.
• Encrypt local D1 backups with age #58: after it merges, the backup step's npm run backup:d1 needs age and BACKUP_AGE_RECIPIENTS. Mention that.
• wiki: describe the Brain snapshot echo as what releases actually carry #62: once it merges, wiki/src/mcp.ts no longer describes a build time and Mathlib revision, so the BRAIN-ACTIVATION sentence about the snapshot echo (around lines 45-47) should drop its mcp.ts reference. docs/BRAIN-API.md still describes them until wiki: describe the Brain snapshot echo as what releases actually carry #62's planned follow-up.

Order: merge with a merge commit, not squash or rebase, or #60 conflicts in 3 files. Then retarget #60 to main. AGENTS.md and CONTRIBUTING.md are release-affecting, so land this before the next Brain release is built.

---

_{🤖 Automated status pass by Claude Code over all 18 open PRs (#46–#63), posted for the repo owner. An independent verifier re-checked each finding. All 18 heads were also merged and tested together in a scratch tree; the only test failure that comes from combining them is #47 × #55 (three other pairs had mechanical text conflicts). Reviewed head: 74d66832.}

[Deicyde]

Fixes pushed (2026-10-14)

This addresses findings from the "Status review (2026-10-14)" comment and the PR swarm's review: the reconciled attempt, the reconcile conditions for future attempts, the host-context gate, the migration rule, the resolver scope and the 2026-10-13 review entry.

What changed

• 85c974a1: the six docs the status review listed now record the 2026-10-08 reconciliation (deployed_reconciled), and ROADMAP's queues drop the reconcile item. The activation record replaces the open-attempt section (its 2eb31baa route and reconcile command) with the reconciliation record. Its operator table gains the outcome and candidate Worker IDs, and the host, receipt-root and backup rows point to the private journal.
• 85c974a1, 2af03d0d: the runbook says a future reconcile needs wiki/wrangler.jsonc, the Node/Wrangler executables (paths and versions) and the installed Wrangler tree to match the intent byte for byte. 2af03d0d adds the paths and the tree.
• 6e56b4df: the runbook, site/ops/README.md and brain/authority/README.md again say each new bundle's host context still needs Jack's authorization, matching ROADMAP.
• d1382a8b: AGENTS.md/CLAUDE.md allow a documented ADD COLUMN migration that is verified after applying. CONTRIBUTING.md limits the resolver to its three rules.
• 85c974a1 also states the review-step failures in the ROADMAP 2026-10-13 entry, and fixes two ID labels and two README anchors.

Verification

• At 85c974a1: test_moderate.py 124 passed; the authority (7) and activation-CI (16) tests OK; link check 58 links, 0 broken; CLAUDE.md and AGENTS.md differ only on line 1.
• Docs: archive superseded docs #60 still merges cleanly onto 2af03d0d.
• CI on 2af03d0d: all checks green.

Not changed / still open

• The PR body's "separate PR" sentence, ROADMAP's checked P1B freeze and shadow-nightly boxes, the missing host-context row in the operator table, and README's "wiki/src is unchanged on main since" row.
• Owner decisions: the Worker-only hotfix path (the deploy notes still say none exists), where the Waiting list goes, and NEUTRAL_FILES.
• Cross-PR wording for wiki: GET /api/version + npm run deploy refuses + narrower agent wrangler rules #54, Encrypt local D1 backups with age #58 and wiki: describe the Brain snapshot echo as what releases actually carry #62 waits until they merge.

Merge notes

• Merge with a merge commit, not squash or rebase, or Docs: archive superseded docs #60 conflicts. Then retarget Docs: archive superseded docs #60 to main.
• Land this before release B is built. "Reconcile before pulling wiki: GET /api/version + npm run deploy refuses + narrower agent wrangler rules #54" no longer applies.

---

_{🤖 Posted by Claude Code for the repo owner. An independent verifier checked the fixes through 85c974a1 before they were pushed; 2af03d0d applies its one should-fix finding. Head: 2af03d0d.}