Status: reference page, a dated snapshot of the facts as read up to 2 October 2026, 00:55 BST (the commit follows the read, and nothing after it is reflected), read at origin/main 85a5472 (2 October, 00:32 BST). That main carries wave 1b's three test-only stabilisation merges (d1da83e, 9651734, 85a5472) on 3121bdd, which merged IP1 (pull request #64), on d73b06e (1 October, 16:36 BST), which merged the reviewed independent-adoption stack (draft pull requests #11–#54, by integration pull request #61; follow-up issues #55–#60 and #63). The handover and the canonical Notion record own changing status; this page owns the order of the remaining work and the evidence for each row's status. Sonnet 5.5 (claude-sonnet-5-5) refreshed it from Opus 5.5's 16:00 BST snapshot (read at c27b643, itself built from the 29 September consolidation, consolidation/roadmap.md) against origin/main's history and files, the merged pull requests and open issues, the worktrees, the archive and the owner's answers, merge instruction and acceptance decision of 1 October (OD-A to OD-H, under "Recorded, not on main"). The progress doc was last re-read at revision 25 earlier on 1 October, when none of its five decisions was set; it was not re-read for this refresh, so it may still show decisions the owner has since answered in the coordinator session. Archive paths are relative to <local evidence archive>. Each lane's own spec stays authoritative for detail. Nothing here is started, adopted or granted unless its status says so, and a merged candidate is not an accepted Module or Workflow. All 27 customer-value epics and the eleven adoption epics (E28–E38) stay open, and no status claims release or customer value. Row numbers are those of the previous refresh, so row 3 (IP1, now in Done) is absent; cite IDs, which are stable.
Status words. done (SHA): on origin/main at that commit. merged, not accepted (SHA): on origin/main as an integrated local candidate. Fable's advisory acceptance review ran and the coordinator decided to accept all 24 stack families as local infrastructure (issue #63, 1 October, 23:53 BST), but the acceptance receipts and status wording are not on main, so main does not yet record it as an accepted Module or Workflow. done, not on main: finished work whose product is not a commit (CX0's source retrieval); it appears under "Recorded, not on main" with its evidence. in flight: committed or drafted on a branch or draft pull request and not on main, or a lane opened with nothing committed yet. blocked: waiting on a named external or owner input; nothing proceeds until it arrives. held: an owner hold; nothing proceeds until the owner reopens it. recorded: an owner decision, an external event, a reviewed design or an archive record, with no commit on main; it appears under "Recorded, not on main", never under Done. planned: not started. not planned: the owner has decided against it for now; kept for provenance. design in review; not adopted. An owner item is open until the owner answers.
Why this order. The owner's bet for the Factory (consolidation/trajectory.md) gives two measures, drawn from the owner's words and accepted with the bet on 1 October (OD-D): owner minutes and asks fall (KR1), and broken builds are caught and put right (KR2). Relief comes first, then the instruments that measure relief, then the machinery that removes the cause. On 30 September the owner added a second axis: every Module and Workflow must be adoptable on its own, and the Factory composes them through the same contracts (independent adoption; the adoption programme owns E28–E35's outcomes and estimates). Dependencies decide the rest.
Verification. AGENTS.md rule 3 on main: the implementer never verifies its own work; Opus 5.5 implements and Astra (gpt-6-astra) verifies independently. For 30 September only, the owner allowed Astra-only independent reviews across the Codex coordinator's continuation (.intent/tasks/codex-continuation.md): first for continuation/P4 and continuation/P8 only (9355778, 13:27 BST), then across the whole continuation (1d3717c, 15:14 BST, "superseding the earlier P4/P8-only exception"); the Knowledge draft was excluded. Most rows marked done on 30 September were accepted under that exception and have no Fable review. Until the evening of 1 October the Claude coordinator's lanes, this page included, were to be accepted only when a fresh Fable 5.1 reviewer and Astra both passed; the owner then changed who accepts (OD-H, about 23:45 and 23:50 BST): the Claude Code coordinator is the acceptance reviewer and decides, and Fable review is still wanted but advisory. AGENTS.md rule 3 on main has not been edited to say so. For the merges pending on the evening of 1 October the owner set a different gate at about 23:00 BST (OD-G): "use fable on xhigh for secondary review and then when you're happy get it merged", that is an Opus 5.5 primary review, a Fable 5.1 (xhigh) secondary review, then the coordinator's own judgement, with the coordinator alone merging. It replaces an Astra round for those merges and is not Astra acceptance. During the stack review on 1 October Fable was unavailable (the Codex coordinator recorded Fable review as blocked by authentication), so the owner had Opus 5.5 (xhigh) review all 31 stacked pull requests in stack order and the whole stack, and put the Claude Code coordinator in charge of merging until the Factory can; it merged them at d73b06e. Those reviews let the stack merge. They are not Fable acceptance. Fable's advisory acceptance review of the 24 merged families ran at 23:52 BST and issue #63 records the coordinator's decision to accept them, with the acceptance receipts still to be made (CXS-F). The owner also keeps the Claude CLI unavailable (OD-A): the Factory's own model roles do not use it.
Keys
- IDs. An ID prefixed
continuation/is a task of the Codex continuation (.intent/tasks/codex-continuation.md):continuation/P2is the plain-style pass in Done. A bareP2is the delivery task of the archive's roadmap (producer composition, row 63); the two are different tasks. IDs from the archive'sproduct-design-scope/roadmap-todos.mdare kept; its row number is shown as (n). Prefixes:- FB- = the Factory bet (
bets/factory/bet-proposals.md): FB-Q1, FB-H1–FB-H7. FB-H7r is H7's register, before its rollouts; FB-CMD is the Factory commands the bet modules need; FB-H6 is restore's diagnosis and prepared owner steps, FB-H6L its execution under a grant. - TB- = the Tally bet: TB-N1–TB-N4, TB-M1 (instrumentation), TB-P1 (privacy), TB-B1 (brief). TM-T triages Tally's findings that TM does not carry.
- WI1 and WI2 = work items, stages 1 and 2 (the owner's request of 2 October); WI1-register and WI1-lanes are WI1's two parts, WI1b to WI1d its follow-ups, and WI2b is stage 2's optional model similarity.
- CF1–CF7 = the Cloudflare adapter's C1–C7 (
service-access/cloudflare/cloudflare-adapter.md§7). C1 was the Claude audit lane (C1-6, C1-A, C1-T, C1-D, C1-R7, C1-S); it is not planned since 1 October (OD-A). CFA moves the Factory to its own Cloudflare account. - W2-R = the owner's deploy route; W2-G = the guarded deploy step; W2-F = Fable's review of the Codex coordinator's commits of 29 September; W1-E = the website's completion evidence; EV2 = catch-up receipts, beside EV1's reviews and rows.
- SA-OP and SA-HA = the owner-presence and high-autonomy designs; GH-W = the GitHub write route for granted Actions; CX0 = the Codex source for L7's audit (done, OD-E).
- E28–E38 = the eleven adoption epics on
main(docs/epics.json); E36–E38 (issues #20–#22) came in with pull requests #28 and #29 of the merged stack. - CXS = the Codex coordinator's stack of 30 September–1 October (pull requests #11–#54), merged on 1 October at
d73b06eas a candidate, not accepted (CXS-A: the E28, E29 and E34 work and the packaging; CXS-B: planning, provider and correction work beyond E35; CXS-C: the branches built on the stack, not onmain; CXS-F: its follow-ups and acceptance); KN0 = the Knowledge design draft; IN12 = the 29 September owner directions as an intent revision; DX-R = the remaining Diátaxis work after7fd968d. - OD-A–OD-H = the owner's answers and instructions of 1 October (OD-G is the merge gate; OD-H is the acceptance and shipping decision). IP1 = per-task model priority lists and provider-neutral declarations in Intelligence. DOA = Discovery's scans and synthesis on OpenAI through
codex-cli. W2-H = HTTPS and HSTS for both public sites. - V1 = "The production line" explainer; V2 = product walkthroughs (was (71)). CO = cloud orchestration. DOC-R = the documentation round (PD0, RM1, DOC1). PD1 = the progress doc's asks in one place. AST–AST3 = the owner's verification decisions.
- Tally maintenance findings keep their run-1 IDs under
tally/(for exampletally/C1). The lifecycle signatures are L-S1–L-S7; the Tally bet's questions aretally-bet/Q1–Q12.
- FB- = the Factory bet (
- Lanes.
- The Claude coordinator's open lanes, read at 00:55 BST on 2 October:
roadmap(this page),deploy-sites(W2-G, built; awaiting its merge reviews),claude-audit(C1; parked, not planned) anddelivery-merge(superseded: R1, R3 and R4 reachedmainas ports,06d1c10and3122534). - Merged lane:
intelligence-priority(IP1;factory/intelligence-priorityatdb04abd(23:47 BST), merged as #64 at3121bdd, 00:24 BST on 2 October; the worktree stays). claude-ship(claude/ship-1b, at85a5472): the integration worktree that put wave 1b onmainat 00:32 BST.- Nineteen
claude/w1-*andclaude/w2-*lanes, opened fromd73b06ebetween 23:40 and 23:53 BST (worktreesclaude-w1-01-claude-deadlinetoclaude-w2-19-cf1; planclaude-pr-review/2026-10-01/build-plan.json, 23:39 BST; run stateclaude-build/STATE.md). Three,w2-01tow2-03(#57's test-only stabilisation of provider-event tests), reachedmainas wave 1b. The other sixteen each had commits by 00:47 BST, none pushed or onmain: #57's deadline fixture and Guidance shards (w1-01,w1-02), the CI storage preflight with CI1's portable files (w1-03), the Branch health mirror pin (w1-04), test pins (w1-05,w1-06,w1-08,w1-12), the Producer pin evidence (w1-07), the owner-digest commands (w1-09), the eight-value Guidance rehearsal command on a journal copy (w1-10), #59'sScheduleErrorre-export (w1-11), FB-H7r's register (w1-13), the receipt drafts census (w1-14), capacity headroom (w2-16) and CF1 (w2-19). Their review rounds are recorded underclaude-build/and were not read for this refresh; none is accepted. - A website refresh on
claude/exciting-planck-smrrd0(ed6a9a0at 23:52 and0fe7f2eat 00:06 BST, pushed toorigin, not onmain; no review of it was read). - The Codex coordinator owns the main checkout and its own worktrees:
codex-cloudflare,delivery-d4(D4),docs-four-types(factory/knowledge-plan, KN0) and theadoption-*,provider-*,milestone-*,research-job-*and correction worktrees of CXS (the stack is merged; the worktrees stay while its later branches use them). - Planned lanes:
lifecycle,design,strategy,growth,website(a refresh is already onclaude/exciting-planck-smrrd0),codex-audit(L7);tally(Tally's own repository, only under a Tally grant);archive(design only);owner.
- The Claude coordinator's open lanes, read at 00:55 BST on 2 October:
- Fixtures now? yes: can start today, on fixtures or docs. after deps: once its dependencies land. doc: design, spec or review only. no: live: needs a live service, grant or real data. no: owner: an owner action.
Done
| ID | Item | Lane | Status |
|---|---|---|---|
| L0, L1r, L2r, LM (1–3) | Lifecycle increments 0–2 (lifecycle-schedule on a fake clock, discovery-sources on a loopback corpus) merged into main | lifecycle, coordinator | done (217887b, 469bc56, 978d6a2; merged at 21bb146) |
| D1–D3b | Step 1 increments 1–3b: Repository Assurance, Product gate and records, collector, guard seam; composed into nothing | delivery | done (d64f5ea, 120b767, 11ec8e1; on main since 985b5f9) |
| SA1 (23) | Service access increment 1: names-only catalogue and reference map, on test-made fixtures; Astra's sweep findings fixed (29adb73, e81d4d7) | service-access | done (4bf1fa6, merged at 2101d4d; repairs integrated at e6b33cf, receipt docs/service-access-r3-receipt.json) |
| SA1-F2 | Organisation-owned repositories: a secret not conclusively listed at organisation level is unknown, never absent; the spec's §3 and §5 step 5 amended | service-access | done (87f86fd, a6fce3b; integrated at ea7758e, recorded at 226b90f) |
| FB-H3 | Ask ledger, the first increment of M4 owner-policy: records asks and stated rules, applies none; no live asks recorded | ask-ledger | done (e95ea6b; integrated at 272a868, receipt docs/owner-policy-receipt.json) |
| FB-H1, FB-H2 | branch-health (read-only GitHub watch on recorded and adversarial fixtures) and owner-digest (cited exception batches, a 150-word digest, a read-only GET /api/digest and Digest page); no live read, schedule or delivery | branch-health | done (integrated at be776a0; receipt docs/branch-health-continuation-receipt.json) |
| IR, R13 (9, 30) | The README's Intelligence section renders only participating declarations, with headroom; the produce-admission key accepts the gate's own produce: shape | coordinator | done (41b6910, 9ce3f24; integrated at 964b5fe, receipt docs/intelligence-layout-receipt.json) |
| FB-CMD | npm run factory:bet: one GET-only health poll and owner-ledger records against an existing journal (command guide); nothing live was run | branch-health, ask-ledger | done (f68c744, receipt docs/factory-bet-commands-receipt.json) |
| R1, R3, R4 (15, 17) | Observability catalogue; Repository's shared wire grammar and private validation patterns in the gate and records (R4's Astra finding, recompilable patterns, closed); old recipe pins refused, never rewritten | coordinator (ports of factory/delivery) | done (06d1c10, 3122534; receipts docs/delivery-core-integration-receipt.json, docs/observability-catalogue-receipt.json) |
| R2 (30) | Structural module-graph checks; no runtime change | coordinator | done (291056f, receipt docs/module-graph-receipt.json) |
| R8 (16) | Guidance command namespace guidance- | coordinator | done (053b53d, receipt docs/project-guidance-namespace-integration-receipt.json) |
| TOOL1 | scripts/receipt-check.ts and scripts/readability.ts as tested repository tools | coordinator | done (0d13a42; accepted at cf9ac3a) |
| continuation/P2, continuation/P3, continuation/P5 | Plain-style pass on docs/design.md, docs/values.md and docs/lifecycle.md (the owner's request to remove machine-sounding wording); copy lint and focused module guides | coordinator | done (a056645, c64f42e) |
| DOCS-T | Every authored document classified as tutorial, how-to guide, reference or explanation in docs/documentation-map.json; one owner per topic; a fixture tutorial; navigation by reader need | coordinator | done (7fd968d, 8bedc04; receipts docs/documentation-types-receipt.json, docs/documentation-types-followup-receipt.json) |
| ADP | The owner's decision of 30 September: Module → Workflow → Factory, independent adoption for existing and planned parts (project intent r11, P-S11 and P-C21); E28–E35 planned at 17–31 increments, low confidence | owner, coordinator | done (9927368, c27b643) |
| CIc, CI0 (14) | CI on the private origin; full root and dashboard checks run on pushes to main on the dedicated bravo-mini runner, the recommended default of the progress doc's decision 1 (its pick-list is still unset); runs 36738013911 and 36740595689 passed | coordinator | done (179da9b, ba5f1f0, f1051ce, 3a5b72c); of the runs since, those at 7f2f9c4 and d73b06e failed (see the merged stack), the run at 3121bdd was cancelled by the next push, and run 36941478221 at 85a5472 (00:34 to 00:53 BST on 2 October) passed |
| W1 (12) | Website, built locally (Astra r2 PASS). Its fresh browser check, both module pages, receipt and build-review row are W1-E | website | implemented locally (66f66d3); completion evidence pending (W1-E) |
| IP1 | Per-task model priority lists and provider-neutral declarations in Intelligence: a task can name models at a priority, so arbitrary providers can be declared and put in, and Discovery's scans and synthesis can move off Claude (OD-B). Owner request of 1 October. Declarations only; no model call | intelligence-priority | done (9fd1080, cb45e4a, 5a96159, db04abd; merged at 3121bdd as pull request #64, 00:24 BST on 2 October; plan revision 2; round 1, Astra at 22:45 and Fable at 22:54 BST, FAIL on the same two independence defects, dispositioned at 22:56 BST; at 5a96159 the Opus 5.5 primary and Fable 5.1 xhigh secondary merge reviews under OD-G PASS, at 23:16 and 23:21 BST; db04abd, after both reviews, records that gate in the receipt, the build-review row and the status lines and restores the two lifecycle-adversarial tests the reviews noted; receipt docs/intelligence-priority-receipt.json; intelligence-priority/) |
| CXS-F: #57, first slice | Wave 1b, test-only stabilisation of provider-event tests under issue #57: the provider Guidance tools matrices sharded (cd00dce), the provider-subscriptions late-callback race removed (92ba0ac, 1b40c47) and the notification-ownership process matrices sharded (e5c54f6), with no timeout raised | coordinator (Claude lanes w2-01 to w2-03) | done (merged at d1da83e, 9651734 and 85a5472, 00:32 BST on 2 October; Opus 5.5 and Astra passed them and Fable's advisory verdict was ship, per #57's comment of 00:36 BST; #57 stays open) |
| CXS-A, CXS-B (merged part) | The independent-adoption stack, pull requests #11–#54 incl. #49: the E28, E29 and E34 packaging and contracts, E36–E38 planning, the MCP event, subscription and proposal-ownership work, the Verification workflow design and four correction fixes (table below) | Codex coordinator (built), Claude coordinator (merged) | merged, not accepted (d73b06e, PR #61; Opus 5.5 merge reviews; Fable's advisory acceptance review and the coordinator's decision are in issue #63, receipts not made) |
| W2 | Public website and docs at plumbfactory.fyi and docs.plumbfactory.fyi, live since 29 September, 21:18 BST, as static assets on two Workers in the owner's Cloudflare account, by the owner's decision of 29 September. Directory routing, 404 pages and safe headers followed (9df0ab8, accepted at 5235f88); the publication then passed 207 live checks (codex-continuation/current-handoff.md). The five Codex commits of 29 September (9163f21, d439c16, c98a655, 8782002, e1c4d6e) have Astra PASSes in the Codex lane (the records are listed at W2-F) and no Fable review (W2-F) | Codex coordinator | done, live; W2-F and W1-E open |
The merged stack (CXS-A and CXS-B)
Pull requests #11–#54 (31 of them, #49 a sibling) were stacked drafts, each merged into its stacked base. Integration pull request #61 merged the whole stack into main as one --no-ff merge at d73b06e (1 October, 16:36 BST), so every stacked SHA below is an ancestor of main. Never squash or rebase-merge stacked work: the packaged distribution pins commit 27f0dcb. Opus 5.5 reviews: 28 merge with follow-ups, one merge (#51), two fix before merge (Material Timing's reason split in #35 and the planning docs' stale "unmerged" wording in #29), both fixed; the whole stack aligned with follow-ups (claude-pr-review/2026-10-01/). Each integration commit was independently reviewed (pass with notes). Status of every row: merged, not accepted: Fable's advisory acceptance review ran at 23:52 BST (claude-pr-review/2026-10-01/fable-acceptance.json: one ACCEPT, #49, and 23 ACCEPT-WITH-FOLLOW-UPS, no blocking defect) and issue #63 (23:53 BST) records the coordinator's decision, as the owner-designated acceptance reviewer (OD-H), to accept all 24 as local infrastructure, with its new follow-ups; the acceptance receipts and status wording are not made and none is on main, so each row stays merged, not accepted until they land. Each draft's *-draft.json stays its evidence, and all 38 epics stay open. Follow-ups are issues #55–#60 and #63 (CXS-F); older issues #41, #42 and #45–#48 stay open. Between c27b643 (run 36752654236, 30 September) and 85a5472, CI on main did not pass: run 36883101755 at 7f2f9c4 failed one timing-sensitive test (process group: a grandchild in the group ends with the stopped CLI and the group is empty; 1,601 of 1,602 passed; issue #57), and run 36886006843 at d73b06e failed twice: attempt 1 (16:39 BST) passed 2,124 of 2,132 tests, its eight failures timing-sensitive child-process and packed-consumer tests in issue #57's scope; attempt 2 (17:44 BST) ended in npm run check with SQLite disk I/O error and No space left on device on the bravo-mini runner; the portable job stays skipped (CI1). Run 36941478221 at 85a5472 (00:34 to 00:53 BST on 2 October, after wave 1b) then passed, the first full-suite pass since c27b643; the run at 3121bdd was cancelled by the next push.
| PR | Item | Group | Merged at |
|---|---|---|---|
| #11 | Standalone CommandJournal distribution | CXS-A | 0b5ea49 |
| #12 | Execution, scheduling and model policy modules | CXS-A | 503fbef |
| #13 | Project guidance independently adoptable | CXS-A | 38261e6 |
| #14 | Neutral Attention and Owner digest contracts | CXS-A | e92b959 |
| #15 | Adoption inventory and refactor estimates | CXS-A | 1a39c50 |
| #16 | Confined executor outside Factory | CXS-A | 5eb8631 |
| #17 | Guidance history kept across the eight-value migration | CXS-A | 71f5b43 |
| #18 | Owner policy with caller-owned storage and clock | CXS-A | dcff926 |
| #19 | Guarded fixture resources | CXS-A | c7fe3bb |
| #23 | Repository collection and Assurance for external hosts | CXS-A | cc33044 |
| #24 | Branch health independently adoptable | CXS-A | 55dfbf5 |
| #25 | Discovery and Service access independently adoptable | CXS-A | 4139e32 |
| #26 | Repository, Product gate and Delivery records for external hosts | CXS-A | cbf7966 |
| #27 | Bounded Producer contracts and adapters | CXS-A | 2380995 |
| #28 | Plan for independent dates, capacity and stage triggers | CXS-B (adds E36) | 53527bf |
| #29 | Plan for operational Signals and production repair | CXS-B (adds E37, E38) | 2573f51 |
| #30 | Digest health validation and private package adoption | CXS-A | 8b629e6 |
| #31 | MCP Events design with Factory admission and Intelligence | CXS-B | bc032e4 |
| #32 | Caller-owned Dashboard and date planning as private modules | CXS-A | 20aa589 |
| #33 | Committed Factory facts projected for MCP event adapters | CXS-B | 2e1e182 |
| #34 | Capacity forecasts and authenticated operational signal intake | CXS-B | 79a734d |
| #35 | Passive material timing with pinned calendar rules | CXS-B | 6e18d5c |
| #36 | Bounded MCP event subscriptions with signed verification | CXS-B | 543167c |
| #37 | Bounded proposal ownership with permanent first-offer retention | CXS-B | 0cc00ff |
| #38 | Original-generation Guidance acceptance | CXS-B | 7f89d28 |
| #49 | D4-owned Verification workflow design (sibling of the stack) | CXS-B | 0798394 |
| #50 | Fulfilled native receiver data observed without changing commit outcomes | CXS-B | 18bd84e |
| #51 | Current Journal schema validated before write configuration (issue #39 closed) | CXS-B | cf816de |
| #52 | Private fence temporary name cleaned after catchable errors (issue #40 closed) | CXS-B | 25b2345 |
| #53 | Event methods and Guidance tools with notification ownership | CXS-B | 0df9769 |
| #54 | Dashboard journal contention identified without retrying commands | CXS-B | 6c167dc |
Recorded, not on main
Owner decisions and external events that no commit records, reviewed designs and records in the archive, and work finished in a lane but not yet on main. None of these is done: each cites its evidence instead of a commit on main, and none is adopted.
| ID | Item | Lane | Status |
|---|---|---|---|
| OD-A | The owner kept the Claude CLI unavailable (1 October): the Factory's model roles do not use it, there is no Factory Claude profile, and audit trust assumptions O2–O7 are not accepted. Every Claude-transport item moves to "Not planned"; the claude-audit commits stay on factory/claude-audit, not on main | owner | recorded (owner answer in the coordinator session, 1 October; no commit) |
| OD-B | For Discovery's daily and weekly scans and its weekly synthesis, which can no longer run on Claude: switch to Codex, and add to Intelligence a way to give models at a priority for certain tasks, so arbitrary providers can be put in. Becomes IP1 (priority lists, done at 3121bdd) and DOA (discovery on OpenAI through codex-cli, after L7) | owner | recorded (owner answer, 1 October; no commit) |
| OD-C | Paid extra usage on the owner's ChatGPT account is off: the owner's answer of 1 October, "Yes, it's off", to an option that read "I record it as your dated confirmation. It goes stale after 30 days or after any sign-in change". The dated owner-ledger record belongs to L-S1 and has not been made; the coordinator makes it from this answer, with no new question to the owner, and it lapses on 31 October 2026 or at any sign-in change | owner | recorded (owner answer; L-S1's record still planned) |
| OD-D | Tally's bet and the Factory's bet accepted with all recommendations (1 October). For a broken Product build the Factory prepares each restore within the hour and the owner runs it; after five clean restores on a Product it offers a limited, revocable grant. Tally run 1 decisions 2–7 accepted (read as the report's defaults; the owner's answer is the record). Acceptance records the decisions: no grant, credential, store submission or Tally change follows from this page, and each keeps its own step and gate | owner | recorded (owner answer, 1 October; no commit) |
| OD-E | The Codex CLI source download approved (1 October) and done: see CX0 | owner | recorded (owner answer; CX0 below) |
| OD-F | Always Use HTTPS, plus HSTS for six months on both sites, plumbfactory.fyi and docs.plumbfactory.fyi, without subdomains or preload, then a check that http:// redirects: approved (1 October); waiting on the owner's Cloudflare sign-in: see W2-H | owner | recorded (owner answer; W2-H blocked) |
| OD-G | The merge gate for the work pending on the evening of 1 October: an Opus 5.5 primary review, a Fable 5.1 xhigh secondary review, then the coordinator's own judgement; the coordinator alone merges. Cited by the IP1 merge reviews (intelligence-priority/opus-m1.md, fable-m1.md). It replaces an Astra round for those merges and is not Astra acceptance | owner | recorded (owner instruction in the coordinator session, about 23:00 BST; no commit) |
| OD-H | The acceptance and shipping decision (about 23:45 and 23:50 BST on 1 October, said to the Claude build session and recorded in claude-build/STATE.md): "you are the acceptance reviewer, I authorise full shipping, we're still mvc so we can move fast and break things to fix later", then "don't wait for ci so just ship and we'll fix forward. We do want fable review but you are decision maker". The Claude Code coordinator accepts and merges reviewed work; Fable review is advisory. That session read it as commissioning #55's test-only stabilisation (wave 1b, now on main), the eight-value Guidance live save after a rehearsal and a backup, and the first live read-only poll; this page records no live save or poll as run. It answers W-17's question of who accepts; it does not edit AGENTS.md | owner | recorded (owner words relayed in claude-build/STATE.md; no commit) |
| CX0 | The Codex source for L7's audit, retrieved on 1 October at 16:31 BST after the owner approved the download (OD-E): openai/codex tag rust-v0.159.1 (commit dd48cd3, Apache-2.0; tarball SHA-256 beginning 656cafb9, full value in PROVENANCE.txt) at <local volume>. Nothing was built or run, and the audit itself is L7, still planned | coordinator (for codex-audit) | done, not on main (a cache directory with PROVENANCE.txt; no commit) |
| W2-R | The owner's deploy route (29 September, 20:01 UTC): Workers with static assets through cf, guarded to the two named Workers (W2-G); later a Factory-only account (CFA) | owner | recorded (owner decision; no commit) |
| CFI | Cloudflare's cf installed with the owner's yes; the factory profile signed in with Workers permissions | owner, coordinator | recorded (owner action and external state; no commit) |
| DOM0 | plumbfactory.fyi registered by the owner: 1 year, auto-renew off, expires 29 September 2027 | owner | recorded (external event; no commit) |
| AST, AST2, AST3 | Verification decisions: Fable interim while Astra was out (29 September, 17:24 UTC); Astra back beside Fable (19:05 UTC); Astra-only reviews allowed for 30 September across the Codex continuation (recorded at 9355778 for P4 and P8, widened across the continuation at 1d3717c) | owner | recorded (owner decisions; the commits record only AST3) |
| TR1, SPECS | Tally run 1, five Opportunities rejected at G1 (discovery/tally/2026-09-29/); designs passed by Astra (growth r3, service access r5, Cloudflare r2, refactor r4, Diátaxis r4, extension, epics and intent proposal r3, both bets r3) | archive | recorded (archive records and reviewed designs); none adopted |
Now
Work that is moving this week, and the blocked items that hold a place in the order. The Codex coordinator's work on the stack (CXS-C) runs in parallel; nothing in it waits on the Claude coordinator's rows.
| # | ID | Item | Lane | Depends on | Owner decision | Fixtures now? | Status |
|---|---|---|---|---|---|---|---|
| 1 | FB-Q1p, PD1 | This week's asks, prepared and in one place: the red-build session (Family Watch's step rerun; JustSpeakToIt's reconcile log re-read), each item's read-only recheck and Q1's minutes as the first KR1 datum. In the progress doc, the decisions the owner has not answered (its decisions 2–4 and the discovery models are answered in OD-A to OD-C; decision 1 rests on its default) and the asks below in one list with a link; nobody sets the owner's pick-lists for them | coordinator | — | — | yes (read-only; doc) | planned |
| 2 | RM1 | This page: refreshed on 2 October, with facts read up to 00:55 BST, to main at 85a5472 and the owner's answers, merge gate and acceptance decision (OD-A to OD-H); receipt docs/roadmap-refresh-r10-receipt.json | coordinator | the owner's merge gate (OD-G) | — | doc | in flight (factory/roadmap; rounds 1–3 failed one or both reviewers; the Opus 5.5 primary and Fable 5.1 xhigh secondary merge reviews FAIL twice, each time on facts that moved after the page's read: those of the round 3 commit (consolidation/refresh-1oct/opus-m1.md and fable-m1.md, 23:38 to 23:40 BST) on stale IP1, CXS-F, CXS-C and CI rows and the unrecorded merge gate, and those of the next commit (opus-m2.md, fable-m2.md, to about 00:51 BST) on IP1's head, the owner's acceptance decision, Fable's acceptance review and the nineteen Claude lanes; this revision re-reads every row at 85a5472 and dates the snapshot to the read, not to the commit; a fresh pair of reviews under OD-G pending) |
| 4 | W2-G | The guarded deploy step: each site through cf under the factory profile, a hard-coded allow-list (plumbfactory-website, plumbfactory-docs, both domains) checked before every call, a stale or untested build refused, HTTPS checks afterwards. Built with a fake cf; deploys nothing until both reviewers pass it. Pinned cf 1.0.0-beta.5 cannot list Workers routes, and cf 1.0.0-beta.10 (checked at 18:05 BST, publish/deploy-step/cf-beta10-check.md) cannot either. On 2 October 2026 the owner removed the route-check requirement rather than make every deploy manual (W-15), so the step does not read routes and the residual is accepted as the how-to's "Not established" states it; adoption is read again before each deploy (Astra w3 finding 2, Fable w3 finding 1) | deploy-sites | W2 (live) | the route (W2-R) | yes (fake cf) | built on factory/deploy-sites with the route reading removed (rounds r1, w1, w2 and w3 failed one or both reviewers before the owner's decision of 2 October, publish/deploy-step/); awaiting the merge reviews; it deploys nothing until a live run is commissioned |
| 5 | W2-H | Always Use HTTPS, plus HSTS for six months on both sites, plumbfactory.fyi and docs.plumbfactory.fyi, without subdomains or preload, then a check that http:// redirects, approved by the owner on 1 October (OD-F) | owner, coordinator | W2 (live) | approved; the owner's Cloudflare sign-in (W-16) | no: live | blocked (approved; waiting on the owner's Cloudflare sign-in; nothing changed) |
| 6 | CXS-F | Follow-ups of the merged stack and its acceptance: issues #55 (provider events: hosting, tracking, consumer), #56 (outcome-honesty gaps in the package contracts; first), #57 (timing-sensitive tests), #58 (one Promise-observation helper), #59 (neutral package contracts), #60 (docs and code readability), #63 (new follow-ups from Fable's advisory acceptance review); the acceptance receipts and status wording for each merged draft (decided in #63, not made). Eight-value Guidance's first save is a live, irreversible journal append; the Claude build session reads OD-H as allowing it after a rehearsal on a journal copy (lane w1-10) and a backup, and no save is recorded | Codex coordinator, coordinator | the merged stack (done) | #55's decisions (W-17) | yes | in flight in part (issues open; the Codex coordinator triaged all six in issue comments, 16:40–16:48 BST on 1 October; its corrections for #56 (storage refusal cd49810, product Attention isolation 03fa3d7, collector resource drift 292eb22, the owner digest's future polls dca6c23), #57 (package-consumer isolation c1097f4, 6fcc763), #58 (native rejection reasons 54630de) and #59 (symlinked script entry 8373784) are in draft pull request #62, each independently reviewed in the Codex lane (continuation-review/issue-triage-2026-10-01-new/: c1097f4 REVISE, corrected by 6fcc763; the rest PASS within their scopes), none on main and none reviewed for merge; #55 has triage comments and its test-only stabilisation, which reached main as wave 1b (Done), and #60 has triage comments only; the Claude coordinator's lanes also work on #57 (w1-01, w1-02) and #59 (w1-11's re-export), on branches and not on main; Fable's advisory acceptance review ran at 23:52 BST and issue #63 records the coordinator's acceptance decision, with the acceptance receipts not made (see the merged stack); main's CI passed at 85a5472 after wave 1b (run 36941478221), having been red at d73b06e on #57 and runner disk exhaustion) |
| 7 | CXS-C | Work the Codex coordinator built on the stack before and during the merge, none of it on main: milestone objectives and the owner UI, passive provider diagnostics, a no-model Research job (branches milestone-*, provider-diagnostics-* and research-job-*). Its integration branch factory/milestone-dashboard-integration composed d73b06e at 70bcfa3 (17:31 BST) and is draft pull request #62 against main (opened 18:38 BST at 49d031d as "Draft for independent review; do not merge"; head 327810b (committed 21:47, pushed 21:58 BST), 21 commits later; its description, last edited 22:04 BST, has said "Keep this PR draft; no merges authorised for Codex" since 20:49 BST and has reported a failed current full check, 2,379 passes and 13 failures, since 20:58 BST, with "No full PASS claimed" and the combined outcome pending); #62 also carries CXS-F's corrections (row 6); each pull request needs independent review before the Claude coordinator merges it | Codex coordinator | the merged stack | each epic's adoption is a process step | yes | in flight (draft pull request #62 open, not reviewed for merge; its branch and the branches cut from it since (factory/issue57-distribution-isolation, factory/milestone-work-brief (created 18:28 BST from e71a33b), factory/issue57-installed-package-guard, factory/attention-product-isolation, the work-brief width correction, factory/collector-runtime-drift-design, factory/script-main-entry and factory/collector-resource-drift) descend from d73b06e; the branches built before the merge, and those cut after it from a pre-merge branch such as factory/milestone-research-identity-correction, do not; Astra-reviewed within the Codex lane, continuation-review/milestones/ and continuation-review/research-workflow/, the Research source "PASS within source scope" with package and combined qualification pending; no Fable or Opus merge review; wave 1b has since changed provider-event tests on main, and the overlap with #62's own #57 corrections is unchecked) |
| 8 | D4 (18) | Delivery composition bound to verify, with R7's read-only checkout Git; it admits only intents prepareIntegration returned. The D4-owned Verification workflow design (#49) is on main (0798394); D4 itself is not | Codex coordinator (delivery-d4) | R4 (done) | — | yes | in flight (42d2700, unaccepted draft; input-boundary corrections drafted, delivery-input-observation-correction and delivery-observation-traversal-correction) |
| 9 | W2-F | Fable's review of the five Codex commits of 29 September that W2 put on main (9163f21, d439c16, c98a655, 8782002, e1c4d6e): they have Astra PASSes in the Codex lane (publish/verify/codex-astra-r3.md for 9163f21, publish/verify/codex-astra-root-routing.md for d439c16 by scope, its pinned scripts/build-public.ts hash matching no commit, mobile-nav/astra-review.md for c98a655, and brand-integration/astra-review.md with its addendum for 8782002 and e1c4d6e; each reviewed the uncommitted change before its commit, so none names its SHA) and no Fable review, and no ledger row: provisional/ledger.md holds only the Claude lane's three Fable-interim rows of 29 September (SA1, R4, the public build; Astra pending). Anything Fable fails is fixed or reverted. Then one receipt of current bytes for any file they changed that no later receipt records, and a build-review row for each | coordinator | W2 (live) | — | yes (a review, then a receipt) | planned (not commissioned; Fable reviews ran in other lanes on 1 October) |
| 10 | IN12 | The 29 September owner directions (the bets, the Experience stage, service access with per-Product vaults, building everything into the Factory, Cloudflare and the public sites, cloud orchestration, owner presence and high autonomy, both reviewers) as an intent revision. The lane's intent r11 carried them as P-S11–P-S25, P-C21–P-C28 and P-R02–P-R05; main's r11 (9927368) uses P-S11 and P-C21 for independent adoption and does not carry them, so they need fresh IDs and their own review | coordinator | — | none: each is the owner's recorded direction | doc | planned (the lane's r11 text was set aside in this merge; consolidation/intent-r11.md keeps it) |
| 11 | DOC-R: PD0 (6), DOC1 | The owner's design decisions of 29 September in the extension spec, E-numbered epics and docs/design.md (Experience as the sixth domain, D16; the system proposes redesigns with concepts and the owner confirms, D17; defaults, D18); the doc-only drift in consolidation/alignment.md §2 and §6, including "Astra xhigh" in handover.md and docs/build-review.md beside the Fable reviewer | coordinator | IN12 | decided 29 September | doc (receipt-pinned files need a documentation receipt) | planned |
| 12 | SA-OP | Owner-presence approvals design (service-access/owner-presence/), asked for at 19:15 UTC on 29 September: steps that need the owner present while away; presence once, then a dated, revocable per-Product delegation; approval items in the ask ledger. Grants nothing before adoption | service-access (design) | SA1 | adoption, once it passes (W-14) | doc | held by the owner after round 7 (owner-hold.md, 18:00 BST: rounds do not resume until the owner reopens it; W-14); design in review; not adopted (Astra FAIL in all seven rounds, round 7 at 17:24 BST on 1 October; Fable PASS in r3 and r5, FAIL in r1, r2, r4, r6 and r7, round 7 at 17:40 BST: routine renewal still needs the owner at the Mac, and a link can reach the phone before any check; round-7 findings not dispositioned) |
| 13 | SA-HA | High-autonomy design (service-access/high-autonomy/), asked for at 19:23 UTC: account creation, terms and spend automated inside an owner-signed policy, with budgets, a kill switch and a report after each act; limits no policy lifts. Unsigned, every class stays at "prepare" | service-access (design) | SA-OP | the amendment's signature (W-14) | doc | design in review; not adopted (Astra r4 and Fable r4 FAIL, 30 September; no round since; held with SA-OP by the owner's hold of 1 October) |
| 14 | KN0 | The Knowledge design draft on factory/knowledge-plan (52096ff), awaiting a Fable and Opus review before any implementation; the Astra-only exception did not apply to it | Codex coordinator | — | — | doc | design in review; not adopted |
| 14a | WI1 | Work items, stage 1 (the owner's request of 2 October): one register of work per Product across coordinators and dispatched agents, Claude, Codex or any other; a claim that duplicates open or recently merged work is refused by fixed scope-overlap rules unless a declared comparison, a follow-up or an open takeover allows it; merged, superseded and stale lanes reported per Product with evidence and a proposed action, never deleted; npm run factory:work. Two reviewed parts: the register, then the lane reports. First fixture: the seven lanes left open from 29 September to 2 October. Follow-ups: WI1b, the package entry and external consumer; WI1c, lane findings for Attention, the Dashboard and the owner digest; WI1d, lifecycle stages claim before they create work | coordinator (work-items) | — | the claim rule in AGENTS.md and the live register's location | yes | in flight (row added 2 October, after this snapshot) |
Next
On fixtures, in order, as Now's items are accepted.
| # | ID | Item | Lane | Depends on | Owner decision | Fixtures now? | Status |
|---|---|---|---|---|---|---|---|
| 15 | FB-H1L, FB-H3L | The first live poll of all six Products, GET-only through npm run factory:bet under the owner's commission, agreeing with a manual read-only check in the same hour; the same day, the coordinator records the progress-doc and chat asks in the ledger with their original dates. Asks dated before the first channel list neither freeze KR1's windows nor count as a fall when withdrawn | branch-health, ask-ledger | FB-H1, FB-H3, FB-CMD (done) | W-1's gh commission | no: live (read-only) | planned |
| 16 | FB-H4 | Blocker classes, M5: each owner unblock records its class, cause, runbook and a recheck 14 days before expiry; a repeat commissions automation. Seeded by Q1's recheck; built on the Portfolio blocker facts H1 writes; its runbook half after SA3 | ask-ledger | FB-H3 (done); W-1's outcomes | — | after deps | planned |
| 17 | FB-H5 | Owner rules, M4 owner-policy: Factory-drafted wording the owner confirms, a check before any ask in a ruled class, the one-tap "should have asked me" that demotes a rule, quarterly re-validation. Owner-scoped, dated, never inferred | ask-ledger | FB-H3 (done); live after FB-H3L | each rule is the owner's (E23) | yes | planned |
| 18 | LS-R | Generalise the lifecycle-schedule rhythms: H1's 30-minute poll, H2's batches and digest, quarterly notes and design reviews under one Factory scheduler, the L-S6 runner; the module is pinned, so it needs its own receipt | branch-health | FB-H1L | the LaunchAgent load (L-S6) | yes | planned |
| 19 | MRG0 | Symbol anchors instead of file:line anchors in test/intelligence-lifecycle-adversarial.test.ts and docs/lifecycle.md, so later merges need no anchor edits | coordinator | LM | — | yes | planned (docs/lifecycle.md still uses file:line anchors at 85a5472, two of which IP1 re-anchored; the test file's anchors were not rechecked) |
| 20 | CI1 | Add the lifecycle, discovery and intelligence-lifecycle tests to the portable list. The full suite already runs on the Mac runner (CI0); the portable Linux lane stays off while hosted minutes are blocked by billing (GITHUB_HOSTED unset), and the Factory never changes billing | coordinator | CI0 (done) | — | yes (config) | in flight (lane claude/w1-03-ci-storage, two commits, head ba603c2 at 00:18 BST: the CI storage preflight, so a full runner disk reads as no verdict, with CI1's portable files in its first commit b3e3764; not pushed, not on main) |
| 21 | FB-H2L | First live batches and Monday digest: batches as a local macOS notification from the polling runner, the digest on the dashboard; email or Slack later, through SA7. Until it is live, the coordinator's Monday update follows H2's format, labelled hand-written | branch-health | FB-H1L, LS-R | the channel (W-2) | no: live | planned |
| 22 | FB-H7r | Prevention register, M3's first part: guardrail templates and presence reads, no grant. First templates: a dispatcher circuit breaker (Pasta's 264 failed bot-dispatched Alpha builds on one head); self-hosted runners on public repositories (Tally, Pasta; tally/X4); scheduled workflows disabled for inactivity (tally/C1) | branch-health | FB-H1 (done) | — | yes | in flight (lane claude/w1-13-prevention-register, three commits, head 28af1f6 at 00:43 BST; not pushed, not on main) |
| 23 | FB-H6 | Restore, M2's first part, first on software-factory: diagnose from H1's episodes (culprit evidence: the failure reproduced on the suspect and absent on its parent) and prepare the owner's steps within the hour: a pause, a rerun, a targeted revert on culprit evidence, otherwise an investigation. Reads and prepared steps only | branch-health | FB-H1L, FB-H4 | — (answered: the Factory prepares each restore within the hour and the owner runs it, OD-D) | after deps | planned |
| 24 | SA-IO | Interface-order revision of the service-access spec: every runbook step names its interface (agentic CLI, official API, classic CLI, browser last, owner-supervised) and why; adds the configure purpose | service-access | SA1 (done) | each agentic-CLI step runs under the owner's sign-in | doc, then after deps | planned |
| 25 | SA3 (27) | Registration runbooks, per-step checks and owner blockers | service-access | SA1, SA-IO | — | after deps | planned |
| 26 | L4c (36) | owner-decisions core: typed answers and the weekly bundle, carried by H2's digest; reads H5's rule store before asking | lifecycle | FB-H3 (done), FB-H5 | — | after deps | planned |
| 27 | AG-scope (50) | Action gateway scope: record before dispatch, reconcile by key, grants per Action class, Product and blast radius. Enforces nothing until AG is built and accepted | coordinator | — | scope commission, at the first live grant it gates | doc | planned |
| 28 | L3b (8) | Minimal Objective and Capability records; records Tally's Objective in the owner's words (D19) | lifecycle | LM | software-factory brief (L-S5), at L8 | after deps | planned |
| 29 | LC1 | One maintained lifecycle spec: fold the growth revision's delta and the extension's §6 into docs/lifecycle.md | coordinator | PD0 | — | doc (pinned: documentation receipt) | planned |
| 30 | BX0 (19) | Terms (bet, Key result, Experience, risk class); planned declarations product-strategy, experience, design-review; one canonical stage list for the docs, the website and V1 | design | PD0, LC1 | — (decided) | after deps | planned |
| 31 | X2 (20) | sf-design/1: a principles-and-identity pin, the Factory's tokens first, and design code checks | design | BX0 | — | after deps | planned |
| 32 | X3 (21) | The dashboard Work view designed through X2; it cites the Factory's paper bet by digest | design | X2 (W-2 answered, OD-D) | — | after deps | planned |
| 33 | D5 (25) | Integrate, reconcile, inspect, export and observe, with R6's work trace | delivery | D4 | — | after deps | planned |
| 34 | B1 (22) | Metric catalogue and data-class register | strategy | BX0 | — | after deps | planned |
| 35 | B2 (26) | The bet record on 3b: the fields gates read, Key results as contracts or milestones, stop conditions, the learning plan | strategy | L3b, B1 | — | after deps | planned |
| 36 | SA4 (28) | Vault presence with a fake op, vault named sf-<productId>; every value-printing form refused | service-access | SA1 | — | after deps | planned |
| 37 | SA2 (29) | Read-only readers on H1's GET-only gh reader and R7's checkout Git; the live Tally map comes later | service-access | SA1-F2 (done), D4 | SA-1, at the live map | after deps | planned |
| 38 | CF1, CF2, CF3, CF4 | cloudflare/1 kinds and deny rules; a bounded Wrangler scanner; declarePresence and configure runbooks; the public-presence reader and renewal-due, first proved credential-free on plumbfactory.fyi | service-access | SA1; CF3 after SA3 and SA-IO; CF4 after SA2 | CF4: one account per Product (decision 2) | after deps | planned; CF1 in flight (lane claude/w2-19-cf1, three commits, head c96bff0 at 00:47 BST; not pushed, not on main) |
| 39 | L3 (24) | signal-intake and synthesis on a predetermined transport; deltas only. E37's operational intake (#34, CXS-B) is a candidate collaborator | lifecycle | LM | — | after deps | planned |
| 40 | D6 (31) | Delivery CLI, with R12's delivery ops log | delivery | D5 | — | after deps | planned |
| 41 | R11 (32) | Portfolio revisions: verification scope, usage-receipt/2 and unknown delivery authority | delivery | D6 | not a question | after deps | planned |
| 42 | R15 (33) | Product gate /2 design: owner kinds, budgets, times, service grants, the design precondition, the bet's restore grants | coordinator | D6 | — | doc | planned |
| 43 | L4 (36) | Opportunity gate with the awaiting-objective park, and run 1's G4 gap; typed dashboard decide, in one protocol bump with R10 | lifecycle | L3b, L3, R15, L4c | — | after deps | planned |
| 44 | B3–B4 (37, 38) | Stage frame, templates, parks and the bet item; Opportunity risks, a computable score, the roadmap and the backlog cap | strategy | B2, L4 | — | after deps | planned |
| 45 | SC1 | The step 1 spec's §4.1 gains round 5's scope rule | coordinator | — | — | doc | planned |
| 46 | D7 (34) | Independent review of step 1 increments 1–6 on the disposable proof | delivery | D6, SC1 | — | after deps | planned |
| 47 | D8 (35) | Live Slice run-briefing/1 into the Factory-owned store, with a delivery receipt | delivery | R8 (done), D7 | local authority (P-S07) | no: live (local) | planned |
| 48 | L5b (39) | outcome-validation with Key results as contracts; retirement detection | lifecycle | B1, L4 | — | after deps | planned |
| 49 | L5a (40) | growth on fixtures: voice from the bet, the tier rule, the go-to-market brief; E33's Marketing Workflow contract applies | growth | X2, B2, L4 | growth 15–22, at their first live use | after deps | planned |
| 50 | X4 (41) | Web design scenarios with axe, through a UI collector | design | X2 | Playwright and axe-core install (PD-25) | after deps and decision | planned |
| 51 | R10 (42) | Dashboard Work view built from X3's design, with R12's dashboard part | delivery | X3, R11, L4 | — | after deps | planned |
| 52 | X5 (43) | Design debt register, hard triggers and the whole-product review; every redesign it recommends goes to the owner as a proposal with concepts (D17) | design | PD0, L5b, X4 | — | after deps | planned |
| 53 | SA5–SA7 (44, 47, 48) | sf-product-gate/2; sf-confined-node-access/1, a loopback egress proxy; credential-broker with a synthetic provider | service-access | R15, D8; SA4 | — | after deps | planned |
| 54 | BX5, S3 (45, 46) | sf-slice/2 (Business rules, impact, risk class, design section); briefs consume the Guidance, bet and principles pins | design, delivery | X2, B2, SA5, D8 | — | after deps | planned |
| 55 | CF5 | verify-token/1 and read-config/1 recipes on fixtures | service-access | SA5, SA6, SA7 | — | after deps | planned |
| 56 | SA9 (49) | Grant anchoring and unattended brokered use; required before any unattended or mutating brokered use | service-access | SA7 | SA-8, SA-9 (an owner-run drill) | after deps | planned |
| 57 | AG (50) | Action gateway on fixtures: record before dispatch, reconcile by key | coordinator | SA5, SA7 | — | after deps | planned |
| 58 | S4 (51) | Collectors a real Slice needs; Capability disposition apart from health; improvement proposals as ordinary Slices | delivery | B2, D8, L5b | — | after deps | planned |
| 59 | OB1 (52) | Scope a per-Product obligations register | strategy | B2 | — | doc | planned |
| 60 | NX1 | How the owner's per-Product gates in Notion reach the Factory: an owner-sourced import or a read-only collector, before any onboarding | coordinator | — | the owner's read grant, per Product | doc | planned |
| 61 | R14, P2, R16 (53, 54) | Bound the producer's fingerprint read; step 2, producer composition into the Product gate; delivery activity facts into Portfolio as partial coverage | delivery | R3–R4 (done); D8; D6, R12, R10 | — | after deps | planned |
| 62 | EP1 (7) | Adopt the Experience and bet epics the 29 September design proposed (drafted as E28–E29 before main gave those IDs to adoption), under the next free IDs after E38 (E36–E38 are on main), with the Experience epic worded to D17, the P-C12 critique and independent review. Correct the progress doc's "E28–E31, 31 epics" | coordinator | PD0 | adoption is a process step (D18) | doc | planned |
| 63 | EP2 | Map the Factory bet onto epics: criteria on E07, E13, E23 and E27, or new epics (broken builds caught and put right; asked less over time) only if none covers them | coordinator | EP1 (W-2 answered, OD-D) | — | doc | planned |
| 64 | EV1, EV2 | Evidence catch-up: reference reviews where none is current, build-review rows for the dashboard brand increment, design language and CI, and new receipts of current bytes for accepted increments with none (Repository Assurance, the collector, the Producers implementation, the brand increment, design language, CI and the src/ files no receipt hashes); never backdated, no earlier hash rewritten | coordinator | independent review | — | doc | planned |
| 65 | W1-E | The website's completion evidence: both module pages, a receipt of current bytes, a build-review row and a fresh browser check; the same for the public build (scripts/build-public.ts: 8179246 with 9163f21 and d439c16; P4's routing has its own receipt) | website | W2-F; independent review | — | yes (local build) | planned |
| 66 | PF1 | A fresh Portfolio inspection of the six Products' checkouts (the Factory's recorded fact is d286844; main is at 85a5472), checkout facts only, run the same day as FB-H1L | coordinator | — | — | yes (local inspection) | planned |
| 67 | DX-R (78) | The remaining Diátaxis work. 7fd968d classified every document, added the map, a tutorial and how-to pages and reader-need navigation outside the archived step plan (DX0, DX1, DX2–DX9, DX10–DX13 and DX14–DX15, docs-diataxis/migration-plan.md); its unfinished steps (the builder page types, records section, build review as a ledger, agent pages, landing pages, guardrails) are re-scoped against what landed before any further step | coordinator | — (was MRG1, not planned) | at the people's module pages: how Plumb's traits relate to the values | doc | planned (steps 0–1 superseded in part by 7fd968d and TOOL1) |
| 67a | WI2 | Work items, stage 2: duplicated work and existing capabilities across Products found deterministically (shared capability and dependency keys, module and file signatures, the same CI fix), each with a shared-library proposal carrying its evidence, the affected Products, cost and benefit, a versioning and adoption path, and licence and language fit. The Factory never extracts: each extraction or adoption is delivery work under each affected Product's grant. Model-assisted similarity is a later optional Intelligence declaration (WI2b) | coordinator | WI1; live use once a second Product's register holds items | each extraction under each affected Product's grant | yes (synthetic Products) | planned (row added 2 October, after this snapshot) |
R6, R7 and R12 are built inside D5, D4, and D6 with R10. R9 stays cut, as the refactor plan decided.
Later
Live, then measured; future designs. The adoption composition epic E35 follows E28–E34 (its proofs combine theirs).
| # | ID | Item | Lane | Depends on | Owner decision | Fixtures now? | Status |
|---|---|---|---|---|---|---|---|
| 68 | L7 (57) | codex-cli audit, transport and qualification; OpenAI moves to codex-cli (lifecycle decision 3) | codex-audit | CX0 (done) | L-S1's dated record that paid overage is off for the ChatGPT account (the owner stated it off on 1 October, OD-C; the record is still L-S1's); L-S3, L-3, L-4 | no: live | planned (the source is retrieved, CX0; the audit has not started) |
| 69 | BX8 (58) | Model tasks: design section, triage, critiques | design | X5, S3; live after L7 (DOA's transport); the design section named FQ, which is not planned, so it has no transport until one is chosen | — | after deps | planned |
| 70 | DOA | Discovery's daily and weekly scans and weekly synthesis on OpenAI through codex-cli, because they can no longer run on Claude (OD-A, OD-B). Models are chosen through IP1's per-task priority lists. Own qualification; no model call until it is commissioned | lifecycle, codex-audit | L7, IP1 | L-S1's record for the ChatGPT account (OD-C is the statement only); L-S3 | no: live | planned |
| 71 | GH-W | The GitHub write route for granted Actions (PB1's pull requests; FB-H6L's disable, enable and rerun): per Product, least-privilege, never the owner's ambient gh sign-in; brokered (SA7), anchored (SA9), recorded by AG and reconciled from a GET-only read-back | service-access, coordinator | AG, SA7, SA9 | each Product's credential and grant | after deps; then a live proof | planned |
| 72 | PB1 | Delivery to a Product's own branch under a granted Action: pull requests into a protected main. Chain: D8 + R15 → SA5 → SA6 → SA7 → AG → PB1 | delivery | AG, GH-W, D8 | each Product's first delivery grant (L-S7); main protection | no: live | planned |
| 73 | FB-H6L | Restore execution where the owner grants it: pause a runaway, re-enable, rerun a lone red, a targeted revert as a pull request into a protected main, through an accepted Action gateway | branch-health | FB-H6; AG; GH-W; PB1; R15, SA5; D8 | restore authority: the Factory offers a limited, revocable grant after five clean restores on a Product (OD-D), per Product and Action class | no: live | planned |
| 74 | FB-H7 | Prevention register rollouts, M3: each template rolled out one Slice per Product | branch-health | FB-H7r, FB-H6, S4, PB1 | each Product's grant | after deps | planned |
| 75 | TB-P1 | Tally privacy fixes before any read: opt-in web analytics, Do Not Track honoured, no diagnostics before consent, no entry or goal IDs in web events | tally | PB1, or owner-run; NX1 | tally-bet/Q12 (accepted, OD-D); a grant bounded to these fixes | no: live | planned |
| 76 | SA8 (59) | First live brokered read: PostHog aggregates for Tally, attended | service-access | SA7, TB-P1 | SA-5: an aggregate-only key once TB-P1's fixes are verified (run 1 decision 3, read-only aggregate counts, accepted, OD-D; no key exists) | no: live | planned |
| 77 | TB-M1 | Tally instrumentation: consented per-goal summaries computed on the device. KR1 and KR2 read "unknown" until it lands | tally | TB-P1, PB1 | tally-bet/Q4 (accepted, OD-D); G7 | no: live | planned |
| 78 | B9a (60) | The Factory's paper bet recorded unchanged, or as the owner's revision, before its live discovery | strategy | B2 (W-2 answered, OD-D) | the bet itself: accepted with all recommendations (OD-D); this row records it | doc | planned |
| 79 | L8 (61) | Live fetch and triage for software-factory, with a two-week shadow, after H3's baseline. E32's on-demand Research job (CXS-C, unmerged: in draft pull request #62; no Research-job file is on main at d73b06e) is the candidate Workflow, pending its own qualification | lifecycle | L3b, L3, DOA, B9a, FB-H3L | L-S1's schedule commission; L-S5; L-S6 | no: live | planned |
| 80 | L9 (62) | Live synthesis (weekly, on codex-cli through DOA, OD-B), gate and bundle; one admit into a Slice | lifecycle | D8, L4, B3, B4, L8, DOA | L-S7 | no: live | planned |
| 81 | TB-B1 | Tally's brief and allow-list redrawn from the bet; the Reddit API Source dropped until an approved app exists | lifecycle | W-2 (answered, OD-D) | Tally's L-S5; run 1 decision 2 (the brief and allow-list as drafted) accepted, OD-D | doc | planned |
| 82 | B9b (63) | Park re-run and the first quarterly note; Tally's bet recorded from the owner's answers; run 1's Opportunities re-run every gate | strategy | B9a, B3, L9 | — | no: live | planned |
| 83 | TB-N4, TB-N3, TB-N1, TB-N2, EX1 (64) | Tally nudges in order N4 (fair pace, if tally-bet/Q10 is yes) → N3 (one opt-in comeback nudge) → N1 (re-plan offer) → N2 (opt-in regularity); they supersede EX1's landing-page experiments if Q11's default stands | tally | X2, X5 or a manual design review, PB1, TB-M1 | tally-bet/Q9–Q11 (accepted, OD-D); G7 | no: live | planned |
| 84 | TM-T, TM | Tally triage, then maintenance Slices from run 1 (tally/C2–C6, D1–D2, R1–R2, X1–X2, and C1's keep-alive once W-1 re-enables the smoke tests); store listings untouched under the owner's release hold | coordinator, tally | PB1 (W-2 answered, OD-D) | Tally's delivery grant; tally/X3 (run 1 decision 7, OD-D, accepts the owner-only items as the report's defaults state them; no grant follows) | doc, then no: live | planned |
| 85 | X8 (66) | Identity census, then Tally's identity report and first whole-product review | design | X5, B9b | Tally read grant; walkthrough cadence | after deps, then live | planned |
| 86 | ON1 | Onboard Pasta, JustSpeakToIt, Family Watch and Focus Sentinel: a bet item, brief, guidance, restore choice, Notion gates imported, a vault when first needed | strategy | B9b; NX1 | each bet; the read grant | no: owner | planned |
| 87 | SA10–14, SAT, SA-R (67–69) | Launch kinds in interface order; the bounded-text output protocol; read purposes, aggregates first | service-access | SA3, SA4, SA-IO, SA7, SA8 | each registration is owner-executed | after deps; registration live | planned |
| 88 | L11a (70) | Live post-development: an owner-granted release and the first launch item in O mode | growth | L5b, L5a, L9 | release grant; the launch item | no: live | planned |
| 89 | CF6, CF7 | First live attended use (verify-read-token on a 7-day canary, then read-config); edit-dns/1 and deploy-assets/1, which adopts the two Workers and takes over W2-G's deploys through AG | service-access | CF5, SA8; CF4, SA9, AG, W2-G | the owner creates the token; the Action grants | no: live | planned |
| 90 | CFA | Move the plumbfactory.fyi zone and the two Workers to a Factory-only Cloudflare account; the owner creates the account | owner, coordinator | W2-G | when to move | no: owner | planned |
| 91 | V1, V2 (71) | "The production line" explainer, first as an Illustrative SVG animation from the brand tokens; product walkthrough videos later | coordinator, growth | BX0's stage list; W2, L5a for V2 | G-20, only if a video file is needed | yes (Illustrative) | planned |
| 92 | B6–B7, L11b, SA-F, L12, SA-L, SA-D (72–77) | Reviews, Buckets and unit economics once a Product exports a Metric; G mode per channel; flag access and the first communication experiment (E21); later credentials; deferred social channels | strategy, growth, service-access | L11a, AG, SA-R, SA9 | per channel and grant | no: live | planned |
| 93 | CO0 | Cloud-orchestration design: a control plane for remote workers that report back; tenants later. Opus and Fable co-design; Astra reviews | archive | — | the decisions it lists, then adoption | doc | in flight (design run started 1 October, 17:45 BST; cloud-orchestration/ holds design-fable.md (00:17 BST), design-opus.md (00:35 BST) and critique-fable-on-opus.md (00:49 BST), with no Astra review in it; not adopted; a candidate input for SA-OP's hold) |
| 94 | BP1 | Brand plate positions for modules with none; three new module portraits are pending (main's continuation integration) | design | the design system | identity is the owner's | doc | planned |
| 95 | DOM1 | plumbfactory.fyi renewal: CF4's renewal-due raises it from 30 August 2027; it expires on 29 September 2027 (auto-renew off) | owner | CF4 | renew, or let it lapse | no: owner | planned (dated) |
Not planned
The Claude CLI stays unavailable by the owner's decision of 1 October (OD-A). Each item below was a Claude-transport or Claude-audit item of the 16:00 snapshot. None is started, and none will be unless the owner reverses the decision. The factory/claude-audit commits (5079ccb, e3a1d04) stay on that branch, not on main. The rows are kept for provenance.
| ID | Item | Lane | Status |
|---|---|---|---|
| C1-6, C1-A (13) | Claude rules revision 6 (Astra rev6 r2 PASS); the Claude CLI completeness audit recorded complete: false (Astra r7 PASS on the reporting) | claude-audit | not planned: the owner keeps the Claude CLI unavailable (1 October); the work stays on factory/claude-audit |
| C1-T (13) | Static traces Tr1–Tr10 and a writable rerun of the 31 filesystem tests the sandbox blocked | claude-audit | not planned: the owner keeps the Claude CLI unavailable (1 October) |
| MRG1 | factory/claude-audit onto main with both reviewers and a new receipt (its delivery part is done, 06d1c10 and 3122534) | coordinator | not planned: the owner keeps the Claude CLI unavailable (1 October) |
| C1-R7 (13) | Claude rules revision 7 and its probe, then a re-audit towards complete: true; with C1-D (O1–O8) and C1-S (signing the audit) | claude-audit | not planned: the owner keeps the Claude CLI unavailable (1 October); O2–O7 are not accepted |
| L6 (55) | Claude transport extended to Sonnet 5, then qualified; two live calls of at most $0.50 each | claude-audit | not planned: the owner keeps the Claude CLI unavailable (1 October) |
| FQ (56) | Fable 5.1 transport change and its own qualification, for the brief's design task | claude-audit | not planned: the owner keeps the Claude CLI unavailable (1 October) |
| L10 (65) | Research profile: its own audit and qualification. A Research profile on codex-cli, if wanted, would be a new item; E32's Research job on the stack is separate | claude-audit | not planned: the owner keeps the Claude CLI unavailable (1 October) |
Waiting on the owner
Only the genuinely open questions. The owner's answers of 1 October (OD-A to OD-F; OD-G and OD-H are instructions, not answers) closed W-2 (both bets), W-4 and W-5 (the Claude audit) and W-7 (who restores a broken build), and the owner's hold of 18:00 BST put W-14 (owner presence) on hold; see the paragraph below the table. Of the progress doc's five decisions: the CI runner (1) is in use on its recommended default; the Factory Claude profile and the audit's trust assumptions (2 and 4) are answered, and the plan facts (3) are moot for Claude, with the ChatGPT account's overage stated off (OD-C) and L-S1's record still to be made; the discovery default (5) is answered for models (OD-B) and unset for the rest. The doc itself was not re-read (see Status). Defaults hold on fixtures until each remaining question is asked at its first live step; recommended defaults are in consolidation/owner-questions.md.
| # | ID | Item | Depends on | Default | Status |
|---|---|---|---|---|---|
| W-1 | FB-Q1 | Clear the red builds in one prepared session of about 20 minutes (Pasta, JustSpeakToIt, Family Watch, Tally's smoke tests, Focus Sentinel), and allow GET-only reads of the Products' CI, including the polls FB-H1L launches | FB-Q1p | reads: yes, GET-only | open (prepared; unanswered) |
| W-8, W-9 | G0, SA0 (10, 11) | Growth decisions 15–22 (progress doc decision 5 covers discovery defaults) and service-access decisions SA-1, SA-3 to SA-9, each at its first live step | — | defaults | open (defaults hold) |
| W-10 | L-S1–L-S7 | Lifecycle signatures at each step: L-S1's dated record of each subscription account's sign-in and disabled paid overage before the first provider contact (L7 or DOA; the ChatGPT account's overage is answered off, OD-C: the coordinator records that answer, with no new question to the owner, and it lapses on 31 October or at any sign-in change; the record is not yet made), its schedule commission at L8; then Codex, each brief (L-S4, the research profile, belonged to L10, not planned), the LaunchAgent, each first delivery grant | their items | — | planned |
| W-11 | DOM-V | If Cloudflare sent a registrant-verification email for plumbfactory.fyi, confirm it by 14 October 2026 | — | — | unknown |
| W-14 | SA-OP, SA-HA | The owner's hold on the owner-presence design (1 October, 18:00 BST): asked to accept the defaults (a Mac session about once per credential life) or a phone SSH path, the owner answered "Hold it we need to figure out a solution to this". Wanted: routine credential renewal that does not need the owner at the Mac; candidate inputs are CO0, vendor-issued unattended credentials and a hosted broker. Rounds resume only when the owner reopens the design; adoption and the high-autonomy signature are asked once each passes both reviewers | the owner reopening it; CO0 | none: both offered options declined; every class at "prepare" | held (owner, 1 October, 18:00 BST; service-access/owner-presence/owner-hold.md) |
| W-15 | W2-G | How the guarded deploy proceeds, given that the pinned cf (1.0.0-beta.5) and 1.0.0-beta.10 cannot list Workers routes and Astra requires a complete route listing before each deploy; the options are to accept a 15-minute reading window or to keep deploys manual (publish/deploy-step/cf-beta10-check.md) | — | W2-G is not blocked on this; it deploys nothing until a live run is commissioned; the sites stand as deployed on 29 September | answered, 2 October 2026: the route-check requirement is removed rather than making every deploy manual, and the owner accepts the residual as the how-to's "Not established" states it |
| W-16 | W2-H | Sign in to Cloudflare so the approved HTTPS and HSTS setting for both sites can be made (OD-F) | — | nothing is changed until the sign-in | open (approved; waiting on the owner's sign-in) |
| W-17 | CXS-F | The merged stack's open decisions (handover): provider events (#55: hosting, where the work is tracked, notification adapter rather than model transport; the reviews recommend freezing further hardening until one end-to-end slice exists); the instruction-file edits the safety classifier blocked (.intent/tasks/composable-adoption.md still says "stopped" and "no merge before review"; AGENTS.md still points to the old stop and resume note); the acceptance receipts themselves (Fable's advisory review and the coordinator's decision are in issue #63; the receipts are not made); service tokens for the O37.2 adapters, provisioned through the names-only Service access module | — | none set | open (per the handover of 1 October; who accepts was answered by OD-H) |
Answered or withdrawn: W-17's question of who accepts the merged stack was answered by OD-H (about 23:45 BST on 1 October). The CI runner (decision 1) is in use on its recommended default (CI0). W-2 (T1, both bets) was accepted with all recommendations, and W-7 (who restores) answered, on 1 October (OD-D). W-4 and W-5 (the Claude audit) fall away with the Claude CLI kept unavailable (OD-A). W-3, the Codex source, was the coordinator's task CX0 and is done (OD-E). W-6 (T0, Tally's report: its Objective) was answered (D19), its remainder folded into W-1, Q12 and the release hold; W-12 (publish the sites, with indexing) and W-13 (Astra usage) were answered on 29 September (W2, AST); the Astra-only day was the owner's own instruction (AST3).
Reading the order
- Broken builds (KR2): FB-Q1p → W-1 (with the
ghcommission) → FB-H1L → LS-R → FB-H2L. Then FB-H7r's register and FB-H6's prepared restores (after FB-H4); FB-H6L's execution needs an accepted AG, GH-W with SA9 and the owner's grant (the Factory offers a limited, revocable one after five clean restores on a Product, OD-D); FB-H7's rollouts need PB1. - Fewer asks (KR1): PD1 → FB-H3L (the opening backlog recorded; KR1's windows freeze at the first live ask) → FB-H5 → L4c → FB-H4's automation. L8 waits for H3's baseline. SA-OP and SA-HA would cut presence and spend asks only once adopted.
- Independent adoption: the merged stack (CXS-A: E28, E29 and E34; CXS-B: E36–E38 planning, provider and correction work, and #49's Verification design) is merged but not yet recorded as accepted: issue #63 records the decision to accept it, and the acceptance receipts are not made. E30–E33's Workflows and E35's composition proof are not in it; E32's Research job is on CXS-C branches, in draft pull request #62. The order stands: E28 first, then E29–E33, E34 after E29, E35 last. Next: CXS-F, then a re-estimate. New and changed Modules meet the adoption gate before they are offered; local acceptance alone is not adoption proof.
- Merges: the Claude Code coordinator merges reviewed work to
mainuntil the Factory can (the owner's 1 October decision, with Opus 5.5 reviews in place of Fable while Fable was unavailable for the stack review); the Codex coordinator's later branches (CXS-C) are retargeted tomainby hand; the first, draft pull request #62, is open as a draft and not reviewed for merge (its own description says to keep it draft). At about 23:00 BST on 1 October the owner asked for this push to be merged after an Opus 5.5 primary review and a Fable 5.1 (xhigh) secondary review, at the coordinator's judgement (OD-G); at about 23:45 and 23:50 BST the owner made the coordinator the acceptance reviewer, with Fable advisory and no wait for CI (OD-H; see Verification). IP1 merged at3121bdd(#64) and wave 1b at85a5472. The Claude coordinator's lanes land in this order: this page (RM1), then the sixteen unmergedclaude/w1-*andclaude/w2-*lanes and the website refresh, each after the reviews the coordinator requires under OD-G and OD-H, and W2-G, whose route decision (W-15) the owner answered on 2 October; each starts from the currentmain. Each integration branch starts from the currentmain, checks thatmainhas not moved, and regeneratessite/andwebsite/; until MRG0 lands, each re-anchorsdocs/lifecycle.md. - Live loop: LM → L3 → L4 → B3–B4; L3b → B1 → B2 → B9a → L8 → L9 → B9b; step 1 (D4 → D8) and the one transport: CX0 (done) → L7 → DOA, with IP1 giving DOA its per-task priority lists and L-S1's record before whichever first contacts a provider. The Claude transports are not planned (OD-A).
- Product deliveries: D8 + R15 → SA5 → SA6 → SA7 → AG → PB1, plus GH-W (after SA9), each Product's first delivery grant and
mainprotection. Then Tally's Slices (TB-P1, TB-M1, TB-N4 → N3 → N1 → N2) and TM, after TM-T. Each Product's Notion gates are imported before its first live work (NX1). - Public: the website and docs are live (W2). W2-H adds HTTPS and HSTS on both sites once the owner signs in to Cloudflare (W-16). W2-G, which guards later deploys, awaits its merge reviews (the owner removed the route-check requirement, W-15); CF7 takes deploys over through AG, and CFA later moves them to a Factory-only account.
- What moved on 1 and 2 October.
- At 00:55 BST on 2 October (this refresh, to
85a5472):- Done: IP1 (#64,
3121bdd) and wave 1b, #57's first test-only slice (d1da83e,9651734,85a5472). CI onmainpassed at85a5472, the first full-suite pass sincec27b643. - Recorded: OD-H, the owner's acceptance and shipping decision (about 23:45 and 23:50 BST); Fable's advisory acceptance review of the 24 merged families (23:52 BST) and the coordinator's decision to accept them (issue #63, 23:53 BST), with the acceptance receipts not yet made.
- In flight: sixteen unmerged Claude lanes (
w1-01tow1-14,w2-16,w2-19), among them CI1, FB-H7r and CF1's start; the website refresh; CO0's two designs and Fable's critique. - Changed: IP1 moved from Now to Done; W-17's question of who accepts was answered; the snapshot is dated to the read, not to the commit.
- Done: IP1 (#64,
- Earlier, to
d73b06e(the previous revision, with facts read up to about 23:40 BST on 1 October):- Merged, not accepted: CXS-A and CXS-B, with each pull request's SHA (see "The merged stack"); E36–E38 are now on
main; the Verification workflow design (#49) is onmain. CXS-A and CXS-B leave Now; CXS-F (follow-ups #55–#60 and acceptance) and CXS-C (later branches) replace them. - Done, not on
main: CX0 (the Codex source, retrieved at 16:31 BST). L7 stays planned. - Recorded: the owner's answers OD-A to OD-F (Claude CLI unavailable; Codex for discovery with model priorities; ChatGPT overage off, answered to a dated-confirmation option; both bets and Tally run 1 decisions 2–7 accepted; the Codex source download; HTTPS and HSTS on both sites) and OD-G, the owner's merge gate of about 23:00 BST (an Opus 5.5 primary review, a Fable 5.1 xhigh secondary review, then the coordinator's judgement).
- Not planned: C1-6, C1-A, C1-T, MRG1, C1-R7, L6, FQ and L10, each with the owner's reason. W-2, W-4, W-5 and W-7 leave the owner list as answered.
- New: IP1 (then in flight: three commits on its branch, both merge reviews passed at 23:16 and 23:21 BST, not merged), DOA (planned, after L7), W2-H (blocked: approved, waiting on the owner's Cloudflare sign-in), W-15 to W-17.
- Held, not done: SA-OP and SA-HA (the owner's hold at 18:00 BST after round 7: Astra and Fable round 7 FAIL at 17:24 and 17:40 BST; rounds resume only when the owner reopens the design). Blocked, not done: W2-G (the pinned
cfcannot list Workers routes; its rounds w1 to w3 failed). - Changed: dependencies on W-2 and MRG1 are reworded; L8 and L9 depend on DOA instead of L6; BX8 has no transport for its design section while FQ is not planned; EP1's epic IDs move past E38; row numbers were renumbered, so cite IDs.
- Merged, not accepted: CXS-A and CXS-B, with each pull request's SHA (see "The merged stack"); E36–E38 are now on
- At 16:00 BST (Opus 5.5's refresh):
- To Done: SA1, SA1-F2, FB-H1–FB-H3, IR and R13, FB-CMD, R1–R4, R8, TOOL1, the plain-style and copy-lint passes, the documentation types (DOCS-T), CI0 and the adoption decision (ADP). Only work on
mainis Done: owner decisions, external events, reviewed designs and the Claude audit's lane commits sit under "Recorded, not onmain". - Changed: CX0 carried no owner or Factory approval step (Astra's content finding, round 4); EP1's epic IDs moved past E35; DOC-R lost IN11 to IN12 and followed IN12 in the order; the plain-style pass's IDs were qualified
continuation/to tell them from the delivery task P2; the delivery part of MRG1 closed; the Diátaxis steps folded into DX-R; W-3, W-6, W-12 and W-13 left the owner list. - Set aside in the merge: the lane's intent r11 text, because
main's r11 took the same IDs for independent adoption (IN12).
- To Done: SA1, SA1-F2, FB-H1–FB-H3, IR and R13, FB-CMD, R1–R4, R8, TOOL1, the plain-style and copy-lint passes, the documentation types (DOCS-T), CI0 and the adoption decision (ADP). Only work on
- At 00:55 BST on 2 October (this refresh, to
- Merge hazards. Receipts pin the paths whose hashes they record.
docs/roadmap-receipt.json,docs/roadmap-content-receipt.json,docs/roadmap-content-r2-receipt.json,docs/roadmap-refresh-receipt.json,docs/roadmap-refresh-r2-receipt.json,docs/roadmap-refresh-r3-receipt.json,docs/roadmap-refresh-r4-receipt.json,docs/roadmap-refresh-r5-receipt.json,docs/roadmap-refresh-r6-receipt.json,docs/roadmap-refresh-r7-receipt.json,docs/roadmap-refresh-r8-receipt.jsonanddocs/roadmap-refresh-r9-receipt.jsonrecord earlier bytes of this page and of the files named in each (README.md,docs/guide/index.md, both intent files and the build manifests for the content receipts; the page,site/build-manifest.jsonandsite/reference/roadmap.htmlfor the refresh receipts); the merge atd73b06eregeneratedsite/, so the r3 receipt already reports those two site files as changed, as history, and the r4 to r9 receipts report all three files as changed.docs/roadmap-refresh-r10-receipt.jsonrecords this revision's bytes of the page,site/build-manifest.jsonandsite/reference/roadmap.html, taken afterorigin/main85a5472was merged into this branch, so they are the bytesmainreceives, and no earlier hash is rewritten. Once merged, this page is published by the public build, which refuses any UUID, email address or token-like string, so it carries none.
