Observer oracle: verdicts the v0.46.0 tag got WRONG have no gate once a round makes them right
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, testing
Research direction
The gate lives in tools/observer_oracle/floor.json, the score.py checker, and the observer-oracle make target. Read docs/design/phase2-numbers.md §8 Round 3 first, then how --declared is handled in score.py. Done means a decision between options (a) and (b) is recorded in the issue; if (b), a plant that reverts the travel bound turns make observer-oracle red on harmonic@300 converged, with a matching row in tools/selftests.txt.
Written by the indexing model from the issue text.
Description
tools/observer_oracle/floor.json holds only the verdicts the v0.46.0 anchor got RIGHT (1872 arm verdicts on non-capability rows), and --declared covers only capability rows. A verdict the tag got wrong and a later round fixes is therefore unprotected: a regression back to the wrong answer passes make observer-oracle.
Measured in the Phase 2 R3 design (#1758 R3.0, docs/design/phase2-numbers.md §8 Round 3): the proposed R3 rule makes 42 previously wrong verdicts right (a Python model of the rule, port-checked 708/708 against the branch binary), including #1752's harmonic, log_n and ml_loss_power converged=true reads. None of them is a floor verdict, so the oracle cannot see a plant that removes the #1752 fix; only a MAP row (O2.harmonic-not-converged) can.
Options: (a) per-mechanism MAP rows only (the R3.0 proposal, no new machinery); (b) score.py --require FILE, the inverse of --declared: listed verdicts must be right, and a listed verdict the corpus no longer has is STALE.
Done when
- A decision between (a) and (b) is recorded here.
- If (b): a plant that reverts the travel bound turns
make observer-oraclered onharmonic@300 converged, and the self-test row intools/selftests.txtcovers it. - If (a): every R3 mechanism whose fix is invisible to the floor has a MAP row named as a plant's red check in the design's plant table.
— Claude (builder, Claude Code)
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 6h 32m
- Merged PRs (30d)
- 285
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InauguralSystems/EigenScript
-
good first issue needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
InauguralSystems/EigenScript#2347 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 82/100
InauguralSystems/EigenScript#2335 · 1 comment ·
Maintainers usually reply within 1 day
-
area:embed kind:bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
InauguralSystems/EigenScript#2311 · 1 comment ·
Maintainers usually reply within 1 day
-
area:gates kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
InauguralSystems/EigenScript#2305 · 1 comment ·
Maintainers usually reply within 1 day
-
area:ci bug found-by:duet-audit
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
InauguralSystems/EigenScript#2283 ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FujiNetWIFI/fujinet-config#379 ·
Maintainers usually reply within 1 day
-
Ship /Local/Applications, the Local domain's Applications folderPossibly taken @pkgdemon claimed this today. Openarea:base enhancement
Difficulty 1/5 Under an hour Newbie friendliness 94/100
nextbsd/nextbsd-userland#612 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#125543 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
colbymchenry/codegraph#3277 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100