Repository navigation
docs(cutover): record the 2026-11-13/14 rulings; D4 superseded - #675
Conversation
Design only. D2 (14-day shadow), D3 (full pre-push set), the superseded D4 (panicbot gets an optional bridge mode; estate-rescan and bridge-gate move behind it in phase 5), R14 (finishingbot re-point, design not yet written) and the authority/ownership rulings are recorded. No workflow, enrolment or code change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZkEdznGjgTixZgjhB6
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
|
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
Codex Review Summary: ✅ CompletedThis 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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6b0903946c
ℹ️ 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".
|
|
||
| === 8.3 Decided (owner rulings, 2026-11-14) | ||
|
|
||
| D2. **Decided 2026-11-14.** The phase 1 shadow period runs **14 days**. A |
There was a problem hiding this comment.
Align phase 1 with the 14-day shadow period
This ruling makes elapsed time the phase 1 boundary, but the phase table still says to shadow for a fixed number of PRs and evaluate an agreed sample. When PR volume is unusually high or low, following that table can advance phase 2 before 14 days or prolong the shadow past the decided period. Update the phase 1 change and exit criterion to require the full 14 days.
Useful? React with 👍 / 👎.
| D4 (superseded). **Superseded 2026-11-14** (D4 of 2026-11-13 stood for one | ||
| day). The owner's reasoning: panicbot is the harness that lets panic-attack |
There was a problem hiding this comment.
Mark the replacement D4 as superseding
This paragraph contains the operative 2026-11-14 decision, yet its heading labels that decision itself “superseded”; the old 2026-11-13 D4 is already correctly marked superseded in §8.2. A phase 5 implementer can therefore read the bridge plan as withdrawn. Label this entry as revised/superseding and reserve “superseded” for the prior D4.
Useful? React with 👍 / 👎.
| be self-contained as far as it can be. Consequence: panicbot gains an | ||
| *optional* `bridge` mode (a thin subprocess call to `panic-attack bridge | ||
| triage`, same pin, same envelope discipline as `scan`). Hypatia's estate | ||
| rescan and bridge gate move behind panicbot in phase 5 instead of staying |
There was a problem hiding this comment.
Define an adapter path for the estate rescan
The optional mode described here only invokes panic-attack bridge triage, so it cannot replace the estate rescan, which §2.2 identifies as an assail run feeding verisim-data. The existing panicbot scan path emits translated fleet findings rather than the raw report consumed by that pipeline, while phase 5 requires the verisim-data shape to remain unchanged. Specify a separate raw estate-rescan mode or leave that use direct instead of moving both workflows behind the bridge mode.
Useful? React with 👍 / 👎.
| * Pin authority: `bots/*/canon/pin.toml` in gitbot-fleet. Standards reusable | ||
| pins are owned by `propagate-sha-bump.sh` with the closure audit, and | ||
| Dependabot handles third-party actions only. The pin change in standards is |
There was a problem hiding this comment.
Assign scanner-pin updates to a capable mechanism
For phase 1 and subsequent re-pins, this assigns the scanner pins copied into standards workflows to propagate-sha-bump.sh, but that script only handles reusable_workflow_sha_bump_needs_propagation findings and dispatches updates to consumers whose uses: reference contains an old reusable-workflow SHA; it never edits standards' internal panic-ref, pons-ref, or scanner revision values. Following this authority statement therefore leaves those copies stale relative to bots/*/canon/pin.toml; name or add the mechanism that actually synchronizes the scanner pins.
Useful? React with 👍 / 👎.
| === 8.5 Open | ||
|
|
||
| None for phases 0 to 4. The bridge mode of 8.3 D4 is open to review. |
There was a problem hiding this comment.
Keep the unresolved phase 2 and 3 choices open
The claim that phases 0–4 have no open questions contradicts two unresolved choices earlier in this document: §5 still says to decide how counts_excluded is preserved before the direct row is removed, and §4 says phase 3 must choose between native adapter SARIF and a conversion step. Treating these as closed can let phases 2 or 3 proceed without preserving their existing output contracts, so list them here or settle them explicitly.
Useful? React with 👍 / 👎.



What this is
Design only:
docs/migrations/scanner-cutover-ponsbot-panicbot.adoc. No workflow, enrolment or code change.Recorded
panicbot ponsbot hypatia.bridgemode and estate-rescan and bridge-gate move behind it in phase 5. The owner's answer did not name the bridge mode, so this reading is mine: please confirm in review.bots/*/canon/pin.tomlis the pin authority;propagate-sha-bump.showns standards reusable pins; the cutover thread owns the two scanner lanes; one auto-merge actuator.D5 and D6 were already settled in the doc; nothing changed there.
Not done
Phase 1 itself (standards enrolment) is a separate PR.
Generated by Claude Code
Summary by CodeRabbit