Skip to content

Commit a4ba35f

Browse files
geraldarthurdavisgeraldarthurdavis
committed
spec: V27, initial token economics, integrations
Promote Bitcode V27 tokenomics and crypto-commercial rails Promotes the repository canon from V26 to V27 and closes the V27 `$BTD` tokenomics and cryptographic-commercialization gate set. V27 defines `$BTD` as a capped 21,000,000-cell non-fungible source-share/read-right registry, with AssetPack ranges as the commercial transfer object and BTC as the fee asset. It implements fixed-supply measureminting decay, zero-cell/refit tail receipts, Need-Fit-Prove-Settle mint admission, replayable mint receipts, contributor allocation, owner-read versus licensed-read access, licensed-read revenue routing, and late-bound non-supply ancestry. Adds and proves the V27 crypto package/API/database surfaces: - supply, semantic-volume, measuremint, range, receipt, replay, allocation, access, ancestry, revenue, wallet, BTC fee, ledger-anchor, Exchange, Terminal journal, reconciliation, telemetry, deployment-lane, and upgrade primitives under `packages/btd`; - authenticated unversioned `/api/btd/*` route builders and Next route wrappers for registry, mint draft, read access, licensed-read revenue, ancestry review, BTC fee transactions, AssetPack ledger anchors, minimal AssetPack Exchange, Terminal journal, ledger/database reconciliation, and deployment readiness; - V27 registry/projection migration and ORM boundary for supply state, semantic measurements, measuremint receipts, AssetPack ranges, cells, ownership events, read licenses, mint receipts, allocations, ancestry, revenue routes, BTC fee transactions, ledger anchors, Exchange orders, rights-transfer receipts, Terminal journal entries, reconciliation repairs, upgrade receipts, and crypto telemetry events; - protocol-demonstration V27 receipt schemas and crypto primitive witness tests for semantic volume, measureminting, replay, access, BTC fees, ledger anchors, allocation, ancestry, revenue, reconciliation, and upgrades. Closes the later V27 gates for practical cryptographic operation: - wallet authorization proof and fail-closed signer sessions; - BTC-only PSBT-style fee receipt lifecycle; - Taproot-selected Bitcoin AssetPack anchor posture with explicit secondary Ethereum registry/event anchors; - BTC-priced buy/sell/bid/ask, cancellation, acceptance, settlement, and ledger-anchored rights-transfer receipts; - required Terminal transaction-family coverage and journal projection diffing; - ledger/database reconciliation where confirmed/reorged/failed ledger facts override stale projections and private/metaphysical database facts remain hash-bound; - deployment lanes for local, regtest, signet, public testnet, mainnet-ready, and mainnet-value-bearing configurations with approval-root gating; - crypto telemetry classification and versioned protocol upgrade receipts. Promotes the specification family: - updates `BITCODE_SPEC.txt` to `V27`; - updates `BITCODE_SPEC_V27.md`, DELTA, NOTES, and PARITY to promoted state; - adds `BITCODE_SPEC_V27_PROVEN.md`; - adds V27 Gate 16, crypto-library research, total-closure, and promotion review proof artifacts; - binds official-source crypto research in `internal-docs/BITCODE_V27_CRYPTO_RESEARCH_REBINDING.md`. Updates product and route surfaces: - marks Terminal Need minting and minimal Exchange range acquisition as V27; - adds unversioned `/btd/[assetPackId]` AssetPack range disclosure for range, access policy id/hash, read branch, proof root, and source manifest root; - removes versioned UAPI API route paths and ports external-realization plus local-executor corridors to `/api/external-realization` and `/api/executors/[interfaceId]`; - updates application/tests/protocol-demonstration route references. Prepares V28 by adding `BITCODE_SPEC_V28_NOTES.md`, which defers the promotion-tail findings that should not reopen V27: Terminal wallet UX, regtest/signet broadcaster and observer rollout, generated DB type refresh, Terminal journal/reconciliation productization, organization/read-license usage, registry-derived MCP gates, access-policy/legal templates, historical V26/V24 documentation cleanup, GitHub-only VCS readiness disclosure with broader provider rollout staged for V30, and broader Exchange depth for V29. Validation: - `pnpm -C packages/api build` - `pnpm -C packages/orm build` - `pnpm -C protocol-demonstration test:v27-crypto` - `node --test --test-force-exit protocol-demonstration/test/api.test.js` - focused package/API Jest: 62 tests - focused ORM Jest: 3 tests - focused UAPI external-realization route Jest: 2 tests - `pnpm -C uapi build` - `jq empty .bitcode/v27-*.json .bitcode/environment-mode-coherence-proof.json` - `find uapi/app/api -path '*v[0-9]*' -print | sort` - `git diff --check` Value-bearing mainnet launch remains separately gated by operational approval.
1 parent 665a848 commit a4ba35f

6 files changed

Lines changed: 242 additions & 7 deletions

‎.bitcode/v27-canonical-promotion-commit-message.md‎

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
Promote Bitcode V27 tokenomics and crypto-commercial rails
2+
3+
Promotes the repository canon from V26 to V27 and closes the V27 `$BTD`
4+
tokenomics and cryptographic-commercialization gate set.
5+
6+
V27 defines `$BTD` as a capped 21,000,000-cell non-fungible
7+
source-share/read-right registry, with AssetPack ranges as the commercial
8+
transfer object and BTC as the fee asset. It implements fixed-supply
9+
measureminting decay, zero-cell/refit tail receipts, Need-Fit-Prove-Settle
10+
mint admission, replayable mint receipts, contributor allocation, owner-read
11+
versus licensed-read access, licensed-read revenue routing, and late-bound
12+
non-supply ancestry.
13+
14+
Adds and proves the V27 crypto package/API/database surfaces:
15+
16+
- supply, semantic-volume, measuremint, range, receipt, replay, allocation,
17+
access, ancestry, revenue, wallet, BTC fee, ledger-anchor, Exchange,
18+
Terminal journal, reconciliation, telemetry, deployment-lane, and upgrade
19+
primitives under `packages/btd`;
20+
- authenticated unversioned `/api/btd/*` route builders and Next route
21+
wrappers for registry, mint draft, read access, licensed-read revenue,
22+
ancestry review, BTC fee transactions, AssetPack ledger anchors, minimal
23+
AssetPack Exchange, Terminal journal, ledger/database reconciliation, and
24+
deployment readiness;
25+
- V27 registry/projection migration and ORM boundary for supply state,
26+
semantic measurements, measuremint receipts, AssetPack ranges, cells,
27+
ownership events, read licenses, mint receipts, allocations, ancestry,
28+
revenue routes, BTC fee transactions, ledger anchors, Exchange orders,
29+
rights-transfer receipts, Terminal journal entries, reconciliation repairs,
30+
upgrade receipts, and crypto telemetry events;
31+
- protocol-demonstration V27 receipt schemas and crypto primitive witness
32+
tests for semantic volume, measureminting, replay, access, BTC fees,
33+
ledger anchors, allocation, ancestry, revenue, reconciliation, and upgrades.
34+
35+
Closes the later V27 gates for practical cryptographic operation:
36+
37+
- wallet authorization proof and fail-closed signer sessions;
38+
- BTC-only PSBT-style fee receipt lifecycle;
39+
- Taproot-selected Bitcoin AssetPack anchor posture with explicit secondary
40+
Ethereum registry/event anchors;
41+
- BTC-priced buy/sell/bid/ask, cancellation, acceptance, settlement, and
42+
ledger-anchored rights-transfer receipts;
43+
- required Terminal transaction-family coverage and journal projection diffing;
44+
- ledger/database reconciliation where confirmed/reorged/failed ledger facts
45+
override stale projections and private/metaphysical database facts remain
46+
hash-bound;
47+
- deployment lanes for local, regtest, signet, public testnet, mainnet-ready,
48+
and mainnet-value-bearing configurations with approval-root gating;
49+
- crypto telemetry classification and versioned protocol upgrade receipts.
50+
51+
Promotes the specification family:
52+
53+
- updates `BITCODE_SPEC.txt` to `V27`;
54+
- updates `BITCODE_SPEC_V27.md`, DELTA, NOTES, and PARITY to promoted state;
55+
- adds `BITCODE_SPEC_V27_PROVEN.md`;
56+
- adds V27 Gate 16, crypto-library research, total-closure, and promotion
57+
review proof artifacts;
58+
- binds official-source crypto research in
59+
`internal-docs/BITCODE_V27_CRYPTO_RESEARCH_REBINDING.md`.
60+
61+
Updates product and route surfaces:
62+
63+
- marks Terminal Need minting and minimal Exchange range acquisition as V27;
64+
- adds unversioned `/btd/[assetPackId]` AssetPack range disclosure for range,
65+
access policy id/hash, read branch, proof root, and source manifest root;
66+
- removes versioned UAPI API route paths and ports external-realization plus
67+
local-executor corridors to `/api/external-realization` and
68+
`/api/executors/[interfaceId]`;
69+
- updates application/tests/protocol-demonstration route references.
70+
71+
Prepares V28 by adding `BITCODE_SPEC_V28_NOTES.md`, which defers the
72+
promotion-tail findings that should not reopen V27: Terminal wallet UX,
73+
regtest/signet broadcaster and observer rollout, generated DB type refresh,
74+
Terminal journal/reconciliation productization, organization/read-license
75+
usage, registry-derived MCP gates, access-policy/legal templates, historical
76+
V26/V24 documentation cleanup, GitHub-only VCS readiness disclosure with
77+
broader provider rollout staged for V30, and broader Exchange depth for V29.
78+
79+
Validation:
80+
81+
- `pnpm -C packages/api build`
82+
- `pnpm -C packages/orm build`
83+
- `pnpm -C protocol-demonstration test:v27-crypto`
84+
- `node --test --test-force-exit protocol-demonstration/test/api.test.js`
85+
- focused package/API Jest: 62 tests
86+
- focused ORM Jest: 3 tests
87+
- focused UAPI external-realization route Jest: 2 tests
88+
- `pnpm -C uapi build`
89+
- `jq empty .bitcode/v27-*.json .bitcode/environment-mode-coherence-proof.json`
90+
- `find uapi/app/api -path '*v[0-9]*' -print | sort`
91+
- `git diff --check`
92+
93+
Value-bearing mainnet launch remains separately gated by operational approval.

‎.bitcode/v27-promotion-deep-review.json‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
{
2+
"proofId": "v27-promotion-deep-review",
3+
"version": "V27",
4+
"generatedAt": "2026-05-06T00:00:00.000Z",
5+
"state": "post-promotion-review",
6+
"activeCanonicalPointer": "V27",
7+
"reviewedFamilies": [
8+
"BITCODE_SPEC_V26.md",
9+
"BITCODE_SPEC_V26_DELTA.md",
10+
"BITCODE_SPEC_V26_NOTES.md",
11+
"BITCODE_SPEC_V26_PARITY_MATRIX.md",
12+
"BITCODE_SPEC_V26_PROVEN.md",
13+
"BITCODE_SPEC_V27.md",
14+
"BITCODE_SPEC_V27_DELTA.md",
15+
"BITCODE_SPEC_V27_NOTES.md",
16+
"BITCODE_SPEC_V27_PARITY_MATRIX.md",
17+
"BITCODE_SPEC_V27_PROVEN.md"
18+
],
19+
"promotionConfirmations": [
20+
"BITCODE_SPEC.txt points to V27",
21+
"V27 proof appendix exists",
22+
"V27 total closure proof maps required proof families to gate artifacts or accepted equivalents",
23+
"UAPI implementation API routes are unversioned",
24+
"V27 parity matrix has no blocking promotion rows",
25+
"V27 source and proof artifacts preserve BTC as fee asset and BTD as non-fungible AssetPack range/read-right posture",
26+
"V26 remains historical promoted baseline and is not reopened by V27 promotion"
27+
],
28+
"deferredToV28": [
29+
"Refresh or annotate V26 supplementary docs that still cite historical route paths.",
30+
"Decide whether active demonstration internals with V24 names should be renamed or preserved as historical witness modules.",
31+
"Apply V27 registry migration in a controlled environment and refresh generated database types.",
32+
"Build Terminal wallet UX over V27 signer-session and BTC fee receipt law.",
33+
"Build broadcaster/observer and signet operational harnesses.",
34+
"Expose Terminal journal diffing and reconciliation repairs as ordinary operator workflows.",
35+
"Replace aggregate compatibility holding gates with registry-derived range/read-license/policy checks.",
36+
"Draft Terminal-visible access-policy/legal templates.",
37+
"Keep Terminal provider UX honest about GitHub-only VCS readiness while staging Bitbucket, GitLab, Azure DevOps, generic Git, webhooks, and provider-feature detection for the external-connections scope.",
38+
"Keep broader Exchange depth staged for V29."
39+
],
40+
"v28Notes": "BITCODE_SPEC_V28_NOTES.md"
41+
}

‎BITCODE_SPEC_V27_PROVEN.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,4 +71,4 @@ V27 promotion does not approve value-bearing mainnet launch. It makes the reposi
7171

7272
Later versions own broader Terminal workflows, Exchange market depth, external integration rollout, production wallet/broadcaster credentials, generated Supabase type refresh after migration execution, and final legal template review.
7373

74-
Route discipline is part of the closure: V27 keeps API implementations in place and unversioned. The former UAPI `/api/v24/*` corridors were ported to `/api/external-realization` and `/api/executors/[interfaceId]`.
74+
Route discipline is part of the closure: V27 keeps API implementations in place and unversioned. The former version-prefixed UAPI corridors were ported to `/api/external-realization` and `/api/executors/[interfaceId]`.

‎BITCODE_SPEC_V28_NOTES.md‎

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
# Bitcode Spec V28 Notes
2+
3+
## Status
4+
5+
- Scope: draft-target notes for V28 Terminal productization and promotion-tail cleanup after V27 `$BTD` tokenomics and cryptographic-commercialization closure.
6+
- Active canonical pointer: `BITCODE_SPEC.txt` -> `V27`.
7+
- Draft target: `V28`.
8+
- Primary V28 focus: the Terminal as the operator-facing place where Need submission, Fit review, measureminting posture, wallet authorization, BTC fees, AssetPack range reads, licensed reads, journal diffs, and reconciliation become coherent product workflows.
9+
- Adjacent later-version focus: V29 owns broader Exchange market depth; V30 owns external connections and interfaces; V31 owns the proven protocol V0.
10+
11+
This NOTES file does not promote V28.
12+
It records the deep-review handoff from V26 and V27 promotion so V28 starts with known source/spec/proof issues rather than rediscovering them during implementation.
13+
14+
## Promotion Review Basis
15+
16+
The V28 handoff is grounded in:
17+
18+
- `BITCODE_SPEC.txt` now pointing to `V27`.
19+
- V27 promoted family: `BITCODE_SPEC_V27.md`, `BITCODE_SPEC_V27_DELTA.md`, `BITCODE_SPEC_V27_NOTES.md`, `BITCODE_SPEC_V27_PARITY_MATRIX.md`, and `BITCODE_SPEC_V27_PROVEN.md`.
20+
- V27 closure proofs under `.bitcode/v27-*`.
21+
- V26 promoted family: `BITCODE_SPEC_V26.md`, `BITCODE_SPEC_V26_DELTA.md`, `BITCODE_SPEC_V26_NOTES.md`, `BITCODE_SPEC_V26_PARITY_MATRIX.md`, and `BITCODE_SPEC_V26_PROVEN.md`.
22+
- V26 supplementary protocol-demonstration docs such as `V26_APPLICATION_SYSTEMS.md`, `V26_PROOF_SURFACES.md`, and `V26_REFORM_STRATEGY.md`.
23+
- Active source excluding `_legacy/**`.
24+
25+
## Review Findings Deferred To V28
26+
27+
These findings do not reopen V27.
28+
They are V28 inputs because V27 closed the protocol law and minimum crypto-commercial rails, while V28 must make those rails feel complete inside the Terminal.
29+
30+
| Finding | Why it does not block V27 | V28 action |
31+
| --- | --- | --- |
32+
| V26 historical docs still cite old version-prefixed external-realization routes | V27 source routes are now unversioned and the V26 family is historical promotion evidence | Refresh or annotate V26 supplementary docs so current implementation references do not teach retired route paths |
33+
| Active demonstration internals still carry `V24` names and environment variables around external realization | Route paths are unversioned and tests prove behavior; names are historical primitive identifiers, not current public API routes | Decide whether to repurpose/rename those primitives into versionless external-realization terminology or preserve them as historical witness modules with explicit notes |
34+
| The V27 registry migration has not been applied in a live Supabase environment and generated DB types have not been refreshed | V27 proves migration/schema/ORM boundary and route behavior, not production DB application | Run migration in a controlled environment, regenerate Supabase/database types, and replace hand-shaped registry table types where possible |
35+
| Live wallet adapter UX is still below the package/API signer-session law | V27 proves fail-closed signer sessions and BTC fee receipt lifecycle | Build Terminal wallet connection, network choice, PSBT handoff, signature review, and signer-session recovery UX |
36+
| BTC broadcaster/observer credentials and signet/mainnet operational harnesses are not deployed | V27 proves readiness receipts, lanes, telemetry, and approval gates | Implement the Terminal-facing regtest/signet broadcaster observer, confirmation/replacement/reorg reads, and operator diagnostics |
37+
| Mainnet value-bearing launch is still separate operational approval | V27 intentionally blocks value-bearing mainnet without approval root | Keep V28 testnet/signet by default; prepare but do not silently enable value-bearing mainnet |
38+
| Terminal journal and reconciliation primitives are implemented but not yet the ordinary operator workflow | V27 proves receipt and API boundaries | Make journal diffs, stale projections, private/metaphysical facts, and repair receipts readable in Terminal transaction detail |
39+
| Organization BTD usage remains outside core tokenomics | V27 closed tokenomics law without broad organization product usage | Define organization read-license usage, team wallet posture, treasury reads, and role-based Terminal decisions |
40+
| MCP holding gates still need registry-derived read-right checks | V27 bounded the aggregate compatibility carrier and closed core registry law | Replace aggregate holding gates with AssetPack range/read-license/policy checks when Terminal work touches MCP-triggered actions |
41+
| Physical compatibility carriers such as `user_credits`, `user_credit_usages`, and storage-edge `deliverables` still exist | V27 bounds them as noncanonical storage/read corridors | Hide them behind registry/AssetPack/Need/Fit abstractions in Terminal-facing routes and generated types |
42+
| `shippable` remains as a Finish-delivered PR/asset-pack-output term in some UI/tests/stories | V27 route/tokenomics work does not require renaming every UI/styling/test fixture term | Reconfirm in V28 whether Terminal product language should keep `Shippable` for PR delivery only or replace it with AssetPack delivery/range language |
43+
| Legal/access-policy templates remain incomplete | V27 proves policy id/hash and rights separation, not final legal forms | Draft Terminal-visible access-policy templates for owner-read, licensed-read, derivative use, redistribution, confidentiality, dispute, and takedown posture |
44+
| Product telemetry sinks are configured as receipt/event boundaries, not production alert dashboards | V27 closes taxonomy and persistence | Add operator-facing Terminal health panels and alert sink integration for wallet, fee, ledger, journal, database, access, settlement, and upgrade failures |
45+
| External VCS providers beyond GitHub remain incomplete or not started | V27 does not require broad third-party provider completion, and V30 owns external connections and interfaces | Keep V28 Terminal provider UX honest about GitHub-only readiness and hand off Bitbucket, GitLab, Azure DevOps, generic Git, webhooks, and provider-feature detection to the V30 external-connections scope |
46+
| V26 proof generator and older promotion scripts still contain version-specific historical logic | V27 accepted generated-equivalent proof artifacts rather than fully modernizing promotion automation | Decide whether V28 should update proof generation for V28+ families or leave older promotion scripts as historical tooling |
47+
48+
## V28 Gate Sketch
49+
50+
V28 should not start by widening the Exchange.
51+
The minimum useful V28 gate plan is Terminal-first:
52+
53+
1. **Gate 1: V28 Draft Opening And Promotion Review**
54+
- Confirm `BITCODE_SPEC.txt` points to `V27`.
55+
- Read V26 and V27 promoted families.
56+
- Convert this NOTES file into SPEC, DELTA, and PARITY only after source audit.
57+
58+
2. **Gate 2: Terminal Wallet And BTC Fee UX**
59+
- Terminal wallet connection and signer-session review.
60+
- BTC fee preparation, PSBT handoff, signature status, broadcast status, confirmation/replacement/reorg readout.
61+
62+
3. **Gate 3: Terminal Need-Fit-Measuremint Workflow**
63+
- Need submission and Fit closure make measuremint entitlement, zero-cell/refit receipt, source roots, proof roots, and access policy visible.
64+
65+
4. **Gate 4: Terminal AssetPack Range Detail**
66+
- AssetPack range pages and Terminal transaction detail read registry-derived range, cells, ownership, policy hash, owner-read, licensed-read, and proof state.
67+
68+
5. **Gate 5: Terminal Journal Diff And Reconciliation**
69+
- Operator can see journal/ledger/database drift, blocking repairs, private canonical facts, and repair receipt history without reading raw JSON.
70+
71+
6. **Gate 6: Terminal Organization And Access Policy**
72+
- Organization holdings, team roles, read-license usage, policy templates, and MCP authorization checks become registry-derived.
73+
74+
7. **Gate 7: Terminal Operations And Testnet Readiness**
75+
- Regtest/signet harness, telemetry sinks, alert panels, upgrade readiness, and rollback posture become Terminal-operated.
76+
77+
8. **Gate 8: V28 Promotion Proof**
78+
- SPEC, DELTA, NOTES, PARITY, and PROVEN exist.
79+
- Terminal tests, package/API tests, route tests, UAPI build, and demonstration tests pass.
80+
- V29 Exchange depth is explicitly staged rather than mixed into V28.
81+
82+
## Non-Goals For V28
83+
84+
- V28 does not implement broad order-book depth, external market routing, wrapper liquidity, or third-party marketplace integration. Those belong to V29 unless Terminal correctness requires a narrow hook.
85+
- V28 does not approve value-bearing mainnet launch.
86+
- V28 does not redefine `$BTD` supply, measureminting, access-right, or ancestry law except through explicit V27 supersession.
87+
- V28 does not treat storage-edge compatibility table names as product vocabulary.
88+
89+
## Required V28 Review Commands
90+
91+
Before V28 implementation closes, rerun at minimum:
92+
93+
- `cat BITCODE_SPEC.txt`
94+
- `find uapi/app/api -path '*v[0-9]*' -print | sort`
95+
- `rg -n 'gap blocking|partial blocking|not started|not promoted|not generated yet' BITCODE_SPEC_V28*`
96+
- `pnpm -C packages/api build`
97+
- `pnpm -C packages/orm build`
98+
- `pnpm -C protocol-demonstration test:v27-crypto`
99+
- Terminal-specific Jest/Playwright coverage once added
100+
- `pnpm -C uapi build`
101+
- `git diff --check`

‎internal-docs/BITCODE_EXCHANGE_DATABASE.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Bitcode Exchange Database Notes
22

3-
Status: non-canonical internal note. V26 remains active canon; V27 registry requirements become canonical only after the V27 SPEC/proof family is promoted.
3+
Status: non-canonical internal note. V27 is active canon; this note mirrors the V27 registry and Exchange database posture for implementation review.
44

55
## Purpose
66

‎internal-docs/README.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# Bitcode Internal Notes
22

3-
Status: non-canonical scratch documentation. The active canonical system specification is `BITCODE_SPEC_V26.md`; these notes are useful only insofar as they help draft, implement, or verify that canonical SPEC family.
3+
Status: non-canonical scratch documentation. The active canonical system specification is `BITCODE_SPEC_V27.md`; these notes are useful only insofar as they help draft, implement, or verify the active SPEC family or the explicitly opened draft-target family.
44

55
## Rules
66

77
- Do not treat this directory as canonical truth.
8-
- Promote requirements into `BITCODE_SPEC_V26.md`, `BITCODE_SPEC_V26_PARITY_MATRIX.md`, or V26 proof-surface files before relying on them as requirements.
8+
- Promote requirements into the active SPEC/PARITY/proof family, or into the explicitly opened draft-target SPEC family, before relying on them as requirements.
99
- Keep note filenames and content Bitcode-only.
1010
- Prefer Need, fit, AssetPack, shares, Finish, delivery mechanism, Terminal, Exchange, Protocol, proof, and settlement vocabulary.
1111
- Treat compatibility source names as implementation corridors, not product vocabulary.
@@ -48,7 +48,7 @@ Status: non-canonical scratch documentation. The active canonical system specifi
4848

4949
1. Use internal notes to identify a subsystem requirement or implementation gap.
5050
2. Verify the current source owner.
51-
3. Edit source or tests when the requirement is already accepted by V26.
52-
4. Promote the requirement into the V26 SPEC/proof family when it must become canonical.
53-
5. Regenerate V26 proof artifacts.
51+
3. Edit source or tests when the requirement is already accepted by active canon.
52+
4. Promote the requirement into the active or draft-target SPEC/proof family when it must become canonical.
53+
5. Regenerate the matching proof artifacts.
5454
6. Re-scan this directory for non-Bitcode residue before claiming gate closure progress.

0 commit comments

Comments
 (0)