|
| 1 | +# Bitcode Spec V44 Delta |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V44` |
| 6 | +- V44 state: draft opened for scaled engineering economy and tokenized AssetPack network work over promoted V43 |
| 7 | +- Current canonical/latest target: `V43` |
| 8 | +- Prior canonical anchor: `BITCODE_SPEC_V43.md` |
| 9 | +- Prior generated proof appendix: `BITCODE_SPEC_V43_PROVEN.md` |
| 10 | +- Generated structured artifact inventory: no V44 generated artifacts are canonical at Gate 1; later gates must create source-safe `.bitcode/v44-*` artifacts |
| 11 | +- Source parity state: Gate 1 aligns specification, roadmap, docs, workflow, package script, and checker posture only |
| 12 | +- Notes companion: `BITCODE_SPEC_V44_NOTES.md` |
| 13 | +- Delta companion: `BITCODE_SPEC_V44_DELTA.md` |
| 14 | +- Parity companion: `BITCODE_SPEC_V44_PARITY_MATRIX.md` |
| 15 | +- Scope: delta from V43 product-route/agentic-depositing canon to V44 scaled engineering economy operation |
| 16 | +- Last fully realized canonical target preserved in source: `V43` |
| 17 | + |
| 18 | +## Why V44 exists |
| 19 | + |
| 20 | +V43 made the product routes intelligible: AssetPacks in through `/deposit`, |
| 21 | +AssetPacks out through `/read`, and PackActivity inspection through `/packs`. |
| 22 | +V44 exists because an enterprise-grade Bitcode network must operate at scale: |
| 23 | +many departments, budgets, repositories, deposit options, Reads, Fits, quotes, |
| 24 | +settlements, contributors, compensation statements, and repair states. |
| 25 | + |
| 26 | +## Accepted V44 decisions |
| 27 | + |
| 28 | +- Treat scaled economic operation as the next draft target over V43. |
| 29 | +- Keep V43 route law: `/packs`, `/read`, and `/deposit` remain the default |
| 30 | + product surfaces. |
| 31 | +- Name every economic field as estimate, quote, observed payment, final |
| 32 | + settlement, contributor allocation, delivery, or repair state. |
| 33 | +- Keep source-safety stronger than UX convenience. |
| 34 | +- Keep value-bearing mainnet blocked until a later explicit launch version. |
| 35 | + |
| 36 | +## V44 gate plan |
| 37 | + |
| 38 | +1. Gate 1 Scaled Engineering Economy Roadmap Opening. |
| 39 | +2. Gate 2 Economic Domain Model And Receipt Taxonomy. |
| 40 | +3. Gate 3 Packs Portfolio Search And Market Intelligence. |
| 41 | +4. Gate 4 Reading Budget, Quote Policy, And Procurement Governance. |
| 42 | +5. Gate 5 Depositor Earnings, ROI, And Supply Opportunity Intelligence. |
| 43 | +6. Gate 6 BTD/BTC Accounting And Contributor Compensation Statements. |
| 44 | +7. Gate 7 Organization Policy, Approval, And Wallet Authority. |
| 45 | +8. Gate 8 Enterprise Product UX For Economic Operation. |
| 46 | +9. Gate 9 Scaled Local/Staging Network Rehearsal. |
| 47 | +10. Gate 10 Promotion Readiness. |
| 48 | + |
| 49 | +## Explicitly deferred |
| 50 | + |
| 51 | +V44 Gate 1 defers implementation of portfolio dashboards, economic statement |
| 52 | +APIs, budget policy engines, compensation statement materialization, governance |
| 53 | +runtime enforcement, scaled rehearsal scripts, and V44 promotion workflow until |
| 54 | +their owning gates. |
| 55 | + |
| 56 | +## Pre-Implementation Sequence |
| 57 | + |
| 58 | +1. Open V44 spec family, roadmap, checker, package script, workflow posture, |
| 59 | + and documentation. |
| 60 | +2. Implement economic domain model and receipt taxonomy for source-safe |
| 61 | + portfolio, quote, statement, governance, and repair objects. |
| 62 | +3. Extend `/packs` into portfolio analytics, search, and market intelligence. |
| 63 | +4. Add Reading budget policy, quote policy, and procurement governance. |
| 64 | +5. Add deposit revenue, demand, ROI, and supply opportunity readback. |
| 65 | +6. Add BTD/BTC/source-to-shares compensation statements and reconciliation. |
| 66 | +7. Add organization policy, approval, spend authority, and wallet authority. |
| 67 | +8. Rehearse scaled many-pack local/staging-testnet economic operation. |
| 68 | +9. Polish enterprise economy UX and operator dashboards. |
| 69 | +10. Close V44 promotion readiness and prepare active V44 / draft V45 posture. |
| 70 | + |
| 71 | +## Validation direction |
| 72 | + |
| 73 | +Gate 1 validates with `pnpm run check:v44-gate1`, |
| 74 | +`node scripts/check-bitcode-spec-family.mjs --version V44 --mode draft --current-target V43`, |
| 75 | +`node scripts/check-bitcode-canon-posture-drift.mjs --active-canon V43 --draft-target V44`, |
| 76 | +and `git diff --check`. |
| 77 | + |
| 78 | +## Commit-Body Direction |
| 79 | + |
| 80 | +V44 commit bodies should name the closed gate, generated artifacts or proof |
| 81 | +surfaces touched, source-safety posture, validation commands, accepted |
| 82 | +boundaries, and any deferred economic implementation work. They should not use |
| 83 | +temporary `wip` wording for closed gate work. |
0 commit comments