[finding] a control can be correct when written and decay into an impostor-satisfied one with NO edit to it or its fixture — measured on union-fold-command-parity, which stopped pinning the union fold when a sibling mechanism reached the same doors #19371

Activity

1. os-project-manager

   added

   finding

   pm:dispatched

   and removed

   pm:queue

   on Sep 20, 2026
2. os-project-manager

   self-assigned this

   on Sep 20, 2026
3. os-project-manager commented on Sep 20, 2026

   

   os-project-manager

   on Sep 20, 2026 – with Claude

   CollaboratorAuthor

   More actions

   Claim — domain:cli execution PM seat #6024

   Claim: PM loop round 82
   Session: `session_01QCdUBjM47SxioST9z5Zwdf`
   Branch: `claude/issue-19371-control-decay-trigger-feasibility`
   Worktree: `objectstack-issue-19371`
   Domain: `domain:cli`
   Seat: `domain:cli#1`
   File surface: ⚠️ NOT PREDETERMINED — this round's deliverable is a MEASUREMENT and a written verdict. Any code is a throwaway probe unless the verdict says otherwise (stop on breach; explain in the report)
   Container & model: `M`, `mode:subagent`, `model: opus` — the surface is undetermined so no path-derived mandate exists to quote; judged default judgment tier, ⛔ not the floor: the deliverable is a FEASIBILITY VERDICT, and the failure mode is building a gate that fires on the wrong thing.
   Clause-②: no
   Thread-read: 5750829328
   Serial constraints cleared: nothing in flight in this lane. PRs #19405 and #19406 are armed on `packages/runtime/` and `packages/cli/src/utils/collect-docs.ts` — ⛔ neither is this round's surface.
   

   ⭐ The deliverable is a VERDICT, ⛔ not a gate

   This card records a class:

   a control can be correct when written and decay into an impostor-satisfied one with no edit to it or its fixture, because a sibling mechanism reaches the same doors later.

   ⛔ Do not open this as a repo-wide test audit. The #18897 sweep already ablated 21 packages/cli fixtures across 30 legs and 9 mechanisms and found exactly one instance. The base rate does not pay for a blanket sweep, and the card says so.

   ⭐ What is valuable is the trigger, not the sweep:

   when a PR adds a mechanism to a door, ask which existing controls assert something about that door's output.

   Whether that is mechanisable is the question this round answers. ⭐ "No, and here is precisely why" is a complete and valuable outcome — the same shape as #19246, which discharged by measuring that its card did not reproduce.

   What you have to work from

   The one worked instance, with full data in #18897's landing record (5750712407) and PR #19369:

   • union-fold-command-parity.test.ts was a true pin of authoringRuleUnionStack at os validate and os lint judge an EMPTY stack when a project declares its metadata only in packages[] — the ADR-0130 D4 union fold (authoringRuleUnionStack) is wired into os build alone #17069;
   • it stopped being one when [finding] os build runs a per-package authoring-rule walk os validate does not — the residue #17069 left, in the same false-clean direction #18677 and [finding] os lint is the THIRD door with the same union-only authoring-rule gap — #18677 closed two of three, and the card's own table said 2 of 2 #18778 put runPerPackageAuthoringRules on validate and lint — the same rule, same path, same refusal code on that fixture;
   • ablation: fold alone → 6/6 green; per-package alone → 6/6 green; both → 3 red;
   • ⛔ no commit to that file ever weakened it, and both [finding] os build runs a per-package authoring-rule walk os validate does not — the residue #17069 left, in the same false-clean direction #18677 and [finding] os lint is the THIRD door with the same union-only authoring-rule gap — #18677 closed two of three, and the card's own table said 2 of 2 #18778 were correct work.

   The questions to answer, in order

   1. Is "a PR adds a mechanism to a door" detectable at all? What would the signal be — a new call site into an existing dispatch/registration path? ⛔ Do not assume it is a diff-shape question; measure what the one known instance actually looked like as a diff.
   2. Given a detected door change, can "which controls assert something about that door's output" be derived — or does it require knowing what each control means? ⚠️ If the honest answer is the latter, say so; that is the verdict.
   3. What would a false positive cost? ⭐ A trigger that fires on every PR touching a shared path is worse than no trigger, because it trains people to dismiss it.

   ⛔ Fences

   ⛔ Do not build and land a gate in this round. If your verdict is "mechanisable", the deliverable is the design plus the evidence, and the seat dispatches the build separately.
   ⛔ Do not modify any existing test or fixture. ⛔ Never edit content/docs/releases/.
   ⚠️ If you write a probe to measure feasibility, it is a throwaway — say so, and prove the tree is clean afterwards.
   Changeset: likely none, since a measurement round may change no shipped byte — ⛔ but derive it from the repo's gates rather than assuming, and ⛔ do not name a level here before you know whether anything ships.
   Commit trailers model-free: Co-Authored-By: Claude <noreply@anthropic.com> plus a Claude-Session: line. English. If there is a diff, draft PR with Fixes #19371; if there is none, report and the seat closes the card on your measurement.

   ⚠️ If any part of this order is imprecise or contradicts what you measure, say so and stop rather than silently matching it — five of this seat's orders were wrong this shift and a dev caught every one.

   ---

   Generated by Claude Code
4. os-project-manager commented on Sep 20, 2026

   

   os-project-manager

   on Sep 20, 2026 – with Claude

   CollaboratorAuthor

   More actions

   os-dev-report

   {
     "issue": 19371,
     "status": "done",
     "branch": "claude/issue-19371-control-decay-trigger-feasibility",
     "pr": null,
     "session": "session_01QCdUBjM47SxioST9z5Zwdf",
     "premise_still_valid": true,
     "summary": "VERDICT: the trigger as the card phrases it is NOT mechanisable at useful precision, and the reason is the one the card names as the good outcome -- half of the derivation requires knowing what each control MEANS. Measured, not argued: (Q1) the door change IS detectable, but only at SYMBOL granularity -- the natural module-import-edge signal misses #18813 outright, because lint.ts already imported the helper module; the tightest purely mechanical signal I could build fires 8 times per 30 days on packages/cli/src/commands alone. (Q2) 'which controls assert about that door's output' is derivable (24 controls at the moment of decay); 'which of those the new mechanism can now satisfy' is not -- only 10 of those 24 name exactly one exported symbol in their docblock and most of those name a printer or a type, and the ablation itself is semantic (the two mechanisms on this very door need OPPOSITE neutral forms: identity vs empty). (Q3) 8 fires x 24 controls = 192 non-mechanical judgements per 30 days on one package's doors, against 1 known instance -- per-fire precision at most 12.5%, and that is generous. REFRAME, which is the round's residue: detection does not need the causing PR at all. The decay is directly observable as a red-to-green flip in an ablation matrix, which is meaning-free AT DETECTION TIME and O(mechanisms), not O(mechanisms squared) -- single ablation of the union fold alone already left the control 6/6 green, per the card's own table. That is a periodic job, not a per-PR gate. Not built: the fences forbid it and the seat dispatches it separately.",
     "tests": "No diff, therefore no gate is owed: `git status --porcelain` empty, `git diff origin/main --stat` empty, and `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` exits 2 with 'this branch changes nothing against origin/main (merge base 43d492ff9) -- nothing to derive'. No pnpm install, no build, no test run -- there is nothing to build. All readings are git/AST measurements over objectstack-ai/objectstack at origin/main 43d492ff98c1, window 2026-08-21..2026-09-20 proven by scripts/pm/git-history.mjs ensure (floor 2026-08-14, 3785 first-parent commits). Probes were throwaway python in the scratchpad; the worktree never held an edit. NOT MEASURED: wall-clock of one ablation-matrix recomputation -- pricing a hypothetical gate would have cost a shared-container build lap for no deliverable.",
     "mcp_calls": "0 -- no MCP GitHub tool was called, read or write",
     "api_writes": "1 -- POST /repos/objectstack-ai/objectstack/issues/19371/comments. No POST /pulls (no diff), no label writes. One `git push` of an empty branch as the routing probe and the claim's landing marker.",
     "open_questions": [],
     "out_of_scope_findings": [
       "noted, not filed: 222 of 340 packages/cli test files (65%) name no exported cli/lint symbol in their leading docblock, so no mechanical claimed-mechanism can be extracted for them. This is an observation about a convention, not a reproducible defect, a contract violation or an authoring trap -- it is filable only as a repo-wide sweep proposal, which this card explicitly argues against. Successor: none today; it would be the input to the ablation-matrix build if the seat dispatches it.",
       "noted, not filed: the card body and the dispatch both read as if #18677 and #18778 were the PRs that put runPerPackageAuthoringRules on the doors. They are the CARDS; the diffs are PR #18769 (095c7f60ae, `os validate` plus the extraction of the shared helper out of compile.ts) and PR #18813 (9bd631f3ff, `os lint`). Not an error -- citing cards is this repo's norm -- but Q1 asks what they looked like AS DIFFS, and an issue has no diff, so the translation is a required first step and is recorded here. Successor: this report."
     ]
   }

   The verdict

   Not mechanisable as the card phrases it. The honest answer is the one the card names as a complete outcome: half the derivation requires knowing what each control means. Everything below is measured over objectstack-ai/objectstack at origin/main 43d492ff98c1, window 2026-08-21 to 2026-09-20, proven covered by scripts/pm/git-history.mjs ensure (floor 2026-08-14) -- 3785 first-parent commits.

   First, a translation the questions need

   #18677 and #18778 are cards. The diffs are PR #18769 (095c7f60ae) and PR #18813 (9bd631f3ff). #18769 did two things in one commit: it extracted runPerPackageAuthoringRules out of compile.ts into utils/artifact-packages.ts, and it added the second call site on validate. So the causing diff reads as an ordinary refactor-plus-fix.

   Q1 -- detectable, but only at symbol granularity, and only where a door is a directory

   signal	fires / 30 days	catches both instances
   touches packages/cli/src/commands/ at all	207	yes
   adds any import line to a non-test command module	56	yes
   module-edge: new import of a specifier a sibling command module already imports (relative only)	19	NO -- misses #18813
   symbol-level: new named binding a sibling command module already imports	18	yes
   the above, minus fires whose target command file is new in the same commit	14	yes
   the above, restricted to bindings 2 or more sibling doors already import	8	yes

   The third row is the load-bearing negative. "A new call site into an existing dispatch path", read the natural way as a module import edge, has a 50% false-negative rate on the one known instance: at 9bd631f3ff^, lint.ts line 18 already read import { artifactPackages, packageBodyAsStack } from '../utils/artifact-packages.js' -- for its own intra-package duplicate-name advisory, per that PR's own body. #18813 added a binding, not an edge. So any implementation must parse import clauses or call sites, never module specifiers.

   The 8-fire signal is real, not noise-driven: the window contains three instances of the same family -- authoringRuleUnionStack reaching validate and lint (#17524, edaf3b2f78), lowerCallables reaching validate then lint (6b7d709b87, 0cde37d788), and the pair under study. The signal finds a genuine recurring shape. It is the follow-up that does not pay.

   ⚠️ Thresholds were chosen after seeing the answer. 8 per 30 days is therefore a floor on the out-of-sample rate, not an estimate of it. And packages/cli/src/commands/ is one door family that happens to be an enumerable directory; it is 207 of the 2038 window commits touching any packages/*/src. REST routes, kernel registration and driver dispatch have no such directory, so a repo-wide trigger needs a hand-maintained door register -- the meaning problem, relocated.

   Q2 -- the derivation splits, and only the cheap half is mechanical

   Half A, "which controls assert something about that door's output": derivable. At 095c7f60ae^, 24 of 328 packages/cli test files attach to the validate/lint doors -- 22 spawn the binary with validate or lint in argv, 2 import the command module. The victim is in the set.

   Half B, "which of those the new mechanism can now satisfy": not derivable. Two independent measurements:

   (i) The claimed-mechanism mapping does not exist mechanically. Extracting backticked identifiers from a control's leading docblock and resolving them against the 1242 exported symbols of packages/cli/src plus packages/lint/src:

   population	names exactly one	names none	names several
   all 340 packages/cli test files	71 (21%)	222 (65%)	47 (14%)
   the 24 controls on this door	10	11	3

   Of the 10 that name exactly one, most name a printer, a type or a constant -- emitJson, LintIssue, TEMPLATES, errorCodeFields -- not a mechanism. The victim is the lucky case: its pre-repair docblock named exactly one exported symbol, authoringRuleUnionStack. Its own named sibling, authoring-rule-command-parity.test.ts, names none.

   (ii) The ablation is semantic, and the two mechanisms on this very door prove it. authoringRuleUnionStack has a generic identity-shaped signature -- stack in, stack out -- and its neutral form is return the input unchanged. runPerPackageAuthoringRules returns a findings record and its neutral form is return nothing. A generic mutation engine cannot choose between them, and choosing wrong makes the leg meaningless in both directions: identity-ablating the per-package pass does not typecheck, empty-ablating the fold destroys every door at once. One hand-authored neutral form per mechanism is unavoidable.

   ⇒ the honest answer to Q2 is the latter, and that is the verdict.

   Q3 -- what a false positive costs, quantified

   8 fires per 30 days on packages/cli/src/commands alone, each asking for Half B over 24 controls: 192 non-mechanical judgements per 30 days, one package, one door family, roughly one interruption every 3.75 days.

   Against that: one known instance in the window, surfaced by the #18897 sweep, not by any trigger. Per-fire precision is therefore at most 12.5%, and that bound is generous because it credits the fire for a find the trigger did not make. The other 6 fires' follow-ups -- 144 judgements -- are NOT MEASURED, not clean: nobody ran them.

   For scale, the #18897 sweep judged 21 controls by property across 30 ablation legs and 9 mechanisms to find that one instance. The trigger would demand roughly 9 times that judgement volume per month, on one package's doors, with no ablation legs behind it -- pure reading. That is exactly the rate at which the card says a trigger becomes worse than none.

   The reframe -- the part worth keeping

   The card binds detection to the causing PR. But the causing PR is correct work whose diff contains nothing about the victim, and asking a reviewer to reason about 24 other files is the expensive half. Detection does not need the causing PR at all.

   The decay is directly observable as a red-to-green flip in an ablation matrix: for each mechanism M, record which control cases die when M alone is ablated; a cell that was red and is now green, on a control nobody edited, is the alarm.

   • It is meaning-free at detection time -- no claimed-mechanism mapping is needed, which is what kills the per-PR trigger.
   • It is O(mechanisms), not O(mechanisms squared). Read off this card's own table: ablating the union fold alone already left the control 6/6 green. The pair was needed to explain the cause, never to detect it.
   • Its false positive is a named cell, not "audit 24 controls", and the legitimate flips (control edited, fixture edited, mechanism renamed) are filterable by the diff.
   • Its cost is one recomputation of roughly the [finding] two of three per-package pins had their lit control satisfied by an ECHO, not a real survivor — at least four more fixtures were never checked against the discriminant #18897 sweep's size -- a periodic job, not a per-PR gate. ⛔ NOT MEASURED: wall-clock of one recomputation. Pricing it would have cost a shared-container build lap for a round that produces no diff.
   • Its preconditions are the honest catch: one hand-authored neutral form per mechanism, and a mechanism register -- the same register a repo-wide trigger would have needed.

   ⛔ Not built. The fences forbid it and the seat dispatches it separately if it wants it.

   The cheap thing that already works

   PR #19369's repair is the zero-per-PR-cost form of the same idea: runPerPackageAuthoringRules owns the package 'PACKAGE_ID' -- prefix on every finding it raises, so a control can assert the absence of a pedigree it must not carry. Generalised: a mechanism that can reach a door someone else's control asserts on should own a marker in its output.

   ⚠️ It is not universal, and the victim's own docblock says why: a real falsifier -- a fixture the impostor structurally cannot reach -- does not exist for this rule class, because the per-package pass is a superset of the union run for reference rules. The pedigree is load-bearing there only because it is paired with a positive control. An unpaired negative assertion would be satisfied by a prefix the suite never produces at all.

   Round state

   No diff, so no PR, no changeset and no labels. Changeset class: there is no diff to classify. skip-changeset is a label for a diff that publishes nothing; with an empty diff the question does not arise, and dispatch-gates.mjs derives no gate family. Had the verdict landed as a docs/audits/ record instead, the class would be skip-changeset -- no package manifest's files array reaches docs/, and the root package is private -- but writing that file was not asked for and would be scope this card fences off.

   The branch claude/issue-19371-control-decay-trigger-feasibility is pushed and empty (identical to origin/main); it is the claim comment's landing marker and carries no PR. Delete it at will.

   ---

   Generated by Claude Code
5. os-project-manager

   removed

   pm:dispatched

   on Sep 20, 2026
6. os-project-manager

   removed their assignment

   on Sep 20, 2026
7. os-project-manager commented on Sep 20, 2026

   

   os-project-manager

   on Sep 20, 2026 – with Claude

   CollaboratorAuthor

   More actions

   Seat closeout — VERDICT: not mechanisable at useful precision. The card is discharged by a measurement, ⛔ not by a build.

   ⭐ This is the outcome the dispatch named as complete: "'No, and here is precisely why' is a complete and valuable outcome." ⛔ No gate was built, no test was touched, and there is no diff — git status --porcelain empty, dispatch-gates --commands exits 2 with "this branch changes nothing against origin/main — nothing to derive."

   Q1 — the door change is detectable, but only at symbol granularity

   ⚠️ The natural signal is the one that fails. A module-import-edge check misses PR #18813 outright, because lint.ts already imported the helper module at line 18 for its own duplicate-name advisory. The edge existed before the mechanism arrived.

   The tightest purely mechanical signal fires 8 times per 30 days on packages/cli/src/commands alone — ⚠️ and its thresholds are hindsight-tuned to this instance, so 8 is a floor, not an estimate.

   Q2 — half the derivation is semantic, which is the verdict

   "Which controls assert about that door's output" is derivable: 24 controls were attached to the validate/lint doors at the moment of decay.

   "Which of those the new mechanism can now satisfy" is not:

   • only 10 of 24 name exactly one exported symbol in their leading docblock, and most of those name a printer, a type or a constant;
   • ⭐ the ablation itself is semantic — the two mechanisms on this very door need opposite neutral forms: authoringRuleUnionStack ablates to identity, runPerPackageAuthoringRules ablates to empty. ⇒ no mechanical rule produces both.

   Q3 — the precision bound, and why it is generous

   8 fires × 24 controls = 192 non-mechanical judgements per 30 days, on one package's one door family, against 1 known instance.

   ⇒ per-fire precision at most 12.5% — ⚠️ and that bound is generous, because it credits the fire for a find the #18897 sweep actually made, not the trigger.

   ⭐ This is the answer to Q3 as asked: a trigger firing 8×/month at ≤12.5% precision trains people to dismiss it, which is worse than no trigger.

   ⭐ The reframe — the round's real residue

   Detection does not need the causing PR at all.

   The decay is directly observable as a red-to-green flip in an ablation matrix, which is:

   • meaning-free at detection time — the semantic work moves to explaining a flip, ⛔ not to finding one;
   • O(mechanisms), ⛔ not O(mechanisms²) — single ablation of the union fold alone already left the control 6/6 green, read straight off this card's own table. ⇒ ⭐ the pair was needed to explain the cause and never to detect it.

   ⇒ that is a periodic job, ⛔ not a per-PR gate. Preconditions: one hand-authored neutral form per mechanism, plus a mechanism register.

   ⛔ Not built — the dispatch fenced it out, and the decision to build is a separate one. Recorded as #19409, with the base-rate argument against it stated alongside.

   ⚠️ A correction to this seat's order, recorded rather than buried

   The card body and my dispatch both read as though #18677 and #18778 were the PRs that put runPerPackageAuthoringRules on the doors. They are the CARDS. The diffs are PR #18769 (095c7f60ae, os validate) and PR #18813 (9bd631f3ff, os lint) — verified by this seat: both merged with matching titles, and both issues return is_pr: false.

   ⇒ my order said "measure what #18677 and #18778 actually looked like as diffs", and an issue has no diff — the instruction was literally unsatisfiable. ⭐ The dev performed the translation and recorded it as a required first step rather than silently doing it. That is the sixth order imprecision this shift and the sixth a dev has flagged.

   ⚠️ Citing cards is this repo's norm, so the card body is not wrong; ⛔ but an order that asks for a diff must name the PR.

   Card state

   pm:dispatched stripped and the assignee cleared in one write, read back. The card is discharged: the question it asked has a measured answer.

   ---

   Generated by Claude Code
8. os-project-manager

   closed this as completedon Sep 20, 2026