Repository navigation
F9: complete canonical acceptance - #18
Merged
Merged
Conversation
Complete F9 canonical acceptance from a fresh deterministic environment. Add reusable deployment/bootstrap orchestration, bootstrap fidelity coverage, and the uninterrupted Bootstrap -> A1 -> A2 -> A3 rejection -> A4 acceptance flow. Verify authoritative state transitions, exact Beneficiary delivery, rejection atomicity, zero protocol custody, and deterministic reproduction. Refactor the Hook deployment procedure for script/test reuse without changing Standby protocol semantics, and record the Session 16 implementation and retrospective evidence. G9 independently reviewed: PASS / CLOSED.
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.
Summary
Completes F9 — Canonical Acceptance.
Proves that the completed Standby realization can be constructed from a fresh deterministic environment and reproduce the frozen canonical economic history through real deployment, bootstrap, admission, ordinary-swap, rejection, and exercise paths without privileged economic fixture state.
Canonical Acceptance
The acceptance suite reproduces one uninterrupted history over the same live pool and A1-created commitment:
A3 verifies the specific insufficient-prospective-backing rejection and post-revert atomicity.
A4 verifies actual input settlement, exact 50,000 MockUSDC Beneficiary delivery, causal Remaining reduction to zero, O reduction to zero, and zero protected-output custody by StandbyHook and ExerciseRouter.
Fresh Construction
Adds reusable production-path deployment/bootstrap orchestration used directly by the acceptance tests:
HelperConfig
→ PoolManager
→ DeployDemoEnvironment
→ BootstrapStandby
→ A1
→ A2
→ A3
→ A4
The acceptance fixture uses no backed fixture inheritance, harness economic seeding, direct storage mutation, test-only economic setters, pre-created commitments, or mocked fulfillment.
Deployment Orchestration
Refactors the existing Hook deployment procedure into an inheritable deployment component so composed scripts can reuse the canonical procedure without deploying the oversized deployment helper on-chain.
The refactor preserves Hook mining, CREATE2 deployment, validation, and constructor semantics.
No Standby production protocol semantics changed.
Determinism
A second independently constructed environment reproduces the same canonical history, commitment identity, delivery quantity, and exercise input.
The operational deployment and bootstrap wrappers were also successfully exercised against local Anvil as supplementary path-fidelity evidence.
Verification
forge fmt --check— cleanforge build— successfulGas and coverage were not rerun because no production source changed.
Gate
F9 — Canonical Acceptance: COMPLETE
G9 — PASS / CLOSED following independent review.
No prior gate requires reopening.
Next
F10 — Demo / Submission Readiness is the next authorized implementation slice.
F9T — Public Testnet Deployment remains optional and off the critical path.