Problem
Epic #8107's core open design question, now unblocked (#8082 closed 2026-07-23). AMS records fired events for its four eligibility-exclusion reasons (recordEligibilityExclusionSignals, packages/loopover-miner/lib/discover-cli.ts — real runs only), but recordHumanOverride has zero call sites in the miner package: the adapter implements it (signal-tracking-store.ts:95) and nothing calls it. Without override ground truth, AMS's exclusion rules can never be precision-scored or backtested — the corpus stays 100% undecided forever. packages/loopover-miner/docs/ams-signal-tracking-design.md documents this gap with two proposed mechanisms: an operator discover mark-eligible override command, or a profile-diff signal (a later profile re-extraction contradicting the exclusion). ORB faced the analogous question in #8106 (positive-confirmation design); its answer may or may not generalize to AMS's action shape (a candidate being excluded from discovery, vs a PR being blocked).
Requirements
Deliverables
Links & Resources
Boundaries
Decision + doc + follow-up filing only; no capture code lands under this issue.
maintainer-only — calibration-vocabulary authority; the wiring may become contributor work per the decision.
Problem
Epic #8107's core open design question, now unblocked (#8082 closed 2026-07-23). AMS records fired events for its four eligibility-exclusion reasons (
recordEligibilityExclusionSignals,packages/loopover-miner/lib/discover-cli.ts— real runs only), butrecordHumanOverridehas zero call sites in the miner package: the adapter implements it (signal-tracking-store.ts:95) and nothing calls it. Without override ground truth, AMS's exclusion rules can never be precision-scored or backtested — the corpus stays 100% undecided forever.packages/loopover-miner/docs/ams-signal-tracking-design.mddocuments this gap with two proposed mechanisms: an operatordiscover mark-eligibleoverride command, or a profile-diff signal (a later profile re-extraction contradicting the exclusion). ORB faced the analogous question in #8106 (positive-confirmation design); its answer may or may not generalize to AMS's action shape (a candidate being excluded from discovery, vs a PR being blocked).Requirements
HumanOverrideEventvocabulary: what concrete, real event means"reversed"(this exclusion was wrong) and what means"confirmed"— evaluating at minimum the two mechanisms inams-signal-tracking-design.mdplus whether Design a positive-confirmation ('this automated decision was correct') signal #8106's ORB confirmed-signal decision generalizes; ground each candidate in AMS's actual event-ledger vocabulary, not hypotheticals (the audit Epic: AMS parity for the ORB backtest/calibration system (blocked until ORB side is complete) #8107 item 1 called for).ams-signal-tracking-design.mdto match, and file the wiring follow-up issue — contributor-scoped only if the decided shape is fully mechanical with zero interpretive room, maintainer-only otherwise.Deliverables
ams-signal-tracking-design.mdupdated from "nothing calls it yet" to the decided designLinks & Resources
packages/loopover-miner/lib/signal-tracking-store.ts,packages/loopover-miner/docs/ams-signal-tracking-design.mdBoundaries
Decision + doc + follow-up filing only; no capture code lands under this issue.
maintainer-only — calibration-vocabulary authority; the wiring may become contributor work per the decision.