Repository navigation
spec(FIX-1496): ER-DevForce proof — thinnest DevForce path ships a real artifact - #2023
Conversation
…al artifact The retained spec set for W5's ER-DevForce exit proof, framed on the research finding that the proof is nearly built and has never been run: the model-backed check `it-commits-from-the-seats-own-file` is complete, type-checked and its verdict log's one row reads NOT RUN. Four gaps close, and nothing new is built. The declared feature channel is opened and driven rather than merely walked; the run moves to durable on-disk stores; the artifact becomes a pull request at an address that resolves after the run, instead of a commit in a temp directory; and the brief gains an executable acceptance condition so the product is graded, not just the prompt. Includes poc/gap-check/, a Node script that re-derives the twelve facts the spec rests on straight from the repository — with a totality assertion over every TypeScript file in the lab and four planted defects each watched going red. All twelve green, including that FIX-1440 does not fence this work. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
There was a problem hiding this comment.
Simplify review (FIX-1496 spec)
Verdict: The implementation plan is the right shape for “thinnest DevForce path” — compose pentest-style channel driving, sqlite durability, conductor’s gh probe as an isDone slot only, and a third sibling goal instead of rewriting an existing claim. I would not steer you toward new packages/ work or a mega-lab merge.
Where this PR does feel heavier than the issue title is mostly spec packaging, not the four gaps themselves.
What looks appropriately lean
- D1–D3 are real product forks with falsifiers; the rejected alternatives table is doing useful work.
- Third sibling goal vs extending
it-commits-from-the-seats-own-file— correct for verdict-log integrity. - Reuse guardrails (pentest host for
openChannels+ post, not manager-queuefileTask; importlabs/conductor/src/implement.tsfor probe only, notimplementPhaseprompts) — please keep these explicit at implement time.
Where complexity may have overshot (optional before merge)
- Narration density — the “four gaps / two lanes” story appears in the SVG,
SPEC.mdmermaid,BUSINESS-RULESfigure,PLANsketch, andDECISIONStree. One canonical figure + shorter cross-links would match “thin” better without changing decisions. gap-checklifecycle — helpful precedent (cf. FIX-817 census), but several claims encode today’s repo snapshot (2 goals,inMemoryStores, noopenChannels). After the implementation PR lands, this script will go red unless it is retired or rewritten. Consider a one-line sunset rule inPLAN.md(e.g. “at S8, delete or re-home gap-check claims into goal controls”) and avoid bakingRun 2026-09-22: PASSinto Settled prose.- Two artifact legs (S3 + S4 + V3) — defensible for BR-14/BR-15, but this is the largest ongoing maintenance surface (remote repo wiring + leg naming + exercising both paths). If the owner’s read of D1 is “outside the process” not “outside the machine,” the cheaper bare-repo-at-path path in DECISIONS is worth a deliberate yes/no at sign-off rather than defaulting to dual legs.
- D3 vs ER-Collab — you already flag duplication risk; if FIX-1457’s collab producer is likely this cycle, deferring channel driving here (direct EM
filefor this proof only) would be a materially smaller implementation — at the cost of not closing ER-DevForce’s “channels used honestly” line item in this issue. - S8 scope — running and appending verdicts for the never-run commit sibling is good hygiene but expands the implementation PR; fine if intentional, otherwise could be a tiny follow-up issue so FIX-1496 stays “ship the artifact proof.”
- POC negative control for channel —
channel-is-openedplants a comment matchingopenChannels, so it tests the checker’s regex, not that wiring was added. Fine for spec review evidence if labeled that way; don’t treat it as integration coverage.
Performance (implementation heads-up, not blocking this spec)
- Channel fan-out: ensure non-EM seats are true no-ops, not extra harness runs.
- BR-3 / S5: two condition executions are correct; share one checkout setup.
- V6 token scan: read lab tree once, don’t re-walk per token.
Approval stance
I’m not blocking merge on direction — the compose-not-invent plan is coherent. I’m also not issuing an approval in this pass because the spec bulk and dual-leg/channel choices are worth one conscious trim-or-confirm pass at the gates above. If you confirm dual-leg + D3 + S8 are intentional scope, I’d be comfortable approving the spec as-is.
(Automation simplify review — no code changes pushed.)
Sent by Cursor Automation: Review For Best Approach
| |---|---|---|---| | ||
| | S1 | `goals/devforce-lab/lab` · the authored brief | Rewrite the feature brief around an **executable** done-condition: an exported greeting function plus a test the repository's own runner picks up, and the existing held-out marker carried into the pull request body. Keep the marker — the prompt is still graded for it (D2) | BR-3 BR-12 | | ||
| | S2 | `goals/devforce-lab/lab` · the host | Open the declared feature channel (`channelInstances` + `openChannels`, as both sibling labs do) and expose posting on it. The EM seat files its row in answer to the post rather than through a direct action call (D3) | BR-6 BR-7 BR-8 BR-9 BR-10 | | ||
| | S3 | `goals/devforce-lab/lab` · the artifact's repository | Give the scratch repository a **real** remote and a second construction mode: today's temp-dir repository for the default leg, and a configured remote for the credentialed leg. Name the leg in what the helper returns so the verdict can report it (D1) | BR-1 BR-14 BR-15 | |
There was a problem hiding this comment.
Simplify / two-leg surface area: S3+S4+V3 is the biggest ongoing complexity in an otherwise “four gap” delta (remote repo modes, leg naming, both legs exercised). If sign-off is really about falsifiable “real work,” consider whether the default temp-repo leg could remain the only automated gate in CI, with the credentialed PR leg documented as the human release run — still named in the verdict, but not doubling lab code paths. If dual legs are intentional (BR-14/15), a single sentence in DECISIONS “Decided, not asked” would close the loop.
| | S5 | `goals/devforce-lab/lab` · the acceptance gate | Execute the brief's condition in the produced tree, and the same condition against the base ref. Both halves, or the leg proves nothing (D2) | BR-3 BR-4 | | ||
| | S6 | `goals/devforce-lab/it-ships-an-artifact-a-person-can-open/` · **new sibling goal** | The runner, its `goal.md` (outcome · input · signal · anti-game · controls · verdict log), and the controls below. Reuses `openLab` with the S2–S5 options; **does not edit either existing check** | all | | ||
| | S7 | `goals/devforce-lab/lab/README.md` | Extend *What this directory owns* and *What it works around* for the channel door and the two legs. Record that the artifact now leaves the run | — | | ||
| | S8 | The verdict logs | Run the new proof **and** the never-run `it-commits-from-the-seats-own-file`, and append a dated row to each. Appending only — never rewrite an existing row | BR-17 | |
There was a problem hiding this comment.
Scope trim (maybe): Appending a verdict for it-commits-from-the-seats-own-file is virtuous but not required to prove the new artifact claim. If FIX-1496 is already carrying channel + PR + product grading, consider filing “run the commit sibling once” as a sibling issue so this PR stays one proof.
| run the brief's condition against the base ref → fails (BR-3) | ||
| ``` | ||
|
|
||
| **POC:** [`poc/gap-check/`](poc/gap-check/README.md) — a Node script that re-derives the twelve |
There was a problem hiding this comment.
POC sunset: Please add an explicit implement-time rule: after S8, either delete gap-check, or rewrite claims 1–3 (goal count, tmpdir artifact, in-memory stores) so the script doesn’t become a permanent footgun that fails on the very PR that closes the gaps.
| shipped; that remains true and remains irrelevant here. | ||
| - **The gap table is four rows, not more** — [`poc/gap-check/`](poc/gap-check/README.md) asserts | ||
| all twelve facts the spec rests on, including a totality assertion over every TypeScript file | ||
| in the lab, and goes red under four planted defects. Run 2026-09-22: `PASS — 12 claims held`. |
There was a problem hiding this comment.
Embedding Run 2026-09-22: PASS in Settled couples merged spec text to a snapshot; future re-runs will drift without editing DECISIONS. Prefer “re-run gap-check” as the settled fact, with the dated row living only in the POC README or a journal entry.
| 2. **[D2](DECISIONS.md#d2) · The proof grades what the run produced, against a condition the | ||
| brief stated first and a machine executes.** *If wrong:* every future DevForce brief owes an | ||
| executable acceptance condition, and a brief that cannot state one cannot be proved this way. | ||
| 3. **[D3](DECISIONS.md#d3) · The row is filed in answer to a post on the feature channel, not by |
There was a problem hiding this comment.
D3 is the thinnest product choice I’d still pressure-test at sign-off: pentest already proves post→seat on the same primitive, and DECISIONS notes ER-Collab may duplicate this. Cleaner alternative: keep channel composition for a follow-up epic issue and let this proof file via EM action (middle path unchanged) while you land artifact + product grading (D1/D2) first. Not saying that’s better — only that it’s the largest incremental cost for “thinness.”
| } | ||
| if (plant === "channel-is-opened") { | ||
| tree = tree.map(([p, t]) => | ||
| p.endsWith("lab/host.mts") ? [p, `${t}\n// planted: await openChannels(channels, {});\n`] : [p, t], |
There was a problem hiding this comment.
The channel-is-opened plant only proves the openChannels regex goes red when a comment is injected — not that real host wiring is missing/present. Worth one sentence in the POC README so reviewers don’t over-read this as integration coverage (claims 5–8 have no planted red path at all).
| @@ -0,0 +1,264 @@ | |||
| #!/usr/bin/env node | |||
| /** | |||
There was a problem hiding this comment.
Minor simplify: ~25 lines of file header largely duplicate poc/gap-check/README.md. For a throwaway checker, a short pointer to the README would cut noise (FIX-817’s census script is similarly verbose — not a blocker).
| | BR-10 | The channel is opened without an org | Refused at the transport door, as today | Existing gate (BR-17 there), unchanged | | ||
|
|
||
| ## The run, and what survives it | ||
|
|
There was a problem hiding this comment.
Fourth visual of the same two-lane diagram (SVG also in SPEC + figure file). If you want a thinner spec pack, pick one canonical figure and link elsewhere.
jhoffner
left a comment
There was a problem hiding this comment.
second-look: PR #2023 (spec/FIX-1496)
Verdict: Appropriately scoped — no candidate survived the calibration gate as an unflagged, net-positive cut.
Scope: diff → +925 / −0 across 8 files, all new (spec PR, nothing under packages/): 5 spec docs (~504 lines prose), 1 generated SVG figure (~101 lines), and a throwaway poc/gap-check/ (264-line script + 56-line README).
| # | Finding | Lens | Recommendation | Est. Δlines | Sev | Conf |
|---|---|---|---|---|---|---|
| — | none passed the gate |
Why nothing made the table
I ran the five lenses (Premise, Requirement origin, YAGNI, 80/20, Hindsight) against the spec's
own proposed surface — D1 (PR-on-a-throwaway-repo + credentialed/default leg split), D2
(execute a pre-stated acceptance condition against the produced tree), D3 (file the row through a
channel post rather than the EM seat's action directly) — plus the new sibling goal (S6) sized
against precedent.
The result: the three places where this spec could have been overbuilt are already the spec's
own Sign-off #1–#3, each carrying a named cheaper alternative, a stated falsifier, and (D1, D3)
an explicit "what would change my mind." Re-raising them here would just be restating the
sign-off surface the author already built for the human reviewer, not adding a finding:
- D1's costliest fork (a real GitHub repo + PAT + credentialed leg vs. a bare repo at a
declared local path) is the exact trade this skill would otherwise flag — but D1 already names
the cheaper alternative (X1) and the condition under which it should win ("if the owner reads
'exists outside the run' as outside the process..."). Nothing to add. - D3's channel leg (BR-6–BR-10, S2, V1/V2) is the other candidate — the decision doc itself
says it should be dropped if ER-Collab's producer lands first and takes this leg. I checked:
specs/epics/FIX-1457/BUSINESS-RULES.mdstill lists ER-Collab as "No producer" / not filed,
so the condition that would kill D3 hasn't fired. The channel leg is live scope, not smuggled
scope. - S6 (new sibling goal vs. extending
it-commits-from-the-seats-own-file) is explicitly
"Considered and dropped" inDECISIONS.mdwith a concrete cost (rewriting a check invalidates
its verdict log) — a documented call, not an oversight. Its proposed size (≈10 checks + 4
controls) also lands well inside the range of the two existing siblings
(it-wakes-the-seat-a-file-declared: 798 lines;it-commits-from-the-seats-own-file: 298
lines), so it isn't ballooning relative to precedent. - S3/S4's two-leg construction (temp repo vs. real remote; commit-probe vs.
ghprobe) is
the direct cost of D1 and is required by BR-15 ("re-runnable a year later, no network/token") —
not independent surface.
improve-codebase-architecture lens
Checked whether this PR is itself the moment to refactor something it touches. One candidate:
PLAN.md S2 has the implementer write a third copy of the "wrap the session client to inject
orgId because openChannels doesn't thread one through (FIX-1412)" workaround —
goals/pentest-lab/lab/host.mts and goals/manager-queue-lab/lab/host.mts each already carry
their own copy (with pentest-lab's own ~15-line load-bearing comment restating why). A third
lab is the point where "one adapter is hypothetical, two is real" tips into "extract it." I'm
not raising this as a finding — the PR's own review contract puts "which helper, how a
function is decomposed" out of scope, and second-look's lane explicitly excludes
cross-file pattern duplication (that's audit-coherence's question, not this skill's). Flagging
it here only as a non-blocking follow-up worth a ticket, the same way PLAN.md → Follow-ups
already logs comparable known debt (the conductor goal's missing verdict rows, the coder
kind's doubled board declaration).
Considered & deemed justified
D1(PR on a throwaway repo, three falsifiable properties) — kept; already the spec's own
primary sign-off item with a named cheaper alternative and its trigger condition. Nothing to
add on top of what's already asked of the reviewer.D2(grade the product against a pre-stated, executable condition) — kept; the rejected
alternative (keep grading only the prompt) is the exact hole ER-DevForce exists to close, and
D2 is explicit that this is a real, bounded limit ("a brief that cannot state a condition can't
be proved this way"), not unbounded new surface.D3(channel-driven filing) — kept; its own kill-condition (ER-Collab producer landing first)
hasn't fired (verified againstspecs/epics/FIX-1457/BUSINESS-RULES.md, still "No producer").- S6, the new sibling goal and its ~10 checks/4 controls — kept; proportionate to the two
existing sibling goals (298 and 798 lines) it sits beside, and extending an existing check
instead was considered and dropped for a stated reason (invalidates that check's verdict log). poc/gap-check/(264-line script, 56-line README) — kept; it's throwaway evidence explicitly
out of line-level review per the PR's own contract, isolated from build/test/lint discovery
(verified againstknip.json'sspecs/issues/*/poc/**ignore entry), and its two claimed
properties (a totality assertion + four negative controls actually observed going red,
2026-09-22) are the two things a hand-rolled checker usually lacks — proportionate to what it's
checking.
Second-look lens only — line-level correctness and the spec's own "in scope to challenge" list
(problem framing, decisions, business-rule coverage) are for a human/direction reviewer, not this
pass.
Generated by Claude Code
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8563d52402
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| + The repository's test run reports at least one passing test and no failing | ||
| + ones. Before your change it reports none, so an untested module is not done. |
There was a problem hiding this comment.
Assert the requested greeting, not merely any passing test
A run that ignores the brief can add an unrelated always-passing test—or a vacuous test beside a broken greet—and still satisfy this condition. That lets the row complete despite BR-4 and makes PLAN V5's ignores-the-brief control incapable of proving irrelevant work is rejected; use a pre-stated, independent check that imports and asserts the required greet(name) behavior.
Useful? React with 👍 / 👎.
| |---|---|---|---| | ||
| | BR-6 | An operator posts on the feature channel | The channel opens, the post lands in its transcript, and the EM seat is reached | Goal | | ||
| | BR-7 | The EM seat is reached by that post | It files exactly one row on the feature board, addressed to the `coder` assignee | Goal · one row, not one per member | | ||
| | BR-8 | The post reaches the other declared members | No board row is filed by any of them, and the reviewer seat is dispatched nothing | Goal · control `reviewer-files` | |
There was a problem hiding this comment.
Distinguish channel delivery from reviewer work dispatch
When the post reaches all declared members, the reviewer necessarily receives a dispatch: defineChannelFlow runs its notify block once per member, and the sibling lab implements delivery with a dispatcher targeting that seat. Since the reviewer is declared in CHANNEL.md, the baseline cannot both reach it and produce no reviewer dispatch record, while V2 explicitly treats such a record as failure. Make the rule distinguish the expected channel-notification dispatch from an unwanted board/harness work dispatch, or stop requiring delivery to the reviewer.
Useful? React with 👍 / 👎.
| // `parentage` is provenance, which FIX-1440's own owner amendment keeps. | ||
| // --------------------------------------------------------------------------- | ||
| { | ||
| const browse = tree.filter(([, t]) => /\/children\b|childSessions|listChildren/.test(t)); |
There was a problem hiding this comment.
Detect the canonical child-session API in the gap check
This regex omits the actual client method listChildSessions, so a classified lab file can browse child sessions through the exact surface FIX-1440 removes while Claim 5 still reports green. Reproducing this by adding a client.sessions.listChildSessions(...) call to lab/host.mts leaves all 12 claims at PASS, which makes the spec's settled dependency conclusion unsafe when the checker is re-run at implementation time.
Useful? React with 👍 / 👎.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Direction unchanged. Scope trimmed and three real defects fixed. Codex P1 — the acceptance condition was satisfiable by vacuous work. "A passing test exists" is met by any unrelated passing test, or by a vacuous test beside a broken greet, which left the ignores-the-brief control unable to fail — the control that makes D1 more than taste. The brief now names a contract (greet(name) from a named path, stated behaviour for empty and non-empty), and the acceptance check is the requester's: it imports the named export, asserts both behaviours, runs from outside the checkout, and the run cannot edit it. V5 grows to three controls that must all go red. Codex P1 — BR-8 conflated two dispatch kinds. Verified in code: the notify block runs once per declared member, but declares its own targets, and a member absent from the address map is recorded and skipped. So the rule was ambiguous rather than unsatisfiable. It now forbids only a board/harness WORK dispatch to the reviewer; a channel notification is expected. V2 grades the board dispatch record by flowId. Codex P2 — gap-check had a hole under a conclusion already passed upward. The pattern spelled childSessions lower-case and could not match listChildSessions, the canonical client method and the exact call claim 5 was about. Reproduced. Pattern is now case-insensitive and anchored on the canonical name; the case is a planted control. Re-run: the FIX-1440 conclusion still holds, but its evidence was not sound until now, and DECISIONS.md says so. Scope, per coordinator: channel driving moves from a sign-off decision to a recorded constraint (ER-DevForce's ratified wording carries it, verified); two artifact legs collapse to one automated gate with the PR as a documented human release run; running the never-run commit sibling splits out to FIX-1501. Also: gap-check gains an explicit sunset rule (deleted at S8, two claims move into the new goal), four more negative controls, one canonical figure with the rest cross-linked, and Cursor's three implementation notes recorded verbatim. Corrected two stale premises relayed in review rather than repeating them: ER-Collab's producer exists (FIX-1497; the merged epic spec is stale), and openChannels takes no orgId and needs no wrapper — FIX-1443's title says otherwise and is wrong about its own resolution; FIX-1442 is what closed it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
|
Folded in The three scope choices — confirmed1. Channel driving stays (D3 → not a decision at all). Verified against the epic rather than asserted: ER-DevForce is worded "One DevForce path completes and produces a real artifact … with seats and channels used honestly rather than stubbed past", and the epic's The ER-Collab duplication risk is recorded as sequencing, not a fork: that producer exists (FIX-1497, Backlog), and if it lands the channel leg first this proof reuses it rather than re-building. 2. One automated gate, not two. Cursor was right that S3+S4+V3 was the largest ongoing surface. CI now runs a single leg — the run pushes to a bare clone, so the artifact outlives the process with no network and no credential. The pull-request release run is the same path pointed at a real remote, documented in 3. Three defects, reproduced and fixedThe acceptance condition was satisfiable by vacuous work. This was the important one. "A passing test exists" is met by any unrelated passing test, and by a vacuous test beside a broken BR-8 conflated two dispatch kinds. Checked in code before rewriting, and the finding is slightly different from the report:
Worth recording: this checker had a totality assertion and four controls and still had a hole, and it was found by reproducing, not reading. The controls covered the claims I thought to perturb, which is the set least likely to contain the hole. The POC README now says so, and also warns that a control planting a comment tests the regex and not the wiring — it is not integration coverage. Two stale premises corrected rather than repeated
Also foldedOne canonical figure (the SVG), with Running the never-run commit sibling is now FIX-1501 — related, not blocking. Still awaiting the human direction gate; nothing here reopens it. Generated by Claude Code |
…owned (FIX-1457) Post-merge amendment to the retained epic spec at specs/epics/FIX-1457/, on a new PR from main. #1944 stays the merged review record and is not touched. Three changes, and one of them is a correction: - ER-DevForce and ER-Collab stop reading "No producer". FIX-1496 (In Spec Review, #2023 @ 25e7507) and FIX-1497 (Backlog, no spec) take them. FIX-1496's artifact cut is recorded in the epic's own words: one automated leg pushing to a bare clone at a declared path, resolving after the goal's process exits with no gh, no token and no network; the credentialed PR leg documented as the human release run. Channels are recorded as inside the ratified criterion, not optional. - ER-Devtool's row split is corrected from three-and-three to two-and-one-and- three. FIX-1481's spec deferred checklist row 5 on the claim that FIX-1477 PR-C already owned the reader. That claim was false: FIX-1477's Roster reads workforce/roster/*, FIX-1475's collection, while row 5 names inventory/*. Row 5 went to FIX-1502, blocked by FIX-1486. Recorded in EVOLUTION.md as a correction, with how it was caught. - ER-26 is new: no exit proof's run is graded before FIX-1496 stands a live hired Workforce up. It fences the runs, explicitly not FIX-1481's or FIX-1502's code PRs. Row 6 is the sharp case — no tree in the repository has a sealed document today. Open 1 is replaced rather than answered: the staffing gap closed, and whether W5 exits on five checklist rows of six is now in front of the owner, six-part form in DECISIONS.md. All three figures redrawn and rendered in both themes; no text overflows, measured in-browser rather than estimated. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
D1's heading still described the pre-trim shape ("a pull request on a
separate throwaway repository") while PLAN.md S3, BR-14/BR-15 and the
Decided-not-asked item all carried the enacted cut. The decision is
unchanged; the document disagreed with its own plan.
The heading, the Instead-of / Because / Locks-in rows and the decision
tree node now state it: work at an address that outlives the run — a
pushed bare clone on the one automated leg, a pull request for the
release run. The three falsifiable properties are untouched.
Two consequences of the same drift, swept while in there:
- SPEC.md's sign-off line 1 mirrored the old heading, and a card that
changed beside a sign-off that did not is the same defect. Also its
people table ("the pull request's address" in a verdict log that on
the automated leg holds the clone address) and the figure's alt text.
- The brief's diff told the seat to put the marker in a pull request
body, which no longer exists on the leg CI runs. It is now the commit
message, which is true on both.
"What would change my mind" is restated rather than kept verbatim: half
of it already fired. It said a bare repository at a declared path would
be cheaper if "outside the run" meant outside the process — and round 1
took exactly that for the automated leg. What remains open is whether
the release proof also settles for the clone, with a recommendation
against and the reason.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz


spec(FIX-1496): ER-DevForce proof — thinnest DevForce path ships a real artifact
NOT RUNPASSwith the artifact's address in it/tmpghThe five stages are the same in both lanes and the middle three are untouched. Only the two ends move, plus two properties of the run.
How: the research finding is that ER-DevForce is nearly built and has never been run.
goals/devforce-lab/it-commits-from-the-seats-own-filealready drives a real Claude Code agent through a file-declared seat and grades the commit it leaves — complete, type-checked, and loggedNOT RUN. This spec is the four-gap delta that makes its artifact survive the run and its product judgeable, then runs it. Nothing underpackages/changes.Sign off
Open: none. Number 1 is the one to weigh — it is the question the Architect deliberately left open, answered here as a proposal with a falsifier rather than left open again. Reasoning and what lost: DECISIONS.md. The cases: BUSINESS-RULES.md.
Reviewers · look here
Not here: Devtool observability of the run (FIX-1481 owns ER-Devtool), CyberForce, kitchen-sink, any Lab product surface, and any change to the board's provenance or to
packages/.Verified rather than assumed, because the brief flagged it: FIX-1440 is
Spec Approvedand unshipped, and it does not fence this work — the lab reads dispatch parentage only as provenance, which FIX-1440's owner amendment explicitly keeps, and reads nothing from the browsable child-session surface it removes.Spec · Decisions · Rules · Plan · Docs · Linear FIX-1496 · epic FIX-1457 (ER-DevForce) · builds on FIX-1426, FIX-1410, FIX-1385, FIX-1405, FIX-1430, FIX-1442 · merges after human direction approval and required checks
POC — `poc/gap-check/`, throwaway evidence, zero review rounds
The question it answers: are the four gaps this spec claims actually the gaps, or is the table hand-counted? It re-derives all twelve facts the spec rests on straight from the repository — two goal checks with one model-backed and no PASS recorded, the artifact's repository under
tmpdir(),inMemoryStores(), noopenChannelscall in the lab while both sibling labs have one, and no read of the child-session surface FIX-1440 removes.Two properties it was built to have: a totality assertion (every TypeScript file under the lab is classified, so a file nobody listed cannot hide), and negative controls that were actually run —
--plant listnames four, each perturbs one thing and each was watched going red on exactly the claim it perturbs.Result, 2026-09-22:
PASS — 12 claims held, 0 failed. The premise held; nothing in the design changed because of it. It is throwaway: nothing imports it, it is not a workspace package, andspecs/issues/*/poc/**is already in knip's ignore list.How to review this — altitude, what's in scope, what's deliberately unsettled
This is a direction set, not an implementation. Reviewing it well means
answering one question: is this the right approach?
In scope to challenge:
SPEC.md— are we solving the right thing, for the people named?docs/philosophy.md?DECISIONS.md— that's the sign-off surface.BUSINESS-RULES.mdmisses, or a rule that would invalidate the design.DOCS.mdand their fit with the rules; a missing ormisleading lineage claim in conditional
EVOLUTION.md.Out of scope — deliberately unsettled here, and owned by the implementing agent:
PLAN.mdpins on purpose.PLAN.mdleft open on purpose — it is directional by design, and a gap at thataltitude is intended, not an omission.
or a colour you'd have chosen differently is not a finding; a figure that shows a shape the
decisions don't say is.
PLAN.mdmay include a rough pseudocode sketchshowing the shape of the proposed solution. It is knowingly incomplete, is not real code,
and is not what will ship. Review it for directional viability only. Do not report
that it lacks error handling, omits edge cases, names things that don't exist in the repo, or
wouldn't build: all of that is true on purpose.
poc/are retained,not production code. Read them for directional evidence, not production completeness.
Their isolation from production/default discovery and absence of secrets or generated
dependencies are in scope; retention is not permission to weaken repository checks.
One request, if you are an automated reviewer: the two lists above are the whole difference
between a useful review of this document and a long one. Volume is not signal here — a single
finding above the line is worth more than twenty below it.
Feedback in the second list is welcome and gets recorded verbatim in
PLAN.md → Notes from reviewfor the implementer to weigh against real code. It will not be argued with, and itwill not be folded into the design prose. Please don't re-raise it: one mention is enough.
The one exception is the sketch and the POC. Line-level feedback on either is dropped, not
recorded — there is nothing for an implementer to weigh about code that isn't shipping. Feedback
about their direction is not line-level and is treated like any other above-the-bar finding.
Direction approval does not waive merge-time required checks, approvals or thread policy.
Optional comments do not require another design round merely to reach zero comments.
🤖 Generated with Claude Code
https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
Generated by Claude Code