Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions .bitcode/v46-local-interface-comprehension-rehearsal.json
Original file line number Diff line number Diff line change
Expand Up @@ -799,18 +799,18 @@
"delta": "BITCODE_SPEC_V46_DELTA.md:a16a16db40d4eeae612a0657",
"notes": "BITCODE_SPEC_V46_NOTES.md:cca70aca3566132e7026351c",
"parity": "BITCODE_SPEC_V46_PARITY_MATRIX.md:91b47eeaa106639d2d21856b",
"roadmap": "SPECIFICATIONS_ROADMAP.md:90a3988a2651878e43f96c65",
"roadmap": "SPECIFICATIONS_ROADMAP.md:9a349af9258300768b8fc758",
"readme": "README.md:d28ec731634e03953d8adfe6",
"protocolReadme": "packages/protocol/README.md:f5b175049f4f4e8df179e184",
"packageJson": "package.json:b79014968c556bc1b43ab341",
"packageJson": "package.json:9985108aaea23b4bb4f5e7a9",
"packageIndex": "packages/protocol/src/index.js:1f16ea428bd71351a1292cb6",
"packageTypes": "packages/protocol/src/index.d.ts:278dfc652c621533b5e86f4d",
"packageSource": "packages/protocol/src/canonical/v46-local-interface-comprehension-rehearsal.js:553cbdb03542959151ef8fce",
"packageSource": "packages/protocol/src/canonical/v46-local-interface-comprehension-rehearsal.js:ea56065835a819cd454c5558",
"packageTest": "packages/protocol/test/v46-local-interface-comprehension-rehearsal.test.js:5b6ad282088791ea76ec2bbf",
"generator": "scripts/generate-v46-local-interface-comprehension-rehearsal.mjs:d6a9dadb6f8ee51de50a529f",
"checker": "scripts/check-v46-gate7-local-interface-comprehension-rehearsal.mjs:beb49c72404e73e730640a72",
"gateWorkflow": ".github/workflows/bitcode-gate-quality.yml:e5de1dddfaeeb0ee525b0c0f",
"canonWorkflow": ".github/workflows/bitcode-canon-quality.yml:43cc4ded2bd9757dda9091dc",
"gateWorkflow": ".github/workflows/bitcode-gate-quality.yml:7cb34abd82e64e1fb32946b0",
"canonWorkflow": ".github/workflows/bitcode-canon-quality.yml:7e675adc942626fc2048a266",
"v46ProtocolArtifact": ".bitcode/v46-protocol-comprehension-object-model.json:b09508f0d7841284effb0e01",
"v46PublicArtifact": ".bitcode/v46-public-operator-claim-boundaries.json:352e9021ffbe43d650923b98",
"v46ProductArtifact": ".bitcode/v46-product-route-comprehension-readback.json:c5d1d887915cb920288b18a8",
Expand Down
6 changes: 6 additions & 0 deletions .github/workflows/bitcode-canon-quality.yml
Original file line number Diff line number Diff line change
Expand Up @@ -449,6 +449,12 @@ jobs:
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/check-v46-gate8-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-tests
if [ -f BITCODE_SPEC_V47.md ]; then
node scripts/check-bitcode-spec-family.mjs --version V47 --mode draft --current-target V46
if [ -f scripts/check-v47-gate1-scope-measurement-launch-freeze.mjs ]; then
node scripts/check-v47-gate1-scope-measurement-launch-freeze.mjs --skip-branch-check
fi
fi
else
echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2
exit 1
Expand Down
6 changes: 6 additions & 0 deletions .github/workflows/bitcode-gate-quality.yml
Original file line number Diff line number Diff line change
Expand Up @@ -578,6 +578,12 @@ jobs:
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/check-v46-gate8-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-tests
if [ -f BITCODE_SPEC_V47.md ]; then
node scripts/check-bitcode-spec-family.mjs --version V47 --mode draft --current-target V46
if [ -f scripts/check-v47-gate1-scope-measurement-launch-freeze.mjs ]; then
node scripts/check-v47-gate1-scope-measurement-launch-freeze.mjs --skip-branch-check
fi
fi
else
echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2
exit 1
Expand Down
778 changes: 778 additions & 0 deletions BITCODE_SPEC_V47.md

Large diffs are not rendered by default.

137 changes: 137 additions & 0 deletions BITCODE_SPEC_V47_DELTA.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,137 @@
# Bitcode Spec V47 Delta

## Status

- Version: `V47`
- V47 state: draft opening; V46 remains active canon while V47 scopes website commercial testnet launch readiness
- Current canonical/latest target: `V46`
- Prior canonical anchor: `BITCODE_SPEC_V46.md`
- Prior generated proof appendix: `BITCODE_SPEC_V46_PROVEN.md`
- Generated structured artifact inventory: planned draft `.bitcode/v47-spec-family-report.json`, `.bitcode/v47-canonical-input-report.json`, V47 launch-readiness artifacts, and `BITCODE_SPEC_V47_PROVEN.md` after promotion readiness
- Source parity state: V47 source parity is pending; Gate 1 is specification, roadmap, measurement-law, and workflow-hook opening only
- Notes companion: `BITCODE_SPEC_V47_NOTES.md`
- Spec companion: `BITCODE_SPEC_V47.md`
- Parity companion: `BITCODE_SPEC_V47_PARITY_MATRIX.md`
- Scope: V47 delta for commercial website testnet readiness over promoted V46 protocol comprehension canon
- Last fully realized canonical target preserved in source: `V46`

## Why V47 exists

V45 made Bitcode's knowledge commoditization law precise. V46 made that law
commercially legible. V47 exists to make the website application commercially
ready on staging-testnet: IP sellers can deposit AssetPacks, IP buyers can buy
Need-fitting AssetPacks, and `/packs` plus Auxillaries make the whole exchange
auditable, source-safe, and repairable.

V47 is not a broad feature expansion. It is the first generally available MVP
launch-readiness version and therefore must freeze scope, remove or defer
feature excess, specify measurement law, prove seller and buyer state machines,
and validate the website E2E.

## Accepted V47 decisions

- V47 focuses on the rich website application: `/deposit`, `/read`, `/packs`,
and Auxillaries.
- In V47, testnet means BTC amounts and payment observations are testnet only;
all other protocol behavior should be production-intended.
- Measurement is the basis of IP commoditization: individual measurements,
inference prompts, typed outputs, weights, normalized contributions, BTD
scalar formula, and source-safe visualization are launch-critical.
- V47 must support two profiles: IP sellers and IP buyers.
- Conversation experiences, ChatGPT App commercialization, MCP/API
commercialization, deeper BTD mining cryptography, mainnet launch authority,
and advanced market mechanics are deferred.
- A dedicated feature-excess gate must remove, hide, or flag anything that
distracts from the launch MVP.
- A dedicated E2E gate must prove selling and buying IP the Bitcode way.
- A dedicated public launch messaging gate must refurbish the landing page for
V47 commercial testnet readiness.

## Explicitly deferred

- Value-bearing mainnet settlement.
- Commercial launch of API/MCP, ChatGPT App, and Bitcode Chat.
- Deeper BTD mining cryptographic implementation beyond existing website
launch contracts.
- Advanced exchange/market mechanics beyond the MVP seller/buyer AssetPack
flows.
- Source-bearing preview before BTC-testnet settlement and BTD rights transfer.

## Pre-Implementation Sequence

1. Open the V47 draft spec family over active V46.
2. Specify testnet semantics, measurement law, launch freeze, user profiles,
and gate plan.
3. Audit feature excess and gate misalignment.
4. Specify seller/buyer state machines and measurement visualizations.
5. Implement and test depositor website completion.
6. Implement and test reader website completion.
7. Complete `/packs` and Auxillaries commercial dashboard state.
8. Prove E2E IP selling and buying tests.
9. Rehearse canonical staging-testnet deployment.
10. Promote V47 only after commercial website launch-readiness evidence is
complete.

## Commit-Body Direction

V47 commits should describe the commercial launch behavior, the measurement or
state-machine proof they close, the commands run, and any feature flags or
deferrals introduced. Commit bodies should name source-safety, measurement,
testnet semantics, proof/readback, and user-flow consequences when relevant.

## Gate 1: V47 Scope, Testnet Semantics, Measurement Law, And Launch Freeze

Gate 1 closes when the V47 spec family exists over active V46, V47 is framed as
commercial website testnet launch readiness, testnet means only BTC amounts are
testnet/free, measurement law is explicit, seller and buyer flows are named,
the ten-gate launch plan is recorded, package and workflow checks exist, and no
V47 file claims promoted authority.

## Gate 2: Feature Excess And Gate Alignment Audit

Gate 2 audits all website features and protocol surfaces for launch relevance.
It removes wrong features, feature-flags post-V47 behavior, and records
deferrals so the first generally available MVP is focused.

## Gate 3: Seller And Buyer State Machine Law

Gate 3 specifies exact IP seller and IP buyer state machines, including
measurement, proof, repair, settlement, delivery, and `/packs` history.

## Gate 4: Depositor Website Completion

Gate 4 completes source connection, deposit AssetPack option synthesis,
source-safe review, Depository admission, and compensation visibility.

## Gate 5: Reader Website Completion

Gate 5 completes Read Request, Need synthesis/review, Finding Fits, preview,
quote, BTC-testnet settlement, BTD rights transfer, and PR delivery.

## Gate 6: Packs And Auxillaries Commercial Dashboard

Gate 6 completes identity, teams, wallets, histories, PackActivity
master-detail, filters/search, proof readback, and repair surfaces.

## Gate 7: E2E IP Selling And Buying Tests

Gate 7 adds browser-level tests proving both sides of Bitcode: deposit IP into
Bitcode, buy synthesized IP from Bitcode, and verify ledger/database/storage,
proof, settlement, rights, compensation, and delivery.

## Gate 8: Landing Page And Public Launch Messaging

Gate 8 refurbishes landing and public docs for V47 commercial testnet
readiness, core flows, proof-backed trust, source-safe IP exchange, and the
meaning of testnet.

## Gate 9: Staging-Testnet Deployment Rehearsal

Gate 9 validates the canonical staging-testnet deployment with realistic data,
real routes, real storage/database/ledger projections, and BTC-testnet
settlement.

## Gate 10: V47 Promotion Readiness

Gate 10 closes parity matrix, generated proof artifacts, CI/promotion workflow,
commercial website readiness, and canonical promotion.
83 changes: 55 additions & 28 deletions BITCODE_SPEC_V47_NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,19 +7,44 @@
- Active canonical anchor: `BITCODE_SPEC_V46.md`
- Active generated proof appendix: `BITCODE_SPEC_V46_PROVEN.md`
- Current canonical/latest target: `V46`
- Prior canonical anchor: `BITCODE_SPEC_V45.md`
- Prior generated proof appendix: `BITCODE_SPEC_V45_PROVEN.md`
- V47 state: notes-only draft opening
- Scope: V47 starts as a specification-workshopping target over promoted V46 protocol comprehension canon.
- Prior canonical anchor: `BITCODE_SPEC_V46.md`
- Prior generated proof appendix: `BITCODE_SPEC_V46_PROVEN.md`
- V47 state: draft opening for commercial website testnet launch readiness; V46 remains active canon
- Generated structured artifact inventory: planned draft `.bitcode/v47-spec-family-report.json`, `.bitcode/v47-canonical-input-report.json`, V47 commercial website testnet artifacts, and `BITCODE_SPEC_V47_PROVEN.md` after promotion readiness
- Source parity state: V47 source parity is pending; Gate 1 opens launch scope, testnet semantics, measurement law, and closure gates over promoted V46
- Scope: V47 starts as the commercial website testnet launch-readiness target over promoted V46 protocol comprehension canon.

## Notes-only draft rule
## Notes companion rule

These notes make the V47 draft target visible to strict spec-quality checks after
V46 promotion. They are not first-gate implementation authority, not a full V47
specification family, and not permission to bypass the V46 canon. V47 work must
continue by refining specification atoms, creating an explicit parity matrix,
and then opening scoped gate branches only after the new specification intent is
clear.
These notes accompany the V47 draft specification family. They are not stronger
than `BITCODE_SPEC_V47.md`, the active `BITCODE_SPEC.txt` pointer, or generated
proof artifacts. They record concise launch intent, user-flow emphasis,
measurement clarity, and deferrals while V46 remains active canon.

## Concise current-system reading

V45 and V46 made Bitcode's law and explanation precise enough for a final
website commercial-readiness pass. V47 should make the rich website application
deployable and demonstrable on staging-testnet across `/deposit`, `/read`,
`/packs`, and Auxillaries.

IP sellers should be able to connect source, receive deposit AssetPack options,
review source-safe measurements, approve a deposit, and track future
compensation posture. IP buyers should be able to request a Read, review a
synthesized Need, request Finding Fits, review source-safe AssetPack
measurements and quote, settle on BTC testnet, receive BTD rights, and get
repository delivery.

Measurement is the commercial center. Individual measurements, the prompts that
command them, typed output schemas, weights, normalized contributions, and
weighted BTD scalar visualization must be understandable to sellers and buyers.

## Simplified-spec reading rule

V47 should simplify launch experience, not protocol law. If a feature, route,
copy block, state, or panel does not help a seller deposit IP, a buyer buy IP,
an operator prove state, or a user understand source-safe measurement, it should
be removed, hidden, feature-flagged, or deferred.

## Deferred from V46

Expand All @@ -30,30 +55,32 @@ ChatGPT App, Bitcode Chat, proof roots, repair states, Bitcoin/BTC settlement
language, BTD scalar-volume and rights language, GitHub delivery boundaries, compute
constraints, storage boundaries, and build/process validation.

V47 begins from the remaining question: which protocol atoms need further
precision before the next implementation parity pass. The opening posture is
intentionally small so V47 can be workshopped from the promoted canon rather
than inherited from stale notes.
V47 begins from the remaining question: what is still required for complete
commercial website testnet readiness. Its posture is intentionally focused:
website application first, commercial testnet semantics, exact measurement law,
feature excess audit, E2E seller/buyer proof, and promotion readiness.

## Candidate V47 workstreams

- Protocol atom audit: inspect the promoted V46 law in small pieces and classify
each atom as precise, vague, contradictory, missing, or implementation-ready.
- Parity matrix preparation: convert accepted V47 specification changes into a
source-to-proof matrix before implementation gates begin.
- Product claim discipline: keep public, operator, interface, and proof
language aligned with source-safe AssetPack, BTD, BTC, rights, settlement,
delivery, repair, and compensation law.
- Commercial readiness proofs: identify the tests, generated artifacts,
workflows, local rehearsals, and staging-testnet evidence needed for any V47
implementation gates.
- Scope, testnet semantics, measurement law, and launch freeze.
- Feature excess and gate alignment audit.
- Seller and buyer state machine law.
- Depositor website completion.
- Reader website completion.
- Packs and Auxillaries commercial dashboard.
- E2E IP selling and buying tests.
- Landing page and public launch messaging.
- Staging-testnet deployment rehearsal.
- V47 promotion readiness.

## Non-goals during V47 opening

- Do not implement V47 product behavior from this notes-only opening.
- Do not rewrite V46 promoted canon except through an explicit addendum.
- Do not implement product behavior until a scoped V47 gate authorizes it.
- Do not rewrite V46 promoted canon except through explicit V47 draft law and
accepted parity.
- Do not expose raw source, unpaid AssetPack source, secrets, wallet private
material, private settlement payloads, raw prompts, or raw provider responses.
- Do not collapse estimate, quote, observed payment, final settlement,
contributor allocation, delivery, compensation, and repair states.
- Do not treat notes-only V47 material as stronger than active V46 protocol law.
- Do not commercialize API/MCP, ChatGPT App, or Bitcode Chat in V47.
- Do not launch value-bearing mainnet settlement in V47.
Loading
Loading