V47 Gate 10: Open V48 notes posture#247
Conversation
Add the V48 notes-only draft opening after promoted V47, mirroring the V46 promotion precedent: refresh the roadmap posture (V47 active canon, V48 notes-only draft target, V48 interactive local experiential QA named as the next queued work), align the canonical-input artifact inventory (add the missing V47 branch to buildRequiredCanonicalArtifacts so the active V47 canon reports its 11 required generated artifacts), and add the V47 expectation to the protocol-demonstration canonical-input count map. The V48 notes record the QA-first opening charter: staging Supabase preparation, wallet-fauceted testnet BTC, local telemetry expectations, step-by-step debugging, and hands-on validation of identity/authentication, depositing, reading, and ledgerized journaling. Refresh the V47 gate and readiness artifacts against the advanced roadmap posture. Validated with: - pnpm --filter @bitcode/protocol test (237 pass) - npm --prefix protocol-demonstration test (191 pass) - npm --prefix protocol-demonstration run test:v28-mvp-qa - node scripts/run-bitcode-spec-quality.mjs --mode strict-version --version V48 - node scripts/run-bitcode-spec-quality.mjs --mode basic - node scripts/check-bitcode-canonical-inputs.mjs --current-target V47 (artifacts=11) - node scripts/check-v47-gate10-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-tests - node scripts/check-import-casing.mjs - git diff --check Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
https://github.com/engineeredsoftware/ENGI/blob/499d3366f91fe509513755053c1ad87a14e8319b/packages/protocol/src/canonical/v21-specifying.js#L557-L565
Require the V47 drift report as canonical input
When V47 is current canon, this V47 artifact list is the source used by check-bitcode-canonical-inputs; it omits .bitcode/v47-canon-posture-drift-report.json even though the V47 spec/proven files and the promotion report list that drift report as generated proof output. I checked node scripts/check-bitcode-canonical-inputs.mjs --current-target V47, and it now passes with artifacts=11, so deleting or staling the V47 canon-posture drift evidence would not fail the canonical-input gate after this promotion.
ℹ️ 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".
Summary
Final post-promotion posture repair surfaced by #243's validation, mirroring the V46 precedent commit "V46 promotion: open V47 notes posture". Two real failures remained in the protocol-demonstration battery under the promoted pointer:
real canonical input set for active V47 canon passes input checking—buildRequiredCanonicalArtifactshad no V47 branch, so the active-canon inventory reportedartifacts=0. Added the branch (11 artifacts: 8 gate artifacts + readiness + the 2 base reports) and theV47: 11expectation in the demonstration count map.strict draft-target spec-quality passes for the current draft family— post-promotion, the draft target derives as V48 and strict spec-quality requires a notes-only opening. AddedBITCODE_SPEC_V48_NOTES.md(notes-only draft rule, deferred-from-V47 reading, candidate workstreams encoding the V48 charter: staging Supabase prep, wallet-fauceted testnet BTC, telemetry expectations, step-by-step debugging, and hands-on QA of identity/auth → depositing → reading → ledgerized journaling) and refreshed the roadmap posture (V47 active canon row, V48 notes-only draft row, Source Families update).The other "failures" in that CI log were expected stderr from intentional negative-fixture tests.
Validation
pnpm --filter @bitcode/protocol test(237 pass)npm --prefix protocol-demonstration test(191 pass) +test:v28-mvp-qarun-bitcode-spec-quality --mode strict-version --version V48and--mode basiccheck-bitcode-canonical-inputs --current-target V47→artifacts=11check:v47-gate10 --promotion-mode, import casing,git diff --checkall cleanMerging this updates
version/v47and re-triggers #243's validation, which should now settle fully green for the merge tomain.🤖 Generated with Claude Code