V47 Gate 3: Seller And Buyer State Machine Law

[geraldarthurdavis]

Summary

• adds the source-safe V47 seller/buyer state-machine law artifact and package exports
• binds IP seller and IP buyer launch states to Deposit, Read, Packs, BTD receipts, settlement, source-to-shares, and semantic volume sources
• wires Gate 3 generation/check scripts into package scripts and gate/canon workflows

Validation

• node scripts/check-v47-gate3-seller-buyer-state-machine-law.mjs --skip-branch-check
• node scripts/check-v47-gate2-feature-excess-alignment-audit.mjs --skip-branch-check --skip-uapi-tests
• node scripts/check-v47-gate1-scope-measurement-launch-freeze.mjs --skip-branch-check
• node scripts/check-bitcode-spec-family.mjs --version V47 --mode draft --current-target V46
• node scripts/check-bitcode-canonical-inputs.mjs --current-target V46
• node scripts/check-bitcode-canon-posture-drift.mjs --active-canon V46 --draft-target V47
• node scripts/run-bitcode-spec-quality.mjs --mode basic
• pnpm --filter @bitcode/protocol test
• pnpm --dir uapi exec jest --runTestsByPath tests/depositRouteModel.test.ts tests/readRouteModel.test.ts tests/packsPageClient.test.tsx --runInBand
• pnpm --dir uapi exec tsc --noEmit
• pnpm --dir uapi lint
• pnpm --dir uapi build
• git diff --check
• changed-file secret-pattern scan

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
engi-uapi	Ready	Preview, Comment	Jun 5, 2026 5:03pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cc252a6458

ℹ️ 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".

[chatgpt-codex-connector]

Derive state-machine binding coverage from rows

When the gate/canon workflows invoke this checker with --skip-package-tests, these hard-coded coverage values become the checker's only assertion that the seller and buyer state machines are still bound. If a future edit removes or retargets the seller-state-machine or buyer-state-machine rows, buildV47SellerBuyerStateMachineLaw() will still report both bindings as true and check:v47-gate3 can pass with an artifact that attests to bindings it no longer contains. Please compute these flags from stateRows instead of literals.

Useful? React with 👍 / 👎.