Repository navigation
feat: bind acceptance v11 to sealed v10 accounting - #255
Merged
DavidHLP merged 16 commits intoOct 11, 2026
Merged
Conversation
DavidHLP
marked this pull request as ready for review
October 10, 2026 09:21
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e5b6011bbb
ℹ️ 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".
Codex Review SummaryThis 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. |
fix: preserve safe network diagnostics through budget recovery
fix(agent): propagate reviewed U02 repairs into the V12 stack
fix(agent): integrate V12 binding and reviewed U02 safeguards
…vations fix: enforce required prior evidence observations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Propagated U02 stack (current head 1f6af8b). This PR now carries the reviewed safeguards from its descendants: direct submission clarification with independent authorized actions, trusted evidence projection and disjoint judging behavior, shared refusal/corpus/source bindings, coherent judge receipts, strict prior-five observations, and immutable retained V7–V12 accounting. The complete stack has 23 Agent/documentation files; no Java, dependency or U03 database slice is introduced.
Both independent combined-stack reviews APPROVE source 0b511a3. Fetched current-head tree comparison exits0 against that source; exact-source CI38110221731 completed SUCCESS including Agent and ci-ok, and359 related remote tests passed. This is reused identical-tree validation, not a new CI run on this merge head. Current-head check contexts and workflow runs were inspected; no applicable pending/failed gate is bypassed.
Engineering merge does not establish formal U02/U03/U04 acceptance or authorize period creation/activation, reset, unknown-liability release or paid retries. V12 remains permanently halted; main PR231 remains Draft.
Preserved historical PR evidence:
Prepare an independent immutable acceptance package for the corrected judging candidate while retaining the permanently halted V10 period and all older liabilities. V10's actual 84 calls, 21,564 microUSD usage and 806,400 microUSD commitment are pinned through its identity, SQLite ledger, binding and guard. Recursive history validation requires halted, settled accounting and matching receipts.
The retained baseline is 899 attempts, 238,504 microUSD known actual usage, 7,836,914 microUSD commitment, and two unresolved liabilities encumbering 1,572,864 microUSD. The new 241-attempt plan preserves purposes and caps; its conservative combined peak is 12,295,200 microUSD within the user's cumulative USD200 authorization. No old period is refilled, unknown usage released, or automatic paid retry started.
Validation on e5b6011: test-first revision f6326d8 failed eight new V11 cases; the five focused suites passed 224 tests in 31.74s. Both review axes approve. All 33 historical source fingerprints were verified against the actual private files. The candidate is frozen with the unread V3 commitment, and fresh A/B authenticated read-only and provider-model availability preflights passed. CI 38040382616 completed successfully on this exact head. The canonical package was activated once after these checks; a full actual zero-call snapshot was preserved before evaluation. The first registered source-analysis stage completed with one settled call costing 242 microUSD. Subsequent evaluation remains in progress; formal U02/U03/U04 acceptance is not claimed.
Refs DAV-58. Stacked on #254.