Skip to content

docs(scoreboard): the gate 2 row was wrong in both directions (#167) - #188

Merged
kjgbot merged 1 commit into
mainfrom
docs/167-gate2-scoreboard-row
Sep 5, 2026
Merged

docs(scoreboard): the gate 2 row was wrong in both directions (#167)#188
kjgbot merged 1 commit into
mainfrom
docs/167-gate2-scoreboard-row

Conversation

@kjgbot

@kjgbot kjgbot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Closes #167.

The row claimed gate 2 was missing "a test proving a duplicate event does not double-execute". That was already false when #167 was filed — the test existed and was mutation-bound — and tonight's work went further, so the row now understates progress and the gate at the same time.

What is actually done

Each claim checked against main rather than remembered:

property where
sequential duplicates deduped #14
concurrent racing deliveries, under the production topology of one Engine per protocol request #171
claims survive the process that made them #171 (boot id), #182 (panic unwind)
resume adopts only a journal it can actually use #177, #186

What is still missing — narrowly

The RFC-0001 Appendix A wake-time context contract. wake_context carries an epoch summary and the triggering event, but nothing specifies what is guaranteed present, or that a resumed run observes the same context rather than a recomputed one.

The correction #167 cared about most

The row has been understating the gate. RFC-0001 §3's bar is hn-monitor running as a relayflow in production, on its real events, with zero bespoke persistence — not a passing test suite. Someone scoping gate-2 work off this row alone would have mis-sized it in both directions, which is exactly what #167 raised.

Documentation only; no counts in the row, deliberately — counts drift with the base, PR numbers and test names do not.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FtQSAcGDta5VH9xiZFT4sR

#167. The row claimed gate 2 was missing "a test proving a duplicate
event does not double-execute". That was already false when the issue was
filed -- the test existed and was mutation-bound -- and tonight's work
went further, so the row now understates progress and the gate at once.

Dedupe, with each claim checked against main rather than remembered:

  sequential duplicates                     #14
  concurrent racing deliveries, under the   #171
    production topology of one Engine per
    protocol request
  claims that survive the process that      #171 (boot id), #182 (panic)
    made them
  resume adopting only a journal it can     #177, #186
    actually use

Still genuinely missing, and stated narrowly: the RFC-0001 Appendix A
wake-time context contract. `wake_context` carries an epoch summary and
the triggering event, but nothing specifies what is GUARANTEED present,
or that a resumed run observes the SAME context rather than a recomputed
one.

And the correction #167 cared about most: the row has been understating
the gate. RFC-0001 s3's bar is `hn-monitor` running as a relayflow IN
PRODUCTION, on its real events, with zero bespoke persistence -- not a
passing test suite. Anyone scoping gate-2 work off this row alone would
have mis-sized it in both directions.

No counts in the row, deliberately. Counts drift with the base; PR
numbers and test names do not.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FtQSAcGDta5VH9xiZFT4sR

Session-Id: c228933d-4f94-4d83-9a9a-daf3c83b94f1
@coderabbitai

coderabbitai Bot commented Sep 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 50 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: e7ef6f5a-c2af-4408-8e94-7e31be4974e8

📥 Commits

Reviewing files that changed from the base of the PR and between f00d7ce and 8e57b17.

📒 Files selected for processing (1)
  • ops/SCOREBOARD.md

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

Comment @coderabbitai help to get the list of available commands.

@kjgbot
kjgbot merged commit c6ee55c into main Sep 5, 2026
1 of 2 checks passed
@kjgbot
kjgbot deleted the docs/167-gate2-scoreboard-row branch September 5, 2026 19:11
kjgbot pushed a commit that referenced this pull request Sep 5, 2026
 closed

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FtQSAcGDta5VH9xiZFT4sR

Session-Id: c228933d-4f94-4d83-9a9a-daf3c83b94f1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gate 2: SCOREBOARD row overstates what is missing — dedupe is already tested and mutation-bound

1 participant