[brettheap]

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)
Authored by lane openXfactory-3, delegated by lane openxfactory-4 (#656 5984809190)

Plan 034 T097, release 1's bookkeeping. This PR ticks all 63 release-1 boxes of #1144's tasks.md (add-neutral-product-standalone-operability) that a realization task closes, each with its evidence note, and records research R16's non-normative corrections. Its After set has landed: batch P (#1230), T096 (#1241 → 8a37a087) and T099 (the publish at the cut, and openDox#19 → d77f8cbf). On the holder's rulings it also ticks plan 034's T095, T099, T002, T007 and T097, each with its bullet, so plan 034 closes at 92 of its 96 tasks. T090 to T093 tick at the arc's close.

• Bookkeeping, so it carries no Arc: trailer (R1Q20 (a), 5817152735; T091) and no closing keyword. It touches openspec/changes/, so lane openxfactory-4 lands it under a Rule 6 LANDING/LANDED window.

• Based on main 8a37a087 (T096: AT-R1 at openDox-code 389e5a4a (RELEASE1_TIP), both halves, with T095's acceptance job; tick T096 (plan 034) #1241, T096), merged in by 0cde3961. The PR was first based on c8d80020 (Q-GRC-4 bookkeeping: tick 6.9-6.14 against T2 (#1006 → 765d8c6f); 6.15 and 6.18 left open, one named clause each #1232). The merges since are listed below. Its commits:

  • 76d8ff37: the ticks, the notes and R16;
  • b7f49673 and e2efb3a1: from Copilot's review (below), which edit note text only;
  • bd32ea9c: the merge of main after batch P landed;
  • cf2c6bdc: 16.3a's tick, on the T100 follow-on's landing (openDox-code#86 → 651c35fe);
  • 5870cd00: 4.3's and 9.2's ticks, on T086's landing (openXdox-code#37 → 56e1c238);
  • 23665543: 5.5's note reworded (Copilot at 5870cd00), note text only;
  • 96c74eab: the merge of main after T094 and T098 landed;
  • 935164af: 3.3's tick, on T098's landing (openxFactory#1237 → 20ce593e);
  • e93ab9fb: 5.4a's note reworded (Copilot at 935164af), note text only;
  • f6c6dc3c: the merge of main after T089 landed;
  • e873b25f: F4.1's, F5.2's and F16.1's ticks, on T089's landing (openxFactory#1238 → fab575ad);
  • 9759313b: the merge of main f2acc88c;
  • 10b6ba05: the phase-1 and phase-2 checkpoint citations by path (below), note text only;
  • 0cde3961: the merge of main after T096 landed;
  • f94be2fd: 10.3's tick, on T099's publish, and plan 034's ticks (below);
  • 9713f991: plan 034's opening status, which still said batch P was to land (Copilot at f94be2fd, below), plan text only.

  If main moves before the landing, I merge it in. No rebase and no force-push.

Measured, not copied

Lane 4's table (2026-10-03T20:05Z, at de2ab703: 52 CLOSED-LANDED, 11 PENDING, 5 LEFT-OPEN, 2 ALREADY-TICKED) was regenerated by its own generator, patched, at c8d80020, at ba6bb870, and again after each closing landing:

• every landing PR, now 115 across the six repositories, re-read with gh pr view <n> -R opensoft/<repo> --json state,mergeCommit,mergedAt, last at 2026-10-05T16:50Z. Since the first reading these have landed: T007 batch P: the rulings of 5982436447 in #1144 (12.4a's hint line and history limit, 16.3a's in-repo refusal and served-repo limit, F16.1's note) and the T100 follow-on (plan 034) #1230 (batch P, ba6bb870), openDox-code#84 (T104, which realizes no box, 32943cbf), openDox-code#86 (the T100 follow-on, 651c35fe), openDox-code#78 and openDox-code#79 (T101, d59f3f26 and dede32b4), openDox#17 (T076, 504324de), openDox#18 (T087, e1e3a3c3), openXdox-code#37 (T086, 56e1c238), openXdox#22 (T094's openXdox root step, 9564d5d9), T094's ahead PR: the CLI help golden, the usage line and the rebound-Host case hold at both pins (T066's form; not an arc landing) (plan 034) #1234 (T094's ahead PR, ca1c1486), phase 3 ticks: T076, T086, T087, T101 and T104 (plan 034) #1235 (phase 3's plan ticks, 70602a0a), T094: phase 3's consumer pins, openDox e1e3a3c3 and openXdox 9564d5d9, with phase 3's host wiring: openXdox's columns and the governed binding-trust policy (plan 034) #1236 (T094, 36908480), T094/T098: phase 3's interim F11.1, tick both (plan 034) #1237 (T094/T098, 20ce593e), T089: phase 3's checkpoint, quoted; T092's phase-3 notes (plan 034) #1238 (T089, fab575ad), openDox-code#75 (T095, which realizes no box, 389e5a4a) and openDox#19 (T099's root README, d77f8cbf);
• every task's landing re-read from plan 034's own Landed: bullet (78 of 96 tasks ticked at c8d80020 and ba6bb870, 85 at 20ce593e, 86 at a43845e6, 87 at 8a37a087), and each run record traced to the openxFactory PR that added it: checkpoint-phase1.md (T049: phase 1's checkpoint, quoted; F9.2 red as ruled; T092's phase-1 notes (plan 034) #1204 → 9d2e5bc3), checkpoint-phase2.md (T063: phase 2's checkpoint, quoted; T092's phase-2 notes (plan 034) #1218 → a883bbf6), f10.1-run.md (T077: run F10.1 as batch H amends it, at openDox-code 8e377823 (plan 034) #1223 → f261fefa), f13.1-run.md (T074: run F13.1 as batch H amends it, at openDox-code 90ac7033 (plan 034) #1224 → de2ab703), f16.1-run.md (T083: 16.6 and F16.1 at openDox-code 38d3350e; tick T082, T083 and T100 (plan 034) #1231 → 0e01ca85), f11.1-phase3.txt (T094/T098: phase 3's interim F11.1, tick both (plan 034) #1237 → 20ce593e), checkpoint-phase3.md (T089: phase 3's checkpoint, quoted; T092's phase-3 notes (plan 034) #1238 → fab575ad) and at-r1/oracle-verdict.md (T096: AT-R1 at openDox-code 389e5a4a (RELEASE1_TIP), both halves, with T095's acceptance job; tick T096 (plan 034) #1241 → 8a37a087). The T100 follow-on, which is no task, is read from the forge;
• batch P's text read at T007 batch P: the rulings of 5982436447 in #1144 (12.4a's hint line and history limit, 16.3a's in-repo refusal and served-repo limit, F16.1's note) and the T100 follow-on (plan 034) #1230's heads 84113a44 and d08249a2, and as it landed (ba6bb870, the squash of its head 051f9945).

Result: 63 CLOSED-LANDED, 0 PENDING, 5 LEFT-OPEN and 2 ALREADY-TICKED, of 70. Since lane 4's table:

• T082 (openDox-code#76 → ca9e1bd5), T100 (openDox-code#82 → 38d3350e), T102 (openDox-code#81 → 0116293a) and T083 (openxFactory#1231 → 0e01ca85) have landed. That closes 16.4, 16.5 and 16.6.
• The T100 follow-on (openDox-code#86 → 651c35fe) has landed. That closes 16.3a.
• T086 (openXdox-code#37 → 56e1c238) has landed. That closes 4.3 and 9.2.
• T098 (openxFactory#1237 → 20ce593e), phase 3's interim F11.1, has landed. That closes 3.3 (below).
• T089 (openxFactory#1238 → fab575ad), phase 3's checkpoint, has landed. That closes F4.1, F5.2 and F16.1 (below).
• T076 (openDox#17 → 504324de) and T101 (openDox-code#78 → d59f3f26, openDox-code#79 → dede32b4) have landed.
• T095 (openDox-code#75 → 389e5a4a) and T096 (T096: AT-R1 at openDox-code 389e5a4a (RELEASE1_TIP), both halves, with T095's acceptance job; tick T096 (plan 034) #1241 → 8a37a087), AT-R1's two halves, have landed. They close no box of File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144.
• T099 has published opendox 0.1.0, and its root README PR has landed (openDox#19 → d77f8cbf). That closes 10.3 (below), the last box.

Batch P closes and rewords no box. In #1144's tasks.md it only inserts addenda at the ends of 12.4a, 16.3a and F16.1: no box line moves and no box changes state. Since ba6bb870, no landing has touched #1144's tasks.md. In plan 034's tasks.md, T097's own text is unchanged.

The census

python3 box_census.py openspec/changes/add-neutral-product-standalone-operability/tasks.md, with the tool written from research.md § Appendix (byte-identical to the Appendix's heredoc).

Before, at main 8a37a087 (identical to c8d80020's, ba6bb870's, 20ce593e's and a43845e6's):

2 8 2.1[ ] 2.1a[ ] 2.2[ ] 2.3[ ] 2.4[ ] 2.5[ ] 2.6[ ] F2.1[ ]
3 5 3.0[x] 3.1[ ] 3.2[ ] 3.3[ ] F3.1[ ]
4 5 4.1[ ] 4.1a[ ] 4.2[ ] 4.3[ ] F4.1[ ]
5 12 5.0[ ] 5.1[ ] 5.2[ ] 5.3[ ] 5.3a[ ] F5.1[ ] 5.4[ ] 5.4a[ ] F5.2[ ] 5.5[ ] 5.6[x] F5.3[ ]
7 8 7.0[ ] 7.1[ ] 7.1b[ ] 7.1a[ ] 7.2[ ] 7.3[ ] F7.1[ ] F7.2[ ]
9 8 9.1[ ] 9.2[ ] 9.2a[ ] 9.3[ ] 9.4[ ] 9.5[ ] F9.1[ ] F9.2[ ]
10 5 10.1[ ] 10.2[ ] 10.2a[ ] 10.3[ ] F10.1[ ]
11 3 11.0[ ] 11.1[ ] F11.1[ ]
13 8 13.1[ ] 13.2[ ] 13.3[ ] 13.4[ ] 13.4a[ ] 13.5[ ] 13.6[ ] F13.1[ ]
16 8 16.1[ ] 16.2[ ] 16.3[ ] 16.3a[ ] 16.4[ ] 16.5[ ] 16.6[ ] F16.1[ ]
total 125 Counter({' ': 105, 'x': 11, '~': 9})

After, at this head 9713f991 (9713f991 changes only plan 034, so the census is f94be2fd's):

2 8 2.1[x] 2.1a[x] 2.2[x] 2.3[x] 2.4[x] 2.5[x] 2.6[x] F2.1[x]
3 5 3.0[x] 3.1[x] 3.2[x] 3.3[x] F3.1[x]
4 5 4.1[x] 4.1a[x] 4.2[x] 4.3[x] F4.1[x]
5 12 5.0[x] 5.1[x] 5.2[x] 5.3[x] 5.3a[x] F5.1[x] 5.4[x] 5.4a[x] F5.2[x] 5.5[x] 5.6[x] F5.3[x]
7 8 7.0[x] 7.1[x] 7.1b[x] 7.1a[x] 7.2[x] 7.3[x] F7.1[x] F7.2[x]
9 8 9.1[x] 9.2[x] 9.2a[x] 9.3[x] 9.4[x] 9.5[ ] F9.1[x] F9.2[ ]
10 5 10.1[x] 10.2[x] 10.2a[x] 10.3[x] F10.1[x]
11 3 11.0[ ] 11.1[ ] F11.1[ ]
13 8 13.1[x] 13.2[x] 13.3[x] 13.4[x] 13.4a[x] 13.5[x] 13.6[x] F13.1[x]
16 8 16.1[x] 16.2[x] 16.3[x] 16.3a[x] 16.4[x] 16.5[x] 16.6[x] F16.1[x]
total 125 Counter({'x': 74, ' ': 42, '~': 9})

The release-1 groups are shown. Groups 1, 6, 8, 12, 14, 15 and the follow-ons read the same before and after. Earlier heads read 'x': 66, ' ': 50 (76d8ff37 to bd32ea9c), 'x': 67, ' ': 49 (cf2c6bdc), 'x': 69, ' ': 47 (5870cd00 and 23665543), 'x': 70, ' ': 46 (935164af to f6c6dc3c) and 'x': 73, ' ': 43 (e873b25f to 0cde3961).

The change: #1144's tasks.md, and plan 034's ticks

• 63 boxes ticked, each with its evidence note as the item's last paragraph, after any addenda. The note is in 1.8's and 3.0's form: a bold dated lead, **Landed <date>**, where the date is the last landing of the box's realizing tasks; the tasks; the landings as repo#n → sha8; and the falsifier's result, with where it was quoted. For example, 2.4:

  Landed 2026-09-27 (T030, in T011's PR): openDox-code#46 → 0e88454a. tests/test_imports_standalone.py::test_every_module_imports_with_no_sibling first asserts the four siblings absent, then imports every module, failing with the first that still needs one (evidence/checkpoint-phase1.md § 1).

• No ratified line moves. Against main 8a37a087, File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's diff is the 63 checkbox lines, [ ] → [x], and 64 inserted paragraphs (482 lines): 63 notes, and 1 R16 note on an open box (9.5). This was proven at f94be2fd by setting every checkbox to [ ] in both files and diffing: the result is 64 insertions and nothing else, and the lines the two files share differ only by the 63 flips. The only other file the PR changes is plan 034's tasks.md (below). The file is byte-identical to a fresh re-apply of the regenerated decisions onto main's file.

• Research R16 (research.md § R16), each figure re-checked against research R2, R4, R5, R10 and R13 and plan 034's records:

R16 item	box	where it is recorded
1	2.5	in 2.5's note: 22 modules, not 26, were reached by no CI step
2	9.4	in 9.4's note: openXdox-code's floors read 564/558/6 at 626f2c8d, not 539/533/6
3	4.3	in 4.3's note, since 4.3 closed on T086 (an open-box note until then): run_scoped_doc_health makes three of the four reaches, and the fourth is session_documents
4	3.2	in 3.2's note: the proxy's refusal was written for NOTHING REGISTERED
5	10.1	in 10.1's note: Q-R4 is recorded at runtime/cli.py:39-42, not :40-46
6	9.5	a note on the open box (open for the arc's close, T090): the openDox pin was 11 commits behind, not 9, and T086 has since moved it to dede32b4
7	Group 2's heading	in 2.1's note, the box the heading introduces: 1,305 and 1,239 at 1e4a57fb
8	3.0	no new line: 3.0's own note already records it ("Read at ratification, 2026-09-24")

10.3, closed on T099

10.3's box says the openDox root documents the entry point and does not host it, and batch H's addendum makes the documented command pip install "opendox[local]", then opendox generate-and-open --local …. Plan 034 maps it to T076, T101 and T099:

• T076 (openDox#17 → 504324de) documents the install and the start, and adds no make target.
• T101 adds the release workflow and the version bump (openDox-code#78 → d59f3f26, openDox-code#79 → dede32b4).
• T099 publishes that commit at the cut, on Brett Heap's word (5997633384). Read from the forge and from PyPI:
  • the annotated tag v0.1.0 (9153c254) names dede32b4, which the openDox root's contracts/code-pin.yaml names;
  • openDox-code's release run 37339111713, dispatched on that tag, completed success in all four jobs: build and verify, publish to TestPyPI (the dry run), install opendox[local] from TestPyPI and publish to PyPI, whose steps include PyPI serves the files the build job verified;
  • https://pypi.org/pypi/opendox/0.1.0/json lists exactly two files, neither yanked: opendox-0.1.0-py3-none-any.whl (sha256 8ecea00db6f9…) and opendox-0.1.0.tar.gz (sha256 56869b6208a8…);
  • openDox#19 → d77f8cbf replaces the README's stand-in paragraph. At that commit, the README's first line resolves from PyPI, and no paragraph says that no release is published.

Plan 034: T095, T099, T002, T007 and T097

Lane openxfactory-4's delegation of 2026-10-05T16:37:31Z asks #1233 to tick these, each with a Landed or Done bullet in #1226's form, so that release 1 closes at 92 of 96. Its ruling 5999175092 settles three points: (a), (a) and (a). Every sha in the bullets was read from GitHub.

• T095: openDox-code#75 → 389e5a4a, which is X. Its acceptance job at X is the dispatched run 37333323932: head_sha X, job 111841708700, success, and its log reads AT-R1 HTTP half: PASS (314 assertions held).
• T099: P against X. The compare shows four files between them, none a build input, so the ruled check exits 0. Then the tag, the release run, PyPI's two files and openDox#19, as above.
• T002 (ruling (a)): 45 of the 50 slices in the three phases' writer tables were claimed on openDox + openXdox: two open-source layers, an installable app with users, projects and a database; domain descendants pin openXdox (Brett's ruling 2026-09-04) #656, and the bullet cites each claim. The five that were not are named in T091's form: P1-C, whose claim 5850230046 was posted as a literal file path and never edited, and P1-L, P2-H, P2-L and P2-M. Nothing is back-filled.
• T007 (ruling (a)): batches A to P have landed (P T007 batch P: the rulings of 5982436447 in #1144 (12.4a's hint line and history limit, 16.3a's in-repo refusal and served-repo limit, F16.1's note) and the T100 follow-on (plan 034) #1230 → ba6bb870), and its status sentence now says so.
• T097: the census and research R16's corrections, with two non-normative notes beside them:
  • D6's T096 refusals, "refused by name, with no browser signal";
  • the reachability of T096: AT-R1 at openDox-code 389e5a4a (RELEASE1_TIP), both halves, with T095's acceptance job; tick T096 (plan 034) #1241's first commit, f632d70c, which oracle-verdict.md names as holding the bytes that ran (ruling (a)'s wording). It is not on main: refs/pull/1241/head (5c663a7e) reaches it, and so does T096: AT-R1 at openDox-code 389e5a4a (RELEASE1_TIP), both halves, with T095's acceptance job; tick T096 (plan 034) #1241's branch, which still stands. main's SHA256SUMS fixes the reviewed scripts, and the record names the ran bytes by their sha256.

The checkpoint citations, by path

Lane openxfactory-4 ruled at 2026-10-05T16:25:25Z that the notes' CP1 § n and CP2 § n citations name their records, as the phase-3 notes name evidence/checkpoint-phase3.md. CP1 and CP2 are the shorthand of lane 4's table, and #1144 never defines them. The change is non-normative and inside T097's R16 scope. 10b6ba05 makes it. The 26 citations, in 25 notes, now read evidence/checkpoint-phase1.md (T049, #1204) and evidence/checkpoint-phase2.md (T063, #1218). A word diff against e873b25f finds those 26 tokens and nothing else; only the 25 paragraphs' line breaks move.

F4.1, F5.2 and F16.1, closed on T089

T089, phase 3's checkpoint, landed on 2026-10-05T15:26:43Z as #1238 → fab575ad. Its record, specs/034-opendox-standalone-operation/evidence/checkpoint-phase3.md, extracts each block from #1144 by anchor at 36908480 and runs it from a fresh worktree at the commits phase 3 pinned: openDox-code dede32b4, the code of the openDox root e1e3a3c3 (T087), and openXdox-code 56e1c238 (T086). It says of F4.1 and F5.2 "T097 ticks both in #1144; this record ticks nothing there", and plan 034's T089 Run bullet says the same. Each box closes on that run, by plan 034's Box accounting:

• F4.1 (F4.1 → T089): as extracted (sha256 8900b985e72f) and run unchanged, it exits 0 with 1 passed, 1 passed, then no deferred reach names the consumer or the publisher (§ 1).
• F5.2 (F5.2 → T086, T089; RULED 5962785556, item 1, moves its close to phase 3): whole, as batches C, F, G and K amend it (OPENXFACTORY at 36908480, last step --chains), it exits 0. The seven suites pass whole (45, 23, 18, 6, 40, 9 and 12 passed), test -s holds, and the last step prints five admitted: lines, then ok: 5 protected edit(s), each entered and holding (§ 5). One of the five admits T086's edits to tests/test_session_snapshot.py, by entries 16, 17 and 19 of tests/protected_suite_respellings.yaml at 56e1c238: the three pre-arc reds that T063 quoted, each entry naming the test it repairs.
• F16.1 (F16.1 → T083 (at 38d3350e), T089 (batch P's cases, at T087's pin)): with batch M's line, it exits 0 with 24 passed, the dialect line, no model configured: the catalog offers nothing, 83 passed and 532 passed (§ 4). dede32b4 carries the T100 follow-on (openDox-code#86 → 651c35fe is its ancestor, and the only commit between T100's landing and dede32b4 that touches tests/test_model_binding_trust.py). That file is the same at both: 160 tests, among them batch P's six test_F16_1_batch_p_* cases and A8's test_A8_a_state_directory_that_is_a_link_trusts_nothing, none of which exists at 38d3350e. T083's run there is quoted beside it, as before.

3.3, closed on T098

3.3 asks that the carve manifest's deleted_at_carve row for scripts/ideation_dashboard/profile_openxfactory.py stay BYTE-IDENTICAL. T017, which realizes it, reads the row through the three interim F11.1 runs, "and T097 ticks 3.3 on all three". Each was re-checked on main 20ce593e:

• Phase 1, T018 (T017/T018: close F11.1's admitted-arc-edits gap (RULED #656 5890601202), tick both (plan 034) #1202 → e81eed62, evidence/f11.1-phase1.txt): the amended run at T047's landing prints requirement 1 holds: 0 note(s) annotated, every other path a declared surface (11.1), and the record's T017 section reads the row.
• Phase 2, T065 (T064/T065: phase 2's interim F11.1, tick both (plan 034) #1217 → 1f670bc3, evidence/f11.1-phase2.txt): the same line, at T064's landing.
• Phase 3, T098 (T094/T098: phase 3's interim F11.1, tick both (plan 034) #1237 → 20ce593e, evidence/f11.1-phase3.txt), at ARC_TIP 36908480 (T094, T094: phase 3's consumer pins, openDox e1e3a3c3 and openXdox 9564d5d9, with phase 3's host wiring: openXdox's columns and the governed binding-trust policy (plan 034) #1236). It prints the same line (exit 0) over the arc's three landings, and it refuses a planted path. docs/opendox-carve-manifest.yaml is touched by none of the three. Its T017 section finds the row equal at the manifest's introducing commit 17167481 and at that tip, both raw and parsed: not_moved, deleted_at_carve, no edits.
• Re-read for this tick at main 20ce593e: the row is still equal to 17167481's, both raw (4 lines) and parsed. scripts/opendox_host.py is still openxFactory's host: T094 modified it and deleted nothing, which F11.1 would have refused.

4.3 and 9.2, closed on T086

T086 landed on 2026-10-05T12:23:03Z as openXdox-code#37 → 56e1c238. It is a squash whose tree (78ef1ed1) is that of its head 57bebd8b. Its pin is openDox-code dede32b4, the commit T087 pins (openDox#18 → e1e3a3c3).

• 4.3 closes "with the last of" the nineteen reaches into openXdox, and "openXdox-code's ratchet (OPENDOX_BACK_IMPORTS) is tightened to (0, 0) in the same landing". At 56e1c238:
  • tests/test_dependency_direction.py holds OPENDOX_BACK_IMPORTS = {}, and test_the_pinned_opendox_does_not_import_openxdox_back asserts (0, 0).
  • openXdox-code#37's body reads that file 17 passed at the pin, with the census empty.
  • consumer_reach.py, absent at dede32b4, was retired by T084 (openDox-code#77 → e49b17c3).
• 9.2 closes in phase 3 (batch F's addendum), with batch B's note. At 56e1c238:
  • tests/declared_exclusion.yaml holds 66 entries carrying 68 reasons: 60 doc_health, 3 status-exemption-rail and 5 openxfactory-contracts.
  • CI's validate at the PR's head (openXdox-code run 37307785866) printed open extraction: the declared exclusion and triple: selected=1099 passed=1095 skipped=4 failures=0 errors=0.
  • Requirement 9 stays open until T008.

16.3a, closed on the T100 follow-on

16.3a is "Carried out by T100", and batch P's addendum adds "Carried out by a T100 follow-on openDox-code PR (claim 5982447319), which is no task of plan 034 and lands before T087":

• T100 landed as openDox-code#82 → 38d3350e.
• The follow-on landed as openDox-code#86 → 651c35fe (09:49:55Z). It is a squash whose tree is that of its head aecac805, and it landed before T087 (openDox#18, 11:58:27Z) and T101.
• It carries out Brett Heap's 5982436447, item 2, and 5983805990, with the holder's 5984069416, 5985046107 (C1 to C5) and 5985553609, and the holder's A8.
• Its body records the falsifier: F16.1's block as batch P amends it, run by T089's runner at aecac805, exits 0 with 532 passed in tests/test_model_binding_trust.py. The six test_F16_1_batch_p_* tests are present at 651c35fe.
• The open trust-time existence check, and the follow-ons of openDox-code#86's eighth Copilot review, move no box of release 1. 16.3a's own text says so for the first, and the holder's 5992038800 for the second.

Left open, by T097's own text

• 9.5, 11.0, 11.1 and F11.1, for the arc's close (T090 to T093), and F9.2, until T008. Nothing else is held.

T097 is ticked

T097's task is "Tick #1144's release-1 boxes, each with its evidence note: the 63 in the table below." All 63 are ticked, so f94be2fd ticks T097 in the same commit as 10.3, the last box, as lane 4's brief requires.

The merges of main

• bd32ea9c merged batch P (ba6bb870). It gave the one conflict this PR expected, at 16.4's checkbox line, which follows batch P's insertion at the end of 16.3a. The resolution took main's text for every hunk batch P changed and re-applied the ticks and notes with the same tool, byte-identical to a fresh re-apply onto main's file.
• 96c74eab merged main 20ce593e (T094's ahead PR: the CLI help golden, the usage line and the rebound-Host case hold at both pins (T066's form; not an arc landing) (plan 034) #1234 to T094/T098: phase 3's interim F11.1, tick both (plan 034) #1237). It was clean, because none of the four touches File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's tasks.md.
• f6c6dc3c merged main a43845e6 (T089: phase 3's checkpoint, quoted; T092's phase-3 notes (plan 034) #1238 and Q-GRC-4: tick 6.25 + 6.26 — C2 dispatched, admitted and sealed (run 37230435234, five seats); C2 record landed (cxF #500 → cc85a3cc) #1239). It was clean too, because neither touches File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's tasks.md.
• 9759313b merged main f2acc88c (Q-GRC-4 bookkeeping 2: tick 1.7, 2.1-2.6, 5.1 and 5.3 against what landed; 5.3 is a dated reading #1240), and 0cde3961 merged main 8a37a087 (T096: AT-R1 at openDox-code 389e5a4a (RELEASE1_TIP), both halves, with T095's acceptance job; tick T096 (plan 034) #1241). Both were clean, for the same reason.
• Every tick since is a fresh re-apply onto main's file.

Gates, at main 8a37a087 and at this head 9713f991, in one full clone named openxFactory

gate	main 8a37a087	this head 9713f991
python3 scripts/validate-openspec-cli-pin.py --all --no-cache (CI's form; pinned 1.12.0)	rc 0, 110 passed, 1 failed (111 items), 0 UNDISPOSITIONED failures, 1 accepted exception (add-chain-attestation)	identical output, but for the pinned CLI's temporary directory
… --change add-neutral-product-standalone-operability	—	rc 0, 1 passed, 0 failed, validated --strict clean
scripts/doc-health.py --single-repo . --as-of 2026-10-05	31 critical, 22 error, 69 warning, 20 info, 0 new regressions	byte-identical report
proposal-support.py . verify add-neutral-product-standalone-operability	ok	identical
validate-sequenced-after.py . --ledger-diff	229 rows, consistent	identical
validate-code-surface.py, validate-target-release.py, validate-pin-registrations.py, validate-document-catalog.py	rc 0 each (the catalog: 0 errors, 0 warnings)	identical
pytest -m "not postgres" over tests/doc-health, sequenced_after, proposal-support, former_id_arrival, citation_remainder, signed_execution_chain, openspec_cli_pin, target_release, code_surface, packet_reference, scope_globs	the 8 below fail identically	8 failed, 3427 passed, 1 skipped, the same 8 nodes as at 10b6ba05

The 8 failures are environmental, the same 8 at every head. Each needs the openDox and openXdox legs initialized, as CI's pytest-suite does, or a reachable pinned validator: test_ideation_readiness.py (3), test_readiness_dispatch.py (1), test_sentinel_vocabulary.py (2), test_status_reader_real_lines.py (1) and test_chain_reader.py (1). Re-run alone at main 8a37a087, they read 8 failed with the same messages. The venv was built by CI's own pip install --require-hashes -r requirements/hermes-runtime-contracts.lock, with LANG=C.UTF-8 and every GIT_*/XF_* variable unset. The earlier rounds read the same: main c8d80020 against 76d8ff37, b7f49673 and e2efb3a1, main ba6bb870 against bd32ea9c, cf2c6bdc, 5870cd00 and 23665543, main 20ce593e against 935164af, main a43845e6 against e873b25f, and main f2acc88c against 10b6ba05. At f94be2fd the local run was stopped at 31% on a session swap, and CI's pytest-suite passed there. No test, script or workflow reads plan 034's files (git grep over tests, scripts and .github finds none).

Also checked, on the inserted text at 9713f991:

• every repo#n → sha8 in File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's notes (71 distinct pairs, 122 mentions) and in plan 034's bullets is that PR's merge commit, per the forge;
• every other sha (17167481, 1e4a57fb, 36908480, 5c137a90, 626f2c8d, aecac805, dede32b4, f8a1ece; in the plan, 5c663a7e, 9153c254 and f632d70c) resolves in its repository, and the file digests match PyPI's JSON and the SHA256SUMS files;
• each of the 63 Landed dates equals the last landing of the box's realizing tasks (F5.1's and F7.1's notes also name T063's later re-run, and 5.4a's names the host line, T064: phase 2's consumer pins, openDox d5098297 and openXdox f257e021, with openXdox's governed projection registered by the host (plan 034) #1215);
• no closing keyword, no Arc: line, no host path, and no unqualified reference to another repository, in the diff, the commit messages or this body;
• no inserted line is wider than 80 characters, and in File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144 none starts a list, a heading or a table.

CI and review

• CI at this head 9713f991: every check-run but Sourcery's completed success, the 8 required among them (pytest-suite 17:54:16Z to 18:15:30Z). Sourcery's reads skipped. lane-line re-ran on each edit of this description and passed.
• CI at f94be2fd: every check-run completed success, the 8 required among them (pytest-suite 17:13:56Z to 17:31:21Z).
• CI at 10b6ba05: every check-run completed success (pytest-suite until 17:04:09Z).
• CI at e873b25f: every check-run completed success, the 8 required among them (pytest-suite 15:57:01Z to 16:22:01Z). lane-line re-ran on each edit of this description and passed.
• CI at 935164af, 23665543, cf2c6bdc, bd32ea9c and e2efb3a1: every check-run completed success, the 8 required among them (signed-execution-chain-gate, lane-line, former-id-arrival-gate, openspec-cli-pin, wallet-validation, pytest-suite, release-tag-gate, openxdox-consumer-gate). At 5870cd00, 23665543's run superseded its pytest-suite.
• Copilot at 76d8ff37: one finding, r4179674026: F7.2's note named no landing commit for T058 or T063. b7f49673 names them (openDox-code#68 → 047bb4fa, openxFactory#1218 → a883bbf6), and 7.1's changelog landing too (openDox#15 → 66758438). The thread is answered and resolved.
• Copilot at b7f49673: no new finding, and one "previously missed" note: that 5.4a's note wrongly said T059's run deselected the three pre-arc cases. The note was right, and comment 5985467371 gives the records. The cited lines are T059's Falsifier line, written before it landed; T059's Landed record and openXdox-code#35's body (rulings 4 and 6, and its F5.2 run) record the deselections. e2efb3a1 makes the note exact and cites them.
• Copilot at 5870cd00: "Findings: None", and one "previously missed" low note: 5.5's note read as though consumer_reach "names the task lists". 23665543 says what it meant, that the seven consumer_reach names T055 lists are retired.
• Copilot at e2efb3a1, bd32ea9c, cf2c6bdc and 23665543: "Findings: None". Where its status line read "Changes recommended", it named only what this DRAFT waits for.
• Copilot at 935164af: one finding, r4185667778: 5.4a's note read "the seven red at both pins". e93ab9fb reads "the seven reds", and the thread is answered and resolved.
• Copilot at e873b25f: one finding, r4186043242: this description was stale after T089's ticks. It is refreshed here, and the thread is answered and resolved. A second request at that head registered no new review.
• Copilot at 10b6ba05: "Findings: None".
• Copilot at f94be2fd: two findings, review 5418196219. r4186761333: plan 034's opening status still said batch P was to land, against this PR's T007 tick. 9713f991 says that all sixteen batches have landed, A (T007 batch A: record #1144's ruled amendments (F3.1, 2.2, 3.2, 4.3, 10.1, 11.0, 11.1, F11.1) #1171) to P (T007 batch P: the rulings of 5982436447 in #1144 (12.4a's hint line and history limit, 16.3a's in-repo refusal and served-repo limit, F16.1's note) and the T100 follow-on (plan 034) #1230), and that T007 is closed. r4186761413: this description was stale at e873b25f. It was refreshed at 17:16:28Z, while that review ran, and is refreshed again here for 9713f991. Both threads are answered and resolved.
• Copilot at 9713f991: review 5418607294, on the push. Its one open item was r4186761413, this description, refreshed here for 9713f991. Its two "previously missed" low notes, at plan 034's lines 129 ("whose message lacks") and 4496 ("the drive"), need no change, because each phrase is the wording of the record it cites, T091's and oracle-verdict.md's. Comment 6000157580 gives the records. A request through the reviewer API, at 18:01:14Z, registered no new review at this head.
• Sourcery posted a reviewer's guide, and no comment on the diff. At 17:16:25Z it reported its review budget used, and its check-run reads skipped at f94be2fd and at 9713f991.

🤖 Generated with Claude Code

[sourcery-ai]

Reviewer's Guide

This documentation-only PR records release-1 bookkeeping for plan 034 by ticking 55 realized task boxes and appending dated evidence and R16 corrections, while deliberately leaving eight dependency- and arc-close-dependent boxes—and T097 itself—unticked until the stated follow-up landings arrive. The diff is intended to be insertion-only aside from checkbox changes, with validation showing no behavioral or ratified-text changes.

Sequence diagram for bookkeeping merge and final T097 tick

sequenceDiagram
    participant Lane4
    participant Main
    participant BatchP
    participant FollowUps
    participant Tasks

    Lane4->>Main: merge latest main
    Main-->>Lane4: updated tasks.md
    Lane4->>BatchP: resolve 16.4 conflict
    BatchP-->>Lane4: retain batch P text
    Lane4->>FollowUps: wait for pending landings
    FollowUps-->>Lane4: final pending box lands
    Lane4->>Tasks: tick final pending box and T097
    Tasks-->>Lane4: release-1 bookkeeping complete

Loading

Flow diagram for release-1 bookkeeping and pending landings

flowchart LR
    A["Plan 034 tasks.md at main"] --> B["T097 bookkeeping PR"]
    B --> C["55 boxes ticked"]
    B --> D["55 dated evidence notes"]
    B --> E["2 R16 correction notes"]
    B --> F["8 boxes remain pending"]
    F --> G["T086"]
    F --> H["T089"]
    F --> I["T098"]
    F --> J["T099"]
    F --> K["T100 follow-on"]
    F --> L["T083 and batch P"]
    G --> M["T097 becomes tickable"]
    H --> M
    I --> M
    J --> M
    K --> M
    L --> M

Loading

File-Level Changes

Change	Details	Files
Bookkeeping updates the release-1 task ledger with completion evidence and researched corrections.	Ticks 55 completed release-1 task and falsifier boxes. Adds dated landing notes with repository PRs, merge SHAs, test results, and cited evidence. Records eight non-normative R16 corrections, including two notes on boxes that remain open. Leaves ratified task text unchanged and intentionally holds pending boxes awaiting T086, T089, T098, T099, T100 follow-on, and batch P.	openspec/changes/add-neutral-product-standalone-operability/tasks.md
The bookkeeping preserves the PR's staged landing and merge constraints.	Does not tick T097 until all eight pending release-1 boxes land. Documents the expected batch-P merge conflict at 16.4 and its prescribed resolution. Keeps plan-034 content outside the diff while recording the remaining release-1 dependencies.	openspec/changes/add-neutral-product-standalone-operability/tasks.md
The updated ledger is validated as an insertion-only documentation change.	Regenerates the task census from 11 to 66 checked boxes while preserving blocked and open states. Verifies evidence references, landing dates, merge commits, line width, and absence of ratified-line changes. Reports unchanged validation, documentation-health, support, sequencing, catalog, and test-gate results relative to main, with eight known environmental failures.	openspec/changes/add-neutral-product-standalone-operability/tasks.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Copilot]

Copilot review overview

🟡 Changes recommended

Eight pending boxes and T097 remain open until the declared prerequisite landings are incorporated.

Review effort: Balanced
Findings: None

What changed in this PR

Records release-1 bookkeeping for the standalone openDox operability change.

Changes:

• Marks 55 realized release-1 boxes complete.
• Adds landing evidence and R16 corrections.
• Preserves eight pending boxes for prerequisite landings.

File	Description
openspec/​changes/​add-neutral-product-standalone-operability/​tasks.md	Updates release-1 completion and evidence records.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

The F7.2 evidence note omits the required landing commit references.

Review effort: Balanced
Findings: 1

Open (1)

• Add merge references for T058/T063 provenance · New

[Copilot]

Copilot review overview

🔵 Needs a closer look

The 5.4a evidence note contradicts the recorded T059 and T063 test executions.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Add merge references for T058/T063 provenance

Previously missed (1)

In code that hasn't changed since last review

Correct inaccurate claim that three pre-arc cases were deselected

openspec/​changes/​add-neutral-product-standalone-operability/​tasks.md:840

This reverses the recorded T059 run. Plan 034 says only the two consumer-schema cases in test_snapshot.py were deselected and every other suite ran whole (specs/034-opendox-standalone-operation/tasks.md:1620-1630); T063 then reports the three pre-arc cases as executed and red (:1965-1978). Saying those three were deselected makes this evidence note inaccurate.

[brettheap]

Lane: openxfactory-3 (openXfactory-3)

Copilot's review at b7f49673, "previously missed": 5.4a's note and T059's deselections. The review had no thread, so this comment answers it.

The note described T059's run as it landed, and that is correct. The cited lines, plan 034 tasks.md:1620-1630, are T059's Falsifier line. That line is the plan written before the landing, and it deselects only tests/test_snapshot.py's two schema cases. The landed run deselected more, and three records say so:

• T059's Landed record in plan 034: "Seven consumer-schema reds that fail at both pins are deselected in T059's F5.2 run … Three pre-arc reds in tests/test_session_snapshot.py are deselected with the reason "red at both pins; pre-arc carve residue; not the arc's", and stay open for F5.2 whole (T061, T063)."
• openXdox-code#35's body, rulings 4 and 6, and its F5.2 run: test_session_snapshot 20 passed, 3 deselected, test_snapshot 15 passed, 2 deselected, test_generator 41 passed, 4 deselected, test_snapshot_determinism 5 passed, 1 deselected, test_snapshot_registry 38 passed, 2 deselected.
• :1965-1978 is T063's later run of F5.2 whole. There the three pre-arc cases do run, and are red, as RULED 5962785556 (CP2 § 2). That run is T063's, not T059's.

The terse wording invited the misreading, so e2efb3a1 makes the note exact: the seven consumer-schema reds, tests/test_snapshot.py's two, and the three pre-arc reds of tests/test_session_snapshot.py, citing T059's record and openXdox-code#35's rulings 4 and 6, with T063's red quote. No other line moves.

[Copilot]

Copilot review overview

🔵 Needs a closer look

It awaits batch P, T096, and T099, after which the reviewed ledger will materially change.

Review effort: Balanced
Findings: None

[Copilot]

Copilot review overview

🔵 Needs a closer look

The draft remains incomplete pending eight boxes and final T097 bookkeeping.

Review effort: Balanced
Findings: None

[Copilot]

Copilot review overview

🟡 Changes recommended

It remains intentionally incomplete pending T096, T099, the remaining seven boxes, and T097’s final tick.

Review effort: Balanced
Findings: None

[Copilot]

Copilot review overview

🟡 Changes recommended

The PR description and census are stale, and final T096/T099 bookkeeping remains pending.

Review effort: Balanced
Findings: 1

Open (1)

• Refresh stale PR description to reflect current landing and validation · New

Resolved since last review (1)

• Use plural noun “seven reds” for grammatical consistency

[Copilot]

Copilot review overview

🟡 Changes recommended

T099, box 10.3, and T097 remain intentionally pending before this draft can be approved.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Refresh stale PR description to reflect current landing and validation

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 4 days and 3 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[Copilot]

Copilot review overview

🟡 Changes recommended

The PR description and an internal status summary contradict the newly completed bookkeeping.

Review effort: Balanced
Findings: 2

Open (2)

• Update stale batch status summary · New
• Refresh outdated PR metadata and validation details · New

[Copilot]

Copilot review overview

🔵 Needs a closer look

The extensive cross-repository provenance requires final human verification, and two CI checks remain in progress.

Review effort: Balanced
Findings: 1

Open (1)

• Refresh outdated PR metadata and validation details

Resolved since last review (1)

• Update stale batch status summary

Previously missed (2)

In code that hasn't changed since last review

Fix plural agreement in relative clause

specs/​034-opendox-standalone-operation/​tasks.md:129

The antecedent is plural (“two landings”), so the relative clause should also be plural: “whose messages lack.”

Clarify artifact reference as the browser driver

specs/​034-opendox-standalone-operation/​tasks.md:4496

“Drive” refers to no artifact here; the evidence names the browser driver (at_r1_browser.py). Change this to “driver” so the provenance note identifies the file whose bytes ran.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[brettheap]

Lane: openxfactory-3 (openXfactory-3)

Copilot's review at 9713f991 (5418607294), "previously missed": two low notes, on text f94be2fd added to plan 034's tasks.md. Neither needs a change, because each phrase is the wording of the record it cites.

• Line 129, "the two landings whose message lacks 11.0's line". T002's Done bullet repeats T091's own words. T091 (line 4309 at 9713f991) names openDox-code#37 and openDox-code#44 as "the two landings whose message lacks the line". The singular is distributive, one message per landing, and a change here would make T002 cite T091 in words T091 does not use.
• Line 4496, "the runbook and the drive that ran". "The drive" is the name evidence/at-r1/oracle-verdict.md gives at_r1_browser.py: its § "How it ran" has the bullets The runbook. (run-at-r1.sh, line 124) and The drive. (at_r1_browser.py, line 167). The note names the two files by the verdict's own headings. The note's next sentences then name each by its sha256: the bytes that ran, 702e2a4b… for run-at-r1.sh and 763b5919… for at_r1_browser.py, as the verdict records them, and the reviewed files that SHA256SUMS lists at 8a37a087.

Plan 034's opening status, Copilot's one finding at f94be2fd (r4186761333), is fixed in 9713f991. The description is refreshed for 9713f991 (r4186761413). Both threads are answered and resolved.

[brettheap]

READY at 9713f99 — Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

Holder: lane openXfactory-3's D1, T097, release 1's bookkeeping. It is the last landing of release 1. It touches openspec/changes/, so it lands under a Rule 6 LANDING/LANDED window. It carries no Arc: trailer (R1Q20 (a)) and no closing keyword.

• File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's release-1 boxes. All 63 are ticked, each with its evidence note. The last is 10.3:

  • release run 37339111713, all four jobs succeeding;
  • tag v0.1.0 (9153c254) at dede32b4;
  • PyPI's wheel 8ecea00d… and sdist 56869b62…;
  • openDox#19 → d77f8cbf.

  9.5, 11.0, 11.1 and F11.1 stay open for the arc's close, and F9.2 stays open until T008.

• Plan 034's ticks. T095, T099, T002, T007 and T097 are ticked in phase 3 ticks: T084, T102 and T103 (plan 034) #1226's form, which brings plan 034 to 92 of 96. T090 to T093 are ticked at the arc's close. T002's Done bullet cites the 45 slices' claims and names the five found without one, all lane openxfactory-4's own (RULED 5999175092, on T091's precedent; nothing is back-filled).

• R16's non-normative corrections are recorded in the evidence notes:

  • CP1 and CP2 are expanded to their record paths;
  • T096's two notes, "refused by name, with no browser signal", and f632d70c's reachability, in the ruled wording.

• Gates at the head. All checks pass. Copilot has reviewed at the head, with every thread resolved. The pinned OpenSpec gate reads as it does on main.

• The last round, 9713f991. It fixes plan 034's opening status: all sixteen T007 batches have landed (A T007 batch A: record #1144's ruled amendments (F3.1, 2.2, 3.2, 4.3, 10.1, 11.0, 11.1, F11.1) #1171 to P T007 batch P: the rulings of 5982436447 in #1144 (12.4a's hint line and history limit, 16.3a's in-repo refusal and served-repo limit, F16.1's note) and the T100 follow-on (plan 034) #1230), and T007 is closed. That answers Copilot's r4186761333 (holder ruling, 17:20Z). r4186761413, the stale metadata, is answered and resolved. Copilot's review at the head, "Needs a closer look", opens no new thread. Its two "previously missed" grammar notes quote the cited records' wording verbatim, at T091 and oracle-verdict.md, so they stay as quoted.

[brettheap]

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

LANDING — lane openxfactory-4, session faabad8b-8c31-4958-abd5-b35bdc9cd282@Eagle, 2026-10-05T18:17:07Z, PR #1233 into opensoft/openxFactory main

[brettheap]

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

LANDED — lane openxfactory-4, 2026-10-05T18:17:36Z, PR #1233 → 12753f2 (opensoft/openxFactory main; squash)