Repository navigation
Description
Revised 26 October 2026 after the independent audit (C+, revise before Stage 0). All six of its required changes are applied below; the list is the revision comment on this issue. The owner kept #253 as written: persona implementation waits for #253 §10's full MVP acceptance, including P3 and the ten pilot pages. This issue's end state is therefore "ready to prepare the persona plan", not "ready to build the agents".
Dedicated implementation issue for the next stretch of the curation MVP, under #254 (the plan), #253 (the specification, which governs on any conflict) and #193 (the programme). Written 26 October 2026 against main at 9ccc427. It adds no feature. It puts #267 and #264 in one order, with their parallelism, their deployment order and their gates, and it names everything else that still stands between the programme and persona implementation (§4), so the whole route to the agents is visible in one place.
1. Why this issue
The remaining work is spread over #267 (the runtime made live), #264 (P6, the proposal path), #254's unstarted P3, #253 §10's acceptance and five audit comments (four on #254, one here). None says, in one place, what order the rest runs in, what can run at the same time, what must be deployed before what, and what is still the owner's to decide. This issue does. #267 and #264 stay the build issues; Stage 0 (§5) is what corrects them.
2. Where the programme stands (26 October 2026, verified by the audit)
| Part | Issue / PR | State |
|---|---|---|
| P1 published reader | #255 / #256 | Merged, live. On love is published: composition/version 1/1, 3 items, receipt 5. Its three notes are the accepted placeholders, signed "Account #2". |
| P2 owner's screen | #257 / #258 | Merged. The owner's three-page exercise has not happened; #257 closed on 26 Oct with the exercise transferred to #264 §8 step 2a. |
| P3 PoetryDB pin | none | Not started, no dedicated issue. Waits on the owner's two decisions (O1). |
| P4 packet v2 | #262 / #265 | Merged, live. Packets for love, war, hope, truth and coward build, freeze, verify and fit (the audit's read-only run). |
| P5 freshness | #259 / #261 | Merged, live on love: refresh row 1, generation 3, last outcome needs_editor (an input check, not an editorial judgment). #198 stays open: prompt suppression of already-open readers is unproved. |
| P7 runtime + benchmark | #221 / #260, #263, #266 | Merged. #266: GO, 9 of 9 (run 1793029211, attempts 52–70). Bench holds 3 model configs, 1 service, 70 attempts; v2 holds 0 / 0 / 0. The authority marker names the bench database; the service is stopped. |
| P6-0 runtime live | #267 | Not started. Only its GO box is ticked. |
| P6 proposal path | #264 | Not started. Its body still holds the pre-audit instructions and a warning comment that it is unreliable until corrected. |
| v2 curation state | 5 proposed curator profiles, 0 profile versions, no generic editor; one enabled global-default configuration with one immutable manual version. |
3. This issue's end state: "ready to prepare the persona plan"
This issue closes when all of these are true, each with its evidence linked here.
- The runtime is live on v2. One immutable model config (
qwen3.5-9b-v2,generic-editor-v2) registered in v2 with its licence and hash; the service bound to v2;ready --smokepasses; three rehearsal attempts (love, war, hope) posted with readings and a confirmed stop. (Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 §12, as corrected in Stage 0.) - One editor has gone end to end through the record, including its failures. The
generic-editorprofile admitted with a bot actor under a narrow admission rule; a real packet becomes a validated attempt, the attempt becomes a proposed version with model attribution and an attempt link; no bot operation moves a published pointer. Evidence also covers: a crash after the result receipt, a stale or uncertain result recovered, suppression and configuration change during a run, a review reservation recovered, a proposal superseded on arrival, and an offline service that defers without advancing freshness or delaying a reader. - The owner has curated by hand. Three pilot pages curated on
/ops/curationwith the owner's own reasons under the owner's actual public label; love's placeholders replaced through new attributed versions; one page withdrawn, re-opened and re-published; all three end published. - The baseline exists. Five real, non-abstained proposals on five pilot pages, each reviewed on the full quality form (a dismissal counts only with the full form and its reason); at least one edited or dismissed with a reason; a Take only where deserved; D4 (no self-publication) unchanged. The five forms posted on Curation agent MVP: what an editor does, what a curated entry contains, how the page looks, how the owner and the bots share one record, and how it stays current (under #193) #253.
- The shared editor seams are named, each with its file and test, so a later persona plan builds on them rather than beside them:
- exact On-scope provisioning and server-side configuration resolution; the immutable editor/model/instruction binding and its invalidation on a new configuration version;
- Candidates → frozen packet → registry, reference and lead-rule validation, the bounds, the omissions and the duplicate-display check;
- refresh admission, the persisted
needs_editorhand-off, the original published parent, generation, token and lease, suppression and recovery; - the runtime call under the one global slot and the 30-minute daily inference budget;
- every non-proposal outcome (no result, unchanged, refused, uncertain), durable review-unit reservation and release, dismissal history, supersession;
- the trusted proposal writer and its attribution; the trusted human Take/Edit path that preserves authorship, ancestry and compare-and-switch, with the quality form enforced;
- D8 marks and D9's attempt audit.
- P6's post-activation re-audit is complete and satisfactory (Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 §8's "then the re-audit"), posted on Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 and linked here. A requested audit is not a completed one.
What a persona will need that this issue does not build, recorded so the persona plan starts from it (from the audit's answer 1): a versioned dossier-to-prompt seam with its own prompt identity, context budget and provenance; a frozen participant, profile and configuration identity per run; run, round and ballot persistence; roster routing; partial-result recovery; equal weights and the fixed 4-of-5; missing versus abstained responses; ten calls plus one repair; the 20-minute panel deadline and lease renewal beyond P5's 10-minute lease; dissent; finalized panel authority. A persona does not use the generic editor's no-dossier admission exception or the owner's Take/Edit controls; participant ballots are not each an owner-review proposal.
4. After this issue: what still gates persona implementation
#253 is unchanged, so persona implementation starts only when #253 §10 is fully accepted. After this issue closes, that still needs:
| Remaining MVP item (#253 §10) | Owner | Can start |
|---|---|---|
| P3: the PoetryDB pin, its withhold-and-restore round trip, a pinned poem rendered as a highlight | The owner's O1 decisions, then a dedicated P3 issue and session | Now, in parallel, as soon as the owner takes O1. P3 touches discovery, the registry and the opening's work tile; agree the components/opening.ex boundary with #264 in Stage 0. |
| The other five pilot pages showing an opening (or an honest nothing) | Owner, with the editor's proposals | After item 4 above |
§6a demonstrations (owner-curated page receives a proposal without moving; withdrawn page receives none; superseded_on_arrival) |
#264 Delivery B evidence | With items 2–4 above |
| Restore from a bundle, including the new proposal, mark, dismissal and model-config records | A bounded check under #211's bundle | After item 4 |
| #198's prompt suppression of an already-open reader | Unassigned; needs a delivery decision | Any time; do not close #198 on P6 counts |
When those are done, the persona plan (drafted any time after this issue) gets its own independent audit, and persona implementation starts. Fastest route to the agents: take O1 now so P3 runs alongside Stages 0–3, rather than after them.
5. The plan
Stage 0 design: #264's resolved contract + #267 reconciled ──► one independent check
│
Stage 1 ┌─ #267 Delivery A (rehearse, Health card, runbook) ─┐ two worktrees on the Studio,
└─ #264 Delivery A (disabled, stubbed runtime) ─┘ in parallel; P3 alongside if O1 is taken
│
Stage 2 merge #267 and deploy it ──► rebase #264, integrated review + precommit, merge, DO NOT deploy
│
Stage 3 3a #267 live window: idle check, start + rebind to v2, register, smoke, rehearse ×3, stop
3b #264 migration on v2 (owner's yes), editor disabled ──► then deploy #264's code
3c editor configuration activated; love re-established under it; owner's three pages;
five page identities provisioned; proposal path enabled
3d proposal window: love, then war, hope, truth, coward; five forms; stop
3e P6 re-audit
│
end state (§3) ──► §4's remaining MVP work ──► persona plan audited ──► persona build
Stage 0. Resolve #264's contract and reconcile #267 (a design session, no code)
The nineteen corrections (the fourth audit's §E, on #254) are necessary but not sufficient: several say "define" or "resolve" rather than giving the resolved rule. Stage 0 produces the resolved contract, written into #264's body with its schema, migration and test matrix, and a comment on #264 listing what changed. Corrections 1–2 state today's fulfilled GO (#266), not the fourth audit's open-PR state. It must resolve, at least:
- Ancestry.
editorial_composition_versions_shaperequires(version = 1) = (parent_version_id IS NULL), but the proposal's parent is the published pointer captured at admission, which can be null at version 2 or later (after an unpublished draft, a first unaccepted proposal, or withdraw and re-open). Separate published-parent from version ancestry in the scoped migration; never invent a published parent. - Retry identity.
Refresh.act(:admit, …)keeps a deferred row's generation but recaptures the current published parent (refresh.ex:364). State what stays frozen on retry and recovery, and when changed inputs require a new generation and request key. - Enablement versus activation. The configuration manifest (
Configurations.manifest/1, private),ready?/1,resolve_default/1andcurrent/1know only manual mode. Name their changes, the owner's explicit immutable-version creation and activation step, and what happens to love's published version and the owner's manual versions, whichStandingwithholds once made under an older configuration version. - Carry-forward (O2). A kept reference outside the frozen packet is not a model-selected candidate: give copied owner items a separately verified source identity and truthful human attribution. The arrangement still fits one lead and three highlights: specify precedence and overflow when kept items and model choices exceed it, revalidation when marks change during a run, dedup on the actual arrangement, and revised tests. A blanket "model dropped a kept item → refuse" conflicts with carry-forward and is replaced.
- Frozen reference reconstruction.
Packet.summarystoresexcerpt_sha256, not the quotation'swords_sha256(confirmed on bench attempt 59). The proposal writer reconstructs against stored frozen identities and hashes, or the attempt persists the needed reference metadata, and refuses drift. The quote's substring hash stays distinct from the full quotation's reference hash. - Storage choices. Lifecycle storage (or tightly bounded status mutability) for immutable versions; the honest uniqueness rule for an unchanged Take; durable pre-run review-unit reservation, recovery and release (Gateway's pending units count inference, not reviews); exactly-once attempt-to-proposal linkage.
- No bypass. The editor's existing direct Publish of the latest held version and the ordinary manual writer (which stamps notes human) must not bypass Take, the quality form or provenance for a proposal.
- Abstention. The editorial-outcome storage and disclosure contract for a successful abstention, including its 48-hour assessment and cooldown, without loosening
RefreshState's outcome CHECK by accident. - Backward-compatible migration. The scoped migration must be safe under the old code (Stage 3b applies it before Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's code is deployed): additive, nullable or defaulted, constraints only widened for the new path.
- Reconcile Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 with §6.1 and §6.2 below, and replace Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's comment "P6's own build starts after Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267's Delivery A is merged" with the parallel rule in Stage 1.
- Regenerate both file manifests from the resolved contract; the overlap in §6 is the briefs' current lists, not a guarantee.
Stage 0 ends with one independent check of the resolved #264 and the reconciled #267 before any build session starts.
Stage 1. Two build sessions in parallel
#264's Delivery A is built disabled, with the runtime stubbed through Req.Test; it needs neither #267's code nor a live model. Each session in its own worktree on the Studio, its own partition (_cp60 for #267, _cp6 for #264), stopping at a reviewed PR (CodeRabbit and one independent review). Coordinate the two full precommit runs; the Studio is shared. File ownership is §6.
Stage 2. Merge order and deployment order are separate
Deploying here means advancing the Studio checkout's main, which the server on 4007 runs from.
- Merge Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 and deploy it. It has no migration; its Health card must render on v2 with zero model configs and services (§6.2).
- Rebase Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 on it; run the full precommit on the integrated head and review the integrated result (a clean merge is not a compatibility test); merge Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 on GitHub.
- Do not deploy Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 yet. Its new Ecto fields would be selected before their columns exist:
Published.currentdoesRepo.get!(CompositionVersion, …)(published.ex:68), so anattempt_idfield breaks every published page until the migration runs. Deployment waits for Stage 3b.
Stage 3. Live steps, each on the owner's named yes in chat
3a. #267's live window (no proposals written):
- Confirm the bench slot is idle (
budget,sweep, the services row) and handle the already-stopped state. - Start the service and rebind it to v2 (
service start --rebind); record the marker's new contents. - Register the pinned config against the running service (
setup --accept-license; registration reads/api/version,/api/tagsand/api/show, so the service must be up). The owner reads the licence. Record the row id andconfig_hash; it should equal bench config 3's5b8b65ad…if the inputs are identical. ready --smoke; record the receipt. The smoke writes an attempt, so v2 holds four attempts after the rehearsals, not three.- Rehearse love, war and hope,
--dry-runfirst on each; post the records. - Stop, confirm, readings 30 s after.
3b. #264's migration, then its code. On the owner's yes: apply the one scoped migration to v2 from a worktree at the merged head, with the editor still disabled. Verify the old code still serves (it must, by Stage 0's compatibility rule). Then deploy #264's code.
3c. Activation, each step on its own yes:
- Seed and admit the
generic-editorprofile under its narrow admission rule. - Create and activate the immutable configuration version that selects the editor and the model config (Stage 0's contract); re-establish love's publication under it as Stage 0 specifies.
- The owner's three pages (§3 item 3): actual label, own reasons, love's placeholders replaced, one withdrawn, re-opened and re-published, all three published.
- Provision the composition identities for all five proposal pages through the authorized seam. Truth and coward have none today, nor do war and hope; a visit cannot create them.
- Enable the fenced proposal path.
3d. The proposal window. Start the service; love first, then war, hope, truth and coward; the owner reviews each on the full form; stop and confirm. Post the five forms on #253 and the ids here.
3e. The P6 re-audit (§3 item 6).
6. File ownership and interfaces for the parallel builds
refresh_worker.exbelongs to Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 alone. Onmainthe worker calls onlyRefresh.claimandRefresh.check; it never calls the runtime, so it cannot meet a down model service. Theservice_unreachablerefusal and backoff, and Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267's test 4, move to Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's fenced editor step, keeping the rule: offline inference never advances editorial freshness or delays a reader. Move every Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 reference together: D-F, the §5 seam row, §6 scope, §7 files, §8 test 4, §12 acceptance and §13's prompt. Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267's runbook says visits invoke an editor only after Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 is enabled.health_live.exis shared by card, over a defined interface. Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 owns the "Editor runtime" card; Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 adds its own card below. The card is non-mutating and absent-data safe: it must not callReadiness.checkorGateway.budgetunchanged, because both reachGateway.service!, which inserts (gateway.ex:34–39); it reads a SELECT-only snapshot and renders "none" where v2 has no config, service or refusal. Pending review units belong to Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's card; Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267's card shows inference minutes only and does not imply zero review work from an idle slot. Stop history:inference_servicesstores no window or stop history, so the card shows current state only; the confirmed stop and readings live in the rehearsal and window records. Both sessions agree this interface in Stage 0, then rebase and review the integrated result.components/opening.exis Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's for the disclosure changes; if P3 runs in parallel, its work tile is agreed with Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 in Stage 0.
7. Owner decisions
| Decision | Default | |
|---|---|---|
| O1 | P3's two rules: the poem-to-page relation (#253 D6) and PoetryDB supersession (#254 P3 "Identity") | Open. Deferring them does not block this issue, but P3 gates #253 §10 and therefore persona implementation; taking them now lets P3 run in parallel (§4). |
| O2 | Kept items outside the packet's cut (love's published quotation 248575 is omitted over_quota) |
Trusted carry-forward with precedence and overflow rules, resolved in Stage 0; P4's policy unchanged. If Stage 0 cannot resolve it without new scope, P6 stops and says so. |
| O3 | The five proposal pages | love, war, hope, truth, coward. Each has an admissible Bierce lead; all five packets verify and fit (audit: love 10/32, war 9/29, hope 8/17, truth 7/16, coward 6/6). Revalidated at run time; identities provisioned in 3c. They do not test no-lead pages or live exemplars. |
| O4 | The public actor label replacing "Account #2" | The owner's own choice at 3c step 3, recorded with the new attributed versions. |
| O5 | Parallel builds | Yes, after Stage 0 settles §6 and the deployment rule. Parallel building authorizes no live step and waives no review. |
8. What this issue does not do
No code, migration, model call, service start or database write. It changes no part's brief directly; Stage 0 does that. #253 is not amended. Personas, ballots, panels, a second model, the Mac mini, #190 (needed only for bot nominations) and automatic publication are out, as in #253 §10.
9. Audit record
- 26 Oct 2026: independent audit of the first version, C+, "revise before Stage 0". Its six required changes are applied in this revision. Its recommendations are kept as notes: preserve the measured cut-v1 baseline; freeze evaluation pages and the held-out policy before any persona tuning; update
docs/curation/runtime-operations.md(it still says source and Postgres stay internal) and Delivery: curated opening section with five local persona editors and visit-driven refresh #193's stale body status when those are next reconciled. - Next: the independent check that closes Stage 0.
10. Acceptance
- Stage 0: Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's resolved contract, schema, migration and test matrix in its body; Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 reconciled per §6; both commented; the independent check posted and its required changes applied.
- Stage 1–2: Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 merged and deployed; Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 rebased, the integrated head reviewed with precommit counts, merged and not deployed before 3b.
- 3a: Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 runtime/rehearsal evidence complete: marker, config row 1, smoke attempt 1, rehearsals 2–4 and confirmed stop; sitting 1 record. No later stage accepted.
- 3b: proposal migration applied after verified recovery copies; old-code public/auth-boundary compatibility checked; Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 code deployed at pinned
9bfa244, editor/model off. Sitting 2 evidence. - 3c: editor admitted; configuration activated and love re-established; the owner's three pages published; five identities provisioned; proposal path enabled.
- 3d: five forms on Curation agent MVP: what an editor does, what a curated entry contains, how the page looks, how the owner and the bots share one record, and how it stays current (under #193) #253; ids and recovery evidence here.
- 3e: P6 re-audit complete and satisfactory.
- §3 items 1–6 true, each linked.
- §4's remaining items each have an owner and an issue or a recorded decision; Curation MVP implementation plan: seven parts with agent-ready briefs (P1 read compositions, P2 screen, P3 pin, P4 packet, P5 freshness, P6 proposals, P7 runtime) — under #253 #254's checklist and Delivery: curated opening section with five local persona editors and visit-driven refresh #193's status updated.
Activity
holden commentedon Oct 26, 2026
Independent audit of #268 — 2026-10-26
Verdict: revise before Stage 0. The status summary is substantially accurate, and parallel stubbed builds are feasible, but the proposed agent-readiness gate and live deployment sequence are not safe as written. The nineteen corrections are necessary, not yet a sufficient executable contract.
These grade this plan's present implementation readiness, not the quality of unbuilt #264/#267 code.
Evidence and limits
I read #268, #193, #253, #254 and all its comments, including all four audits, the reconciliation and the final P7 GO; #267, #264, #198, #257, #259 and #262 and their relevant delivery comments; both 26 October benchmark records and runtime-operations.md. I inspected the curation schemas, refresh/profile/configuration/composition/review/authority/runtime paths, curation LiveViews, Health, and curation migrations, and compared the relevant constraints/triggers with the actual database catalog.
Audited main:
9ccc42748284a2610d45509aba6c8b1a157ecf46. Studio HEAD, its existing origin/main and GitHub main agreed. I did not pull. GitHub independently confirms PRs #256/#258/#260/#261/#263/#265/#266 merged; its open-PR collection was empty. There is no Proposals or Rehearsal implementation on this main. That establishes the delivered-code position, not the absence of private unpublished work.I connected to the Studio as holden and read its AGENTS.md. Both database inspections used PostgreSQL 18.2, port 5434, cluster 7693849764459364596, SELECT only, with default_transaction_read_only=on. A separate read-only Repo process, without the application/Oban/endpoint, built, froze, verified and checked estimated fit for the five proposed pages, plus greed/bestiality. I independently recomputed both benchmark verdicts from committed raw samples with main's Bench.summarize/verdict; this called no model.
Own suite, once:
MIX_ENV=test MIX_TEST_PARTITION=_audit268 DD_NO_OBAN=1 mix precommit, detached external-drive worktree at the audited SHA, deps/data and every replay gzip symlinked from main: 19 doctests, 2,986 tests, 0 failures; seed 86311; ExUnit 405.4 s; exit 0. The worktree was clean and was removed; main remains clean. This tests main, not the unbuilt proposal path.No live/bench writes, migrations, jobs, model calls, pulls, downloads, service start/stop/rebind, or requests to/restarts of 4007 were performed. I did not exercise signed-in owner controls or remeasure layout. Historical owner approvals and confirmed stops are documented evidence; I did not recreate them. Process/listener inspection found no model-service pid file, listener on 11435, or matching dictionary model process.
§2: claims versus verified state
Additional SELECT inventory: v2 has 5 proposed curator profiles, 0 profile versions, no admitted generic editor, one enabled global-default configuration, one immutable manual configuration version, zero roster members and one activation receipt. Bench has zero compositions, versions, items, reviews, composition-publication receipts, curator profiles or refresh rows. Page-publication receipts, a different subsystem, number 114 on v2 / 0 on bench.
Oban by worker/state on v2: RefreshWorker 3 completed; CleanupWorker 672 completed; Discovery.RunWorker 67 completed + 2 cancelled; Quotations.VerifyWorker 337 completed. Bench has no jobs. The refresh generations match P5's two checks and P4's transition. Older audits' discovery totals are historical snapshots, not today's totals.
The authority marker still names devils_dictionary_runtime_bench on the expected cluster. A database slot marked available is not proof that the OS service is running.
Answers to §8
1. Is §3 the right end state; what seams are missing or not reusable?
It is a useful generic-editor hand-off, but not the governing bar for starting persona implementation. #253 §11 explicitly puts personas/panels after the MVP; §10 includes ten pilot pages, the PoetryDB pin/withhold/restore round trip, freshness/owner-rule demonstrations and recovery evidence. #268 expressly excludes two of those deliverables. Saying “personas lose nothing” is a technical dependency argument, not permission to change the governing scope. Preparing a persona plan can precede MVP completion; calling that “ready to build” cannot, unless the owner explicitly changes #253.
Item 5 also describes less than the shared editor contract. Add named, tested seams for:
A persona needs a versioned dossier-to-prompt seam and a frozen participant/profile/configuration identity. Current Packet.messages accepts pinned generic instructions; Runtime checks the packet instruction against the immutable model config. A dossier cannot simply be appended without designing its prompt identity, context budget, provenance and validation.
The persona plan must own run/round/ballot persistence, routing the admitted roster, partial-result recovery, equal weights/fixed 4-of-5, missing versus abstained responses, the ten normal calls/one repair maximum, the 20-minute panel deadline, dissent and finalized panel authority. A panel may outlast P5's current 10-minute running lease; renewal/recovery must be designed. These are future-phase work, not reasons to implement a panel in #264.
What a persona does not use: the generic editor's special no-dossier admission exception, human quality-form controls, or human Take/Edit buttons. The owner uses those. D8 constraints and D9 audit still apply to persona output. Nor should each ballot automatically become a separate owner-review proposal/reservation; distinguish participant output from the final reviewable composition.
2. Are the §5 scope moves sound?
5.1: accept, with all references reconciled. RefreshWorker only calls Refresh.claim and Refresh.check. Refresh reads/computes inputs and completes or defers. Neither calls Runtime.run or the model. A down model service therefore cannot be its present failure.
The service-unreachable refusal/backoff and #267 test 4 belong to the new fenced editor step in #264. Preserve that test's rule: offline inference never advances successful editorial freshness or delays readers. Move #267's D-F assertion, §5 seam row, §6 scope, §7 file, §8 test, acceptance and implementation prompt together, not just one bullet.
Nothing in rehearsal itself needs this worker behavior: #267 calls Runtime directly and can record its own refusal. Its “last worker refusal” Health row must tolerate none/not yet implemented until #264 lands. The operating-window runbook must identify that visits actually invoke an editor only after #264 is enabled.
5.2: accept layout ownership, reject the implied sufficiency. Separate cards do not define their data/API dependencies. In particular, Readiness.check calls Gateway.service!, and Gateway.budget defaults through service!; service! executes INSERT ... ON CONFLICT DO NOTHING. Using those APIs unchanged is not a read-only Health implementation. It must use an explicitly non-mutating snapshot/query and handle absent live rows/configs.
Gateway.budget reports inference milliseconds, not pending proposal review units. That count belongs to #264's durable accounting. #267 must display unavailable until that seam exists, or put the review count on #264's card. Do not infer zero pending review work from an idle inference slot. Also name the evidence source for “last window / stop confirmed”: ServiceProcess.stop returns confirmation and removes the pid file; inference_services does not store window/stop history. An absent listener is not a historical confirmed-stop record.
5.3: refuse as an unconditional agent-phase scope change. P3 need not block #267/#264 engineering or the first generic proposal. It still gates MVP completion, which #253 currently puts before persona implementation.
3. Is parallel Delivery A safe, and what if #264 merges first?
The complete literal intersection of #267 §7 and #264 §5 is:
lib/devils_dictionary/curation/refresh_worker.exlib/devils_dictionary_web/live/health_live.exNo other file is literally listed in both sections. The corrected briefs' manifests must be regenerated: configuration enablement, lifecycle/capacity storage and any extracted Bench measurement helper may require additional files. “Only expected conflict is Health” is a prediction, not evidence.
Code merge order is not a hard runtime dependency: a correctly disabled, stub-tested #264 could merge before #267 without itself needing Rehearsal. Its live activation would lack #267's command/runbook/evidence, and the current #264 warning comment explicitly requires #267 Delivery A merged first; reconcile that instruction if parallel work is accepted. Any eager call to a future Health API would additionally break the build.
The larger defect exists in either merge order: both PRs merged, then #267 live work, then #264 migration leaves a deployment gap. Pulling/loading that combined head exposes Ecto schemas with columns/tables absent on v2. For example, Published.current uses Repo.get! on CompositionVersion; adding attempt_id makes that query select a nonexistent column before migration. Composition mode and proposal telemetry create similar exposure. The no-config-change reloader is not a migration barrier.
Specify a compatible migration-before-new-schema-code deployment, or explicitly isolated deployment of #267 while #264 remains undeployed. This is a static consequence of the proposed schema/read path, not a failure I induced on 4007. Rebase and final combined-head verification remain required regardless of merge order.
4. Do the nineteen corrections make #264 executable as written?
Not yet. Their diagnoses remain mostly correct, but several say “define/resolve/specify” rather than supply the resolved contract. Stage 0 must produce that contract and revised tests, not paste nineteen summaries and declare readiness.
The existing live CHECKs/triggers confirm the original problems: manual-only version/item origins, human version author, immutable versions/items, sourced/deceased profile admission, human-note author equality and actor-label equality, the arrangement/fingerprint dedup index, and refresh outcomes limited to unchanged/needs_editor.
Further concrete conflicts/unfinished resolutions:
editorial_composition_versions_shapestill requires (version = 1) = (parent_version_id IS NULL). The required parent is the published pointer captured at admission. After an unpublished draft, a first unaccepted proposal, or withdrawal/re-open, that pointer can be null for version 2 or later. Merely adding model origin/bot permission still fails this CHECK. Resolve published-parent versus version ancestry in the scoped migration; do not invent a published parent.Corrections 1–2 should use today's fulfilled GO rather than preserve the fourth audit's historical open-PR state. Corrections 6/7/10/11 are appropriate narrow changes; they are not permission to disable general immutability, deceased-person admission or human review/publication authority.
5. Are O1–O5 safe defaults?
Own Candidates/Packet results, generic-editor-v2, all freeze/verify :ok and estimated fit :ok at 8,192 context / 1,024 output:
Love/war/hope hashes reproduce the previous audit's values; truth is
554b8b5e84d9b2866d52242678d5aa2c81ba4f1982080a54de19cdbcef3f36dc, cowardee5270fec4c99b6888ddabb16cf7aea457f4ac86b204a77e8f3d68c93b738537. Love's current published item 3, quotation-248575-3, is indeed omitted over_quota. Greed/bestiality build at 7/7 and 3/3, with zero admissible leads. No accepted exemplar was offered on these pages; works on the first three are catalog artworks.6. What path/gates are missing?
Beyond the conflicts above:
Required changes to #268 — before Stage 0 starts
These are plan/contract corrections requested by this audit; I have made none of those edits.
Recommendations, separate from required changes
Ranked risks
Smallest safe sequence
Only GitHub write by this audit: this comment. No issue body, PR, commit, live record, service or server was changed.
[-]Curation: the last stretch to the agents — #267 and #264 in one audited order, parallel builds, and "ready to build the agents" as a checkable state (under #254, #253, #193)[/-][+]Curation: the next stretch to the agents — #267 and #264 in one audited order, deployment gates, and "ready to prepare the persona plan" (under #254, #253, #193)[/+]holden commentedon Oct 26, 2026
Revised after the independent audit, 26 October 2026
The owner kept #253 as written: persona implementation waits for #253 §10's full MVP acceptance, including P3 and the ten pilot pages. The end state is renamed "ready to prepare the persona plan", and the title with it. The audit's six required changes, as applied:
words_sha256), lifecycle and review-unit storage, the Publish and manual-writer bypass, abstention, and a backward-compatible migration. It reconciles Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's "after Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 Delivery A merges" comment and every Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 worker reference, and ends with one independent check.Published.current,published.ex:68).Readiness.checkorGateway.budgetunchanged (both reachGateway.service!, which inserts). Pending review units belong to Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264's card. Stop history comes from the rehearsal and window records, not the card.Kept from the first version: the worker's
service_unreachablerefusal moves to #264 (the audit accepted it, with every #267 reference moved together); the five pages (love, war, hope, truth, coward); parallel stubbed builds, now after Stage 0.holden commentedon Oct 26, 2026
Independent re-audit of #268 — 2026-10-26
Verdict: GO for Stage 0's design/reconciliation work. NOT yet GO for Stage 1 builds or live activation. Overall grade: B+, up from C+. The revised issue now represents an honest generic-editor milestone and preserves #253's full MVP gate before persona implementation. The old audit's six required topics have been addressed in the plan; the design obligations they identify have not yet been discharged in #264/#267.
This is a re-audit of the revised planning issue, not its future Stage 0 independent check and not acceptance of unbuilt code.
Evidence and limits
I reread the current #268 body and revision comment, compared them with my first audit, and reread the current #264/#267/#253/#254 bodies and comments. I rechecked the relevant main source, especially the proposed P3 interaction with Packet.
Exact main remains
9ccc42748284a2610d45509aba6c8b1a157ecf46, independently matching Studio HEAD, its existing origin/main and GitHub main. Studio working tree is clean; GitHub's open-PR collection is empty. #264 and #267 have not yet been rewritten. That is expected before this revised Stage 0; it is not evidence that Stage 0 is complete.Fresh database checks were SELECT only, PostgreSQL 18.2, port 5434, expected cluster 7693849764459364596, with default_transaction_read_only=on on both connections:
5b8b65adc7709921eb5cd06ba9d4dc1b96404e82ab04a5eb59bb709021da62cd; service available, epoch 1/fence 70, no holder. Attempts 52–70 remain 13 accepted selections and 6 abstentions.No suite rerun: source/main did not change, and this is a planning revision. My earlier independently executed result remains 19 doctests, 2,986 tests, 0 failures, seed 86311, exit 0, at this same SHA. It is historical evidence from the first audit, not a second run. Likewise the first audit's independently reproduced packet builds and benchmark verdicts were not rerun here.
No worktree, code, database, issue body, service or server was changed. No pull, migration, job, model call, service operation or request to 4007 was performed. The sole GitHub write for this re-audit is this comment.
Disposition of the first audit's six required changes
Answers to the original six audit questions, against the revision
1. Is the end state appropriate and are the shared seams complete enough?
Yes for preparing the persona plan. The revised list now includes provisioning/configuration, packet and reference validation, refresh authority, failure/recovery, reservations, the trusted human path and D8/D9. It explicitly distinguishes future persona prompt/run/ballot work from generic infrastructure, and removes human controls/no-dossier admission from the persona's own responsibilities.
The full MVP and satisfactory P6 re-audit remain prerequisites to their stated next steps. This issue's closure is not persona implementation permission. In §4, interpret “the other five pilot pages” as an inventory against all ten acceptance rows: five proposals and five forms do not necessarily mean five published openings. A dismissed proposal is evaluation evidence, not a public opening; an unprocessed page is not an “honest nothing.”
2. Are the scope moves sound?
The worker transfer and revised Health boundary are sound. The worker remains model-free on main. Moving the refusal and test to #264's new editor step is correct, and the revision now requires moving every contradictory #267 reference. Health's snapshot must stay independent of mutating service creation and of the unbuilt review allocator.
The former P3 gate waiver is withdrawn, correctly. However, the newly promoted parallel P3 path needs more integration ownership than
components/opening.exalone; see required addition R1.3. Are parallel builds and merge/deployment order safe?
Conditionally yes. #264 is explicitly disabled/stubbed; both sessions have independent partitions; rebased integrated review/precommit is mandatory. The original literal shared files remain refresh_worker.ex and health_live.ex, with the former transferred wholly to #264. The revised manifests must be checked again after Stage 0.
The two-PR deployment sequence is now coherent: #267 code without a migration, then a compatible #264 migration before #264 code. Reversing remote merge order would still not inherently break a correctly disabled/stubbed implementation, but it is outside the chosen reviewed sequence and complicates the deployment boundary.
Optional P3 can add commits/migrations to the same main history, so “deploy #267” must identify an exact compatible commit, not simply advance to whatever GitHub main currently contains. Required addition R2 closes that remaining ambiguity.
4. Are the nineteen corrections now sufficient?
The issue no longer claims they are. That is the right correction. The ancestry CHECK, recaptured parent on same-generation retry, immutable lifecycle, Take uniqueness/provenance, out-of-cut kept items/cap, frozen reference reconstruction, review reservations, Publish bypass and abstention contract are now named Stage 0 deliverables.
They are not solved by naming them. The current #264 body still asks for operations incompatible with main; its old warning comment still gives the serial dependency. Stage 0 must replace those instructions, regenerate both file lists/tests and get its independent check. This re-audit does not tick that checkbox.
Do not force an unnecessary fixed implementation from the wording “separate published-parent from version ancestry”: the checked requirement is truthful admitted-published-parent identity, valid version lineage and a deliberately compatible CHECK/API contract. The design should state exactly which fields carry each.
5. Are O1–O5 safe?
6. Are gates or steps still missing?
The major prior omissions are now present. Two bounded integration requirements remain for Stage 0:
Required additions to the design/deployment contract before Stage 1
R1 — P3 must integrate the complete source-record-work path, not only the public tile.
#254 P3 explicitly adds newly pinned source-record works to Candidates. On audited main, Packet's work path still assumes catalog works:
spec.catalog.manifest/checksum/identity;source_record_revision_id;Consequently, a new Candidates work containing a source-record revision without a catalog reference cannot simply flow through the present Packet implementation: construction can raise on missing catalog, and the probe cannot reconstruct the intended source-record reference. Refresh.inputs itself builds Packet, so this affects freshness as well as eventual proposals.
This is a static integration finding, not a live reproduction: I did not create a pin or run new code. It does not block Stage 0 or the two generic build sessions if P3 remains isolated.
Add to Stage 0/P3's dedicated brief: owners and tests for Candidates, Packet build/freeze/verify/probe/summary, proposal reference reconstruction, PublishedReader and the work tile, plus the pin-revision/retirement effects on freshness and D8. Either deliver these compatibly together before pins become offerable, or keep that new offering gated until they are ready. This is integration of the existing P3 requirement, not permission for a new matcher or cut-policy change.
R2 — pin deployment commits and gate the whole deployed history.
Record the exact #267 deployment SHA/schema prerequisites. While #264 is merged but held back, any later P3 commit on main may be its descendant. Deploying that P3 head by advancing the shared checkout would also deploy #264 before Stage 3b.
Therefore specify: no deployment of a head containing #264 until #264's compatible migration is complete; P3 has its own schema/code compatibility and owner-approval gate; final integration checks cover the actual head being deployed. Parallel build permission is not independent deployment permission on one linear main checkout.
This does not require changing the chosen #267 → #264 order. It makes its existing “DO NOT deploy” rule enforceable when the optional third build is used.
Recommendations, not new blockers
Ranked remaining risks and smallest safe sequence
Smallest safe next action: start Stage 0 now. Resolve and rewrite #264/#267, include R1/R2 if P3 proceeds alongside them, and obtain the independent check of those actual resolved briefs. Then follow the revised disabled parallel builds → integrated review → pinned #267 deployment/window → approved compatible #264 migration → #264 code → separately approved configuration/manual/proposal steps → five forms → satisfactory P6 re-audit. Full MVP acceptance still precedes persona implementation.
No additional suite, model run or live activation is needed to start that design work.
holden commentedon Oct 26, 2026
Stage 0: output ready for its independent check (26 October 2026)
Stage 0's design session has finished. #264's body is now the resolved contract (§4 rules R1–R19, §5 schema and migration table, §7 regenerated files, §8 a 36-test matrix each tied to its rule, §10 Delivery B as Stages 3b–3e), and #267's body is reconciled with §6. A Stage 0 comment on each lists what changed and the audit point each change answers (#264's, which also quotes every replaced section verbatim; #267's). Nothing was built, started or written beyond those two bodies and three comments. No build session should start until the independent check is posted and its required changes are applied.
Basis.
mainat9ccc427(Studio checkout andorigin/mainagree; no #264 or #267 worktree or branch exists). The v2 catalog read withdefault_transaction_read_only=on: every curation CHECK, unique index and trigger body named in #264 §3 and §5 was read frompg_constraint,pg_indexesandpg_proc, and the rows from SELECTs; bench attempt 59 confirmsPacket.summary/1storesexcerpt_sha256and nowords_sha256. Not done: no test suite (a design session), no packet build (love's cut counts are the audits'), no process or listener check.What Stage 0 settled, in one line each (the rules are in #264 §4):
parent_version_idstays version history (one line; the shape CHECK untouched); the published parent captured at admission lives on the newcuration_proposalsrow, null when nothing was published; Take's parent is the proposal.proposal:<composition>:<configuration version>:<generation>; the parent, model config and packet hash are frozen per generation; a deferred retry keeps its generation only if the pointer has not moved and its attempt is absent or answered (changingrefresh.ex:364); drift or an answerless attempt opens a new generation.ready?/1named), activation as today (love's version stops standing and is re-published in the same sitting), enablement a separate switch that a new activation invalidates.words_sha256added to the summary; drift refused.proposed,abstained,no_changewith the enum, CHECK and disclosure changed together; 48-hour window.service_unreachableand its test moved to Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264; the Health card SELECT-only and absent-data safe, inference minutes only, no stop history; the live order fixed; the sharedhealth_live.exinterface agreed (three lines per issue). After regeneration,health_live.exis the only file both briefs touch.The re-audit's required additions. R2 (deployment pinned to commits) is in #264 §10 3b and §11 and #267 §9: #267 is deployed by fast-forwarding the Studio checkout to its recorded merge commit; no head containing #264 is deployed before 3b; a later P3 commit has its own compatibility check and yes, and waits for 3b if it descends from #264's merge; integrated checks run on the exact head deployed. R1 (P3's source-record works) is recorded for P3's future brief, with #264's side fixed: #264's writer accepts only the catalog work shape
Packetbuilds onmainand refuses any other (:unsupported_work_reference), so a pin cannot reach a proposal until P3 extendsCandidates,Packet(build, freeze, verify, probe, summary), the proposal reconstruction,PublishedReaderand the tile together, with the pin's revision and retirement effects on freshness and D8.For the check, and for a future P3 issue: the
components/opening.exboundary. #264 edits only the disclosure (about/1,assessed/1, the selected-by and attempt lines). The highlight tiles (highlight/1for works,work_title/1) and the source-record work path above are P3's; #264 does not touch them. The re-audit's ten-page acceptance inventory (§4) is #268's, not #264's: five proposals and five forms are not five published openings.Timing note on 3c-5. "Enable the fenced proposal path" stays step 5, but #264 takes it at the start of 3d's window, after the service is up, so that no visit meets an enabled editor while the service is down.
Housekeeping left to the owner. #254's P6-0 and P6 checklist lines still say the corrections are carried by #267 (Stage 0 may not edit #254). #264's earlier comment was left unedited; the new comment replaces its rule explicitly. #264's body is about 62,600 characters of GitHub's 65,536, so the check's changes there need to stay concise.
Owner decisions Stage 0 could not settle from the specification
Each has the default #264 uses (marked OD-n in its body) and what follows from it.
origin/attempt_id, the freshness table and the D8 marks, "nothing else". #253's own rules (§6a dismissal and supersession, §7's 30 review units, §10's per-item form, §5a step 5's attribution on Take) and #268's separate enable step need more.curation_proposals(lifecycle and form),copied_from_item_idon items,review_unit_reserved_aton refresh rows, the enable columns on the configuration,kindon profiles, three outcome values.sourcesrow (a bot actor must have a source, one bot per source), and the home page prints the count of all sources ("27 sources so far").generic-editor, kindbot, inactive; #264 excludeskind: :botfrom the home count (one filter inhome_live.ex)./on/love. Avoiding it would need a carry-over feature #253 does not authorize.last_completed_at").service_unreachablewith backoff and fill the Stale tab. Neither proposes between windows.Next: the independent check of #264 and #267 as now written.
holden commentedon Oct 27, 2026
Independent check of Stage 0: #264 and #267 against
mainand the v2 catalog (27 October 2026)This is the one independent check #268 §5 requires before any build (#269's D1). I did not write Stage 0. I checked the rewritten #264 and the reconciled #267 against the code and the catalog, not against their own prose.
Verdict: GO for Stage 1 builds, once required changes 1–6 below are applied to the two bodies as written. These are text changes only. Applied verbatim they need no further check; anything beyond them does. Not GO for any live step: 3a–3e each keep their own owner's yes. Overall grade: B+ (A− with the changes). The contract is accurate about
mainalmost line by line, and its migration is backward compatible. But two of its rules would fail in use. "Request a proposal" never reaches the editor on a page that has already been checked, which would stall 3d. And once any proposal exists, the owner's Publish of their own unchanged version is refused.LeadPolicy.statement/2(it isstatement/1).git pull", which contradicts R2 (required 3).words_sha256is where Stage 0 says it is./ops/healthdoes not have (required 5).Evidence and limits
/Volumes/LLM Models/dictionary/src/dictionaryis onmainat9ccc42748284a2610d45509aba6c8b1a157ecf46, equal toorigin/main, with a clean working tree.7693849764459364596, PostgreSQL 18.2, port 5434. Every connection todevils_dictionary_v2anddevils_dictionary_runtime_benchran withPGOPTIONS='-c default_transaction_read_only=on', confirmedon.pg_constraint,pg_indexesandpg_triggerfor the 14 tables §3 and §5 rely on, andpg_get_functiondeffor the 14 functions behind their triggers. Also\dof the configuration, source and refresh tables, and the columns ofcurator_profile_versions,inference_attempts,inference_ledger_entriesandinference_services.quotation:3), 1 review, 5 receipts, 1 activation, 27 sources (nonebot), 5 profiles and 0 profile versions, and 0 model configs, services and attempts. Refresh row 1 is idle, generation 3, token 4,needs_editor/fingerprint_version, due 28 Oct 13:59:58 UTC. Oban hasRefreshWorker3 completed. Bench attempt 59's summary keeps a sense quotation'sexcerpt_sha256and nowords_sha256.refresh.ex(admission, claim, check,outcome/3, complete, fail, fences, release, defer, triggers, suppress, reopen, published, counts) andrefresh_worker.ex. Alsoconfigurations.ex,compositions.ex(create_version/3,not_duplicate/4,note/2,one_display_identity/1),curation_live/editor.ex(held/2,publishable/3,write_version/2),curation_live.exrecord/1,packet.ex(candidate,freeze/1,summary/1),gateway.ex(service!/1,admit/3,budget/2),readiness.ex,runtime.ex,endpoint.ex,publications.ex,reviews.ex,standing.ex,lead_policy.ex,health_live.exand its test,home_live.ex,sources.ex/source.ex,router.ex,proxy_guard.ex,installation/bundle.ex,dd.runtime.ex,pilot.ex,config/config.exs(Oban) andconfig/dev.exs(DD_DATABASE).mainhas not moved since the first audit's independent run at this SHA (2,986 tests, 0 failures, seed 86311), and that result is historical, not repeated here; this check is of a design. I built no packets: love's 10 of 32 and the other cut counts are the audits'. I executed no Elixir, mix task or worktree, made no request to 4007, and started no service. The only GitHub write is this comment.What holds, verified against
mainand v2refresh.ex:364recaptures the parent on a deferred retry;act(:recover)keeps generation and parent;fenced/3,still_configured/2andsuppress/1are as described, with a 10-min running lease, a 15-min queued lease and 3 recoveries. Also:ready?/1ismanifest["mode"] == "manual"and is called byresolve_default/1andcurrent/1;create_version/3(compositions.ex:273) parents to the newest version;note/2is at:546andheld/2ateditor.ex:383.Packet.summary/1is at:1098, andwords_sha256is on the candidate at:631–643.service!/1inserts (gateway.ex:34),Readinessreaches it (readiness.ex:58), andbudget/2defaults through it.Published.current/1usesRepo.get!(published.ex:68), so the deployment hold is real. Every DB object in the table exists with the quoted body.attempt_id, human authors and notes,selection_origin = 'manual'. The new restrictions fall only on rows no code onmainwrites; nonote_author_kind: :modelwrite exists. The constraint triggers that also fire onUPDATE,curation_configurations_receiptandeditorial_compositions_receipt/_scope, compare the pointer, scope and receipts only, so enable and mark updates pass them. The old Ecto schemas select their own fields. The FK targets(id, configuration_id)and(id, composition_id)already have unique indexes.sources.kindis anEcto.Enumthat already includes:bot,:middleand:static, and has no DB CHECK.mix dd.bundleis a fullpg_dumpwith a catalog-driven comparison, socuration_proposalsis captured and compared without a code change.Gateway.admit/3would refuse:idempotency_conflict) and no row stuck in one state. R5.4's exits match every code path that moves a row:complete/3,fail/3→defer!,act(:recover)→defer!after three expiries,release!(also fromin_flight_elsewhere/2andstill_configured/2) andsuppress/1. The 120 sdeadline_mssits inside the 10-minute lease, and Oban'sLifelinerescues after 30 minutes, longer than the lease. The advisory class 264 does not collide withRefresh's 259.editorial_composition_reviews_guardandeditorial_composition_publications_authorityare the only acceptance and publication choke points, and §5 narrows both. A model note in a manual version can only arrive through the copy branch, whichcreate_version/3never sets.freeze/1hashes the packet's canonical JSON, so a rebuild on unchanged inputs gives the same hash, and any other hash is drift. The DB already requireswords_sha256on a sense-quotation item and exactly one revision form on a work.health_live.ex(runtime card first), SELECT-only reads and "none" on empty data.inference_ledger_entries(kind,day,amount_ms) lets the snapshot sum the day's minutes withoutbudget/2.service_unreachablementions arerehearse's own refusal (test 2) and pointers to Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 (D-F, §6 Out, §8 note).refresh_worker.exis listed as not touched.enablemoved to the start of 3d, as Curation: the next stretch to the agents — #267 and #264 in one audited order, deployment gates, and "ready to prepare the persona plan" (under #254, #253, #193) #268's timing note allows. Re-audit R1 is covered by R7.4's:unsupported_work_referenceand §7'sopening.exboundary. R2 is in Curation P6: the first bot proposes into the owner's screen — attempt to proposal, Take, Edit, Dismiss, the quality form, D8 marks and the D9 attempt audit (under #254, #253) #264 §11 and 3b.3 and in Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 §9. Everymix dd.runtimecommand and flag in Curation P6-0: the editor runtime made live — one model, where it lives, the v2 binding, the benchmark GO and a rehearsal against the real pages (under #254, #253, #193) #267 §3.3 exists. OD-9's replacements are on the pilot allowlist (pilot.ex:16).Required changes (to the bodies, before any build session starts)
Characters: #264's body is 62,621 of 65,536; changes 1–4 and 6 add about 1,280 net, leaving it near 63,900 (about 1,600 spare). Each block below is the exact text.
1. #264 R18 and test 34: a request must reach the editor.
outcome/3answers{:unchanged, "unchanged"}whenever the stored fingerprint equals the new one, whatever the pending reason (refresh.ex:613–620), and R3.1 completes an unchanged outcome "exactly as today". Every page in 3d will normally have a stored fingerprint by then: love from the first visit after its 3c re-publication, and war, hope, truth and coward from their firstnothing_acceptedcheck after 3c-4. Sorequest --slug lovewould completeunchangedand call nothing.R18, after "then admits as a visit would (
admit/2, every admission rule applying)." insert:Test 34, replace "admits one run; a second request" with:
2. #264 R13.2 and test 28: a proposal must not block the owner's own Publish.
publishable/3(editor.ex:530–535) publishes the held version only while it isCompositions.latest_version/1, the newest of any origin. Once any proposal exists, pending or dismissed (versions are immutable), the owner's held manual version is refused{:stale_parent, proposal}, and Save of the same arrangement is{:duplicate_version, id}(not_duplicate/4). The owner could not re-publish an unchanged version, for instance after a withdrawal and re-open (#269 W5).R13.2, after "while Save's
:expected_parentstays the newest version of any origin." insert:Test 28, replace "Publish never publishes the proposal," with:
3. #264 R19.2: deployment is the pinned fast-forward.
Replace "so deploying is a
git pulland one request, with no restart." with:4. #264 R6, R7.6 and R8.3: a merged arrangement the checks refuse.
R7.6 checks the merged arrangement against
LeadRule, the bound andone_display_identity/1, but R6 maps only an ineligible chosen item. Two cases slip through. A carried lead may no longer be the admissible lead. Or, on a fallback-lead page, the model's lead may equal a carried highlight, leaving no lead. Both repeat on every retry (same packet, marks and fixed-seed answer), so mapping them as "dirty" would re-run inference on every visit. None of the five pilot pages reaches them today, but the build must not improvise.R6, a new row after the drift row:
R7.6, after "A chosen item that is ineligible now closes the generation (R6)." add:
R8.3, replace "the model's highlights fill the remaining places in the model's order" with:
5. #267 §3.4 and test 4:
/ops/healthhas no reviewer gate.On
main,/ops/healthis in the:operatorlive session withProxyGuardonly (router.ex:115–117), andhealth_live_test.exsmounts it signed out. Making it reviewer-only would be a router change to an existing page that #267's §7 does not list.§3.4, replace "Reviewer-only, 404 through the tunnel like the rest of
/ops." with:§8 test 4, replace "it is 404 through the tunnel and requires a reviewer." with:
6. #264 §5: name the §6a parent reading as part of OD-1.
#253 §6a says the bot writes a proposal "with
parent_version_idN", N being the published version at admission. R9.1 keepsparent_version_idas lineage and puts N on the proposal row. That is the right design, becauseeditorial_composition_versions_shaperequires a parent after version 1 even when nothing is published. But #253 governs and is not amended, so the owner should take this reading explicitly.§5's first paragraph, after "the rest below is what §4's rules need, and is OD-1 on #268." add:
The owner decisions, OD-1 to OD-9
/sources/:slug(SourceLive) renders any source, so/sources/generic-editorbecomes a public page, andSources.list_sources/0also feedsmix dd.export.replaywithout a slug. Either 404kind: :botthere or record it.not_duplicate/4treats the same arrangement under a newer configuration version as a new version (compositions.ex:370), andheld/2will not hold version 1 once it no longer stands, so the screen's Save then Publish re-publishes love. The few minutes of honest-empty are real.stale_parent). (e) matches Curation agent MVP: what an editor does, what a curated entry contains, how the page looks, how the owner and the bots share one record, and how it stays current (under #193) #253 §7.request(required change 1) or the 48-hour window.Recommendations (not required)
Publications.publish/3andwithdraw/3lock the composition and then update refresh rows (Refresh.published/2,suppress/1), while P5'scomplete/3locks the refresh row first. The step's write takes both, so state "composition first, then the refresh row" in R9. Otherwise a publication landing during the write can deadlock: one side aborts, and nothing is lost.curation_configurationstrigger: fire only wheneditor_enabled_version_idchanges, soactivate/4(which leaves it in place, R1.5) is untouched.editorial_composition_versions_dedup_index. Either add amatches_manualcase to R8.4 or name the refusal.LeadPolicy.statement/1; there is nostatement/2.ready --smokeon v2 also inserts the import actor "Curation runtime operator (CLI)" (dd.runtime.ex:414). v2 has none today, so list it.Applying changes 1–6 to the bodies and recording each owner decision on this issue is the driver's work under #269. This check does not tick #268's Stage 0 box itself.
holden commentedon Oct 27, 2026
Stage 0 check: required changes applied to #264 and #267 (27 October 2026)
The check's required changes 1–6 are applied verbatim, with no other text changed:
The six recommendations are not applied. Each stays on the check comment for the build sessions and their reviewers.
The Stage 0 box in §10 is left unticked for the owner. The owner's decisions OD-1 to OD-9 come next. Each will be recorded here individually, with the check's notes on OD-1 (it also covers change 6), OD-2 (
/sources/generic-editorwould become a public page, and the bot source would feedmix dd.export.replay) and OD-5 (it works only with change 1).holden commentedon Oct 27, 2026
Owner decisions OD-1 to OD-9, recorded 27 October 2026
The owner answered each decision separately, in chat with the #269 driver session, after the Stage 0 check and its applied changes. Each question carried the check's notes. None is a blanket acceptance of the defaults. #253 is not amended by any of them.
curation_proposals,copied_from_item_id,review_unit_reserved_at, the enable columns, profilekindand three outcome values. #253 §6a's "parent_version_idN" is stored ascuration_proposals.published_parent_version_id, andparent_version_idstays lineage (the check's change 6).generic-editor: kindbot, inactive. The home page's count excludeskind: :bot. Accepted as known effects, with no code change:/sources/generic-editorbecomes a public page, and the source is included inmix dd.export.replay./on/loveis accepted.merge_refusedrow and themax_highlightscap.With D1 applied and D2 recorded, #269 W1 (#267 Delivery A, partition
_cp60) and W2 (#264 Delivery A, partition_cp6) may be proposed as build sessions. Neither authorizes a live step.holden commentedon Oct 27, 2026
O1 taken (27 October 2026). The owner decided P3's two rules, recorded on #269 as D3 (comment). First, the pin is the poem-to-page relation. Second, the owner declares a successor: a changed PoetryDB text withholds the published item
:revision_supersededonly once the owner declares it the successor, until a version pinning the new text is published. #253 is unchanged.holden commentedon Nov 1, 2026
Closed 1 November 2026 into #298. §3 items 1 and 5 are proven, 2 is tested for crash and offline and partly observed live, 3 and 4 were superseded by the 29 October amendment, 6 is satisfied by the later audits. Its end state, 'ready to prepare the persona plan', is overtaken by #275's single-curator work and now by #298 §5 C4–C5.