V46 Gate 2: Define protocol comprehension claims

Adds the source-safe V46 protocol comprehension object model and deterministic artifact for AssetPack, BTD, BTC, preview, quote, settlement, rights, delivery, compensation, proof, repair, and InterfaceClaim readback.

Documents the claim taxonomy across protocol law, product guidance, operator evidence, investor framing, telemetry, preview, quote, settlement, rights, delivery, compensation, and repair, then wires generation, checks, workflows, package exports, and protocol tests.

Validation: pnpm run check:v46-gate2; node scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs --skip-branch-check; node scripts/check-bitcode-spec-family.mjs --version V45 --mode promoted --current-target V45; node scripts/check-bitcode-spec-family.mjs --version V46 --mode draft --current-target V45; node scripts/check-bitcode-canonical-inputs.mjs --current-target V45; node scripts/check-bitcode-canon-posture-drift.mjs --active-canon V45 --draft-target V46; pnpm --filter @bitcode/protocol typecheck; pnpm --filter @bitcode/protocol test; git diff --check.

Author: geraldarthurdavis

.bitcode/v46-protocol-comprehension-object-model.json

@@ -422,6 +422,9 @@ jobs:
               if [ -f scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs ]; then
                 node scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs --skip-branch-check
               fi
+              if [ -f scripts/check-v46-gate2-protocol-comprehension-object-model.mjs ]; then
+                node scripts/check-v46-gate2-protocol-comprehension-object-model.mjs --skip-branch-check --skip-package-tests
+              fi
             fi
           else
             echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2

.github/workflows/bitcode-canon-quality.yml

@@ -551,6 +551,9 @@ jobs:
               if [ -f scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs ]; then
                 node scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs --skip-branch-check
               fi
+              if [ -f scripts/check-v46-gate2-protocol-comprehension-object-model.mjs ]; then
+                node scripts/check-v46-gate2-protocol-comprehension-object-model.mjs --skip-branch-check --skip-package-tests
+              fi
             fi
           else
             echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2
@@ -592,6 +595,9 @@ jobs:
               if [ -f BITCODE_SPEC_V46.md ] && [ -f scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs ]; then
                 node scripts/check-v46-gate1-commercial-protocol-comprehension-roadmap.mjs --skip-branch-check
               fi
+              if [ -f BITCODE_SPEC_V46.md ] && [ -f scripts/check-v46-gate2-protocol-comprehension-object-model.mjs ]; then
+                node scripts/check-v46-gate2-protocol-comprehension-object-model.mjs --skip-branch-check --skip-package-tests
+              fi
             fi
             if [ "$POINTER" = "V43" ] && [ -f scripts/check-v44-gate1-scaled-economy-roadmap-opening.mjs ]; then
               node scripts/check-v44-gate1-scaled-economy-roadmap-opening.mjs --skip-branch-check

.github/workflows/bitcode-gate-quality.yml

@@ -160,6 +160,100 @@ V46 consolidates these canonical objects and states:
   `btc-settlement-finalized`, `btc-contributor-compensation-routable`,
   `btc-refund-or-escalation-required`, and `btc-settlement-repair-required`.
 
+## V46 commercial protocol comprehension object model
+
+V46 Gate 2 makes the commercial comprehension object model explicit so public,
+product, operator, API/MCP, ChatGPT App, Bitcode Chat, and investor-facing
+surfaces all explain the same protocol without claiming more than their
+evidence supports.
+
+The comprehension object model is source-safe metadata. It describes objects,
+claims, disclosure boundaries, evidence authority, and forbidden
+interpretations. It does not expose protected source, unpaid AssetPack source,
+raw prompts, raw provider responses, credentials, wallet private material,
+private settlement payloads, private Read context, or value-bearing mainnet
+admission.
+
+Canonical comprehension objects:
+
+| Object | Protocol reading | Claim boundary |
+| --- | --- | --- |
+| `AssetPack` | Packaged technical knowledge commodity; never raw source. | May be explained as deposit supply, previewed Need-Fit pack, or settled delivery only when its lifecycle state is named. |
+| `DepositAssetPackOption` | Proposed source-safe supply for depositor review. | May show BTD potential and policy posture, never final BTD, payment, or public source. |
+| `DepositoryAssetPack` | Approved searchable supply with protected-source roots. | May be recalled, ranked, and selected source-safely through Finding Fits. |
+| `ReadRequest` | Buyer demand input. | Does not itself create a reviewed Need, Fit, quote, BTD, or rights. |
+| `ReviewedNeed` | Accepted buyer objective that authorizes Finding Fits. | Enables Need-relative measurement but does not calculate final BTD by itself. |
+| `FindingFitsReceipt` | Search, ranking, threshold, provenance, and repair evidence. | May name many candidates and selected Fits without source disclosure. |
+| `SelectedFitSet` | One or many admitted Depository AssetPacks accepted for synthesis. | Required for Need-Fit synthesis and final BTD calculation. |
+| `NeedFitAssetPack` | New Need-relative AssetPack synthesized from reviewed Need and selected Fits. | Source-bearing internally but withheld until BTC finality and BTD rights transfer. |
+| `SourceSafePreview` | Measurements, quality, provenance, BTD posture, quote readiness, and proof roots. | Preview is not source disclosure. |
+| `BtdScalarVolumeReceipt` | Need-relative weighted scalar technical knowledge volume. | BTD is not money and not merely a read-right; settled BTD carries rights. |
+| `BtcQuote` | Deterministic sats offer bound to BTD volume, policy, network, expiry, and authority. | Quote is not payment. |
+| `BtcSettlementReceipt` | Quote/payment/finality/readback evidence. | Observed payment is not final settlement. |
+| `BtdRightsReceipt` | Settled rights, source unlock authority, ownership/read/use boundary. | Rights transfer follows BTC finality and reconciliation. |
+| `SourceUnlockDeliveryReceipt` | Entitled repository delivery evidence. | Full source crosses only to the entitled Reader boundary. |
+| `SourceToSharesAllocation` | Contributor allocation derived after final Need-Fit settlement. | Allocation is compensation routing, not BTD scalar-volume calculation. |
+| `ContributorCompensationStatement` | Post-finality BTC compensation readback. | Database projection must reconcile to ledger truth. |
+| `ProofRoot` | Evidence root for state advancement or explanation. | Proof can support state but cannot leak hidden payloads. |
+| `RepairCase` | Fail-closed blocker for missing or contradictory evidence. | Repair returns to the narrowest source-safe disclosure boundary. |
+| `InterfaceClaim` | Any public, product, API/MCP, ChatGPT App, Bitcode Chat, telemetry, or operator statement about protocol state. | Must name claim category, evidence authority, disclosure boundary, and forbidden interpretation. |
+
+Claim authority is evidence-specific. Canonical specification and generated
+proof define protocol law; ledger readback governs settlement truth; database
+projection is a synchronized projection; object storage roots prove custody and
+withheld bundles; wallet/provider receipts prove payment observations and
+wallet posture; repository delivery receipts prove entitled delivery;
+telemetry is observability only; interfaces guide and inspect; public education
+explains but does not create live transaction truth.
+
+## V46 claim taxonomy law
+
+Every V46 explanatory statement is an `InterfaceClaim` and must occupy one
+claim category:
+
+- `protocol-law`: formal AssetPack, BTD, BTC, source-safety, rights,
+  compensation, proof, and repair law from the specification family.
+- `product-guidance`: route or workflow guidance that helps users act but does
+  not advance protocol state.
+- `operator-evidence`: source-safe operational evidence, proof roots, runbook
+  posture, and repair information.
+- `investor-framing`: market or deck language; investor framing is not
+  protocol law unless reconciled into the formal specification family.
+- `telemetry-observability`: execution progress and debug signals; telemetry
+  is observability only and cannot advance state by itself.
+- `preview-claim`: source-safe pre-settlement measurement and quality
+  statement.
+- `quote-claim`: BTC quote, expiry, budget, policy, and wallet-readiness
+  statement.
+- `settlement-claim`: BTC preparation, signing, broadcast, observation,
+  mismatch, finality, reconciliation, refund, escalation, or repair statement.
+- `rights-claim`: BTD rights-pending or rights-transferred statement.
+- `delivery-claim`: source unlock and repository delivery statement.
+- `compensation-claim`: source-to-shares allocation or contributor
+  compensation statement.
+- `repair-claim`: fail-closed blocker, replay, operator action, or repair
+  closure statement.
+
+Forbidden claim collapses:
+
+- AssetPack is not raw source.
+- BTD is not only a read-right and is not money.
+- Deposit option is not final BTD.
+- Preview is not source disclosure.
+- Quote is not payment.
+- Payment observation is not finality.
+- Database projection is not ledger truth when stronger readback conflicts.
+- Telemetry and conversation do not advance state.
+- Investor copy is not protocol law.
+- Value-bearing mainnet remains blocked until a promoted canon admits it.
+- Bitcode never takes custody of wallet private material.
+
+For V46, investor framing is not protocol law; telemetry is observability only.
+
+The source-safe generated artifact for this Gate 2 atom is
+`.bitcode/v46-protocol-comprehension-object-model.json`; it is generated by
+`buildV46ProtocolComprehensionObjectModel` and checked by `check:v46-gate2`.
+
 ## V46 whole Bitcode operator chain
 
 The V46 operator chain is: connect source and organization policy, synthesize

BITCODE_SPEC_V46.md

@@ -70,6 +70,32 @@ V45, the roadmap names the V46 focus and tentative gates, the branch/check
 contract is present, CI knows how to validate active V45 plus draft V46, and no
 V46 file claims promoted authority.
 
+## Gate 2: Protocol Comprehension Object Model And Claim Taxonomy
+
+Gate 2 adds `V46ProtocolComprehensionObjectModel` as a source-safe generated
+artifact at `.bitcode/v46-protocol-comprehension-object-model.json`. It
+formalizes the object vocabulary and claim taxonomy that every public,
+product, operator, API/MCP, ChatGPT App, Bitcode Chat, telemetry, and
+investor-facing surface must use when explaining Bitcode.
+
+Accepted Gate 2 decisions:
+
+- AssetPack, BTD, BTC, Finding Fits, source-safe preview, quote, settlement,
+  rights transfer, delivery, compensation, proof, repair, and interface claims
+  are distinct comprehension objects.
+- Every explanation is an `InterfaceClaim` with a category, authority source,
+  disclosure boundary, required evidence class, and forbidden interpretation.
+- Claim categories are `protocol-law`, `product-guidance`,
+  `operator-evidence`, `investor-framing`, `telemetry-observability`,
+  `preview-claim`, `quote-claim`, `settlement-claim`, `rights-claim`,
+  `delivery-claim`, `compensation-claim`, and `repair-claim`.
+- Claim authority is evidence-specific: generated proof, ledger readback,
+  database projection, object storage root, wallet/provider receipt,
+  repository delivery receipt, telemetry, interface guidance, and public
+  education do not have interchangeable authority.
+- Gate 2 is still specification/proof metadata work. It does not authorize
+  route, API, settlement, delivery, or value-bearing mainnet behavior changes.
+
 ## Commit-Body Direction
 
 V46 commit bodies should name the gate class, protocol law or interface claim

BITCODE_SPEC_V46_DELTA.md

@@ -84,6 +84,79 @@ files, preserves `BITCODE_SPEC.txt -> V45`, names the draft focus, wires a
 Gate 1 checker, and prepares CI to validate active V45 plus draft V46. It does
 not authorize runtime behavior or generated V46 proof-family artifacts.
 
+## Gate 2: Protocol Comprehension Object Model And Claim Taxonomy
+
+Gate 2 records the first package-backed V46 comprehension atom. It creates a
+source-safe object model and claim taxonomy artifact for the commercial
+protocol explanation layer. It remains draft-target metadata over active V45:
+no route behavior, API behavior, settlement behavior, delivery behavior,
+source disclosure, or value-bearing mainnet admission is authorized by this
+gate.
+
+## V46 protocol atom 6: protocol comprehension object model and claim taxonomy
+
+Audit classification: V46 already names the major protocol objects in the
+specification, and V45 already proves the knowledge commoditization law. The
+remaining comprehension gap is that external and interface statements need a
+typed claim boundary: what object is being described, what authority backs the
+claim, which disclosure boundary applies, and which common overclaims are
+forbidden.
+
+Protocol-law statement:
+
+Every public, product, operator, API/MCP, ChatGPT App, Bitcode Chat,
+telemetry, investor, or documentation statement about Bitcode is an
+`InterfaceClaim`. Each `InterfaceClaim` must identify the object it describes,
+the claim category, the evidence authority, the disclosure boundary, required
+proof/readback roots, and forbidden interpretations. Claims may simplify
+language for their audience, but they may not collapse AssetPack, BTD, BTC,
+preview, quote, observed payment, finality, rights transfer, delivery,
+compensation, proof, or repair states.
+
+Claim taxonomy separates protocol law from product guidance, operator evidence, investor framing, telemetry, preview, quote, settlement, rights, delivery, compensation, and repair claims.
+
+The canonical claim categories are:
+
+- `protocol-law`
+- `product-guidance`
+- `operator-evidence`
+- `investor-framing`
+- `telemetry-observability`
+- `preview-claim`
+- `quote-claim`
+- `settlement-claim`
+- `rights-claim`
+- `delivery-claim`
+- `compensation-claim`
+- `repair-claim`
+
+The canonical authority classes are:
+
+- `canonical-specification`
+- `generated-proof`
+- `ledger-readback`
+- `database-projection`
+- `object-storage-root`
+- `wallet-provider-receipt`
+- `repository-delivery-receipt`
+- `telemetry-observability-only`
+- `interface-guidance-only`
+- `public-education-only`
+
+Forbidden claim collapses are now explicit: AssetPack is not raw source, BTD
+is not only a read-right and not money, deposit option is not final BTD,
+preview is not source disclosure, quote is not payment, observed payment is
+not finality, database projection is not ledger truth when stronger readback
+conflicts, telemetry and conversation do not advance state, investor copy is
+not protocol law, value-bearing mainnet remains blocked, and Bitcode never
+takes custody of wallet private material.
+
+Acceptance for this atom: later V46 documentation, route, API/MCP, ChatGPT
+App, Bitcode Chat, public docs, landing, proof, and rehearsal gates may adapt
+the wording by surface, but they must preserve this object model, claim
+taxonomy, evidence-specific authority, disclosure boundary labeling,
+forbidden-collapse list, and source-safe generated artifact posture.
+
 ## V46 opening discussion frame
 
 V46 opened from the premise that specification is the source of protocol truth.

BITCODE_SPEC_V46_NOTES.md

@@ -60,7 +60,7 @@ source files and generated artifacts that implement or explain each row.
 | Area | Required V46 result | Current judgment | Source-grounded finding | Closure gate |
 | --- | --- | --- | --- | --- |
 | Commercial protocol comprehension | Explain Bitcode as knowledge commoditization without reducing BTD to a read-right or AssetPack to raw source | draft-required | V45 law is precise but launch-facing surfaces need a shared claim taxonomy and readback language. | Gate 2 |
-| Claim taxonomy | Separate protocol law, product guidance, operator evidence, investor framing, telemetry, preview, quote, settlement, rights, and delivery claims | draft-required | Gate 1 names the need; no taxonomy is source-audited yet. | Gate 2 |
+| Claim taxonomy | Separate protocol law, product guidance, operator evidence, investor framing, telemetry, preview, quote, settlement, rights, delivery, compensation, and repair claims | implemented prerequisite | Gate 2 owns package-backed `V46ProtocolComprehensionObjectModel`, deterministic `.bitcode/v46-protocol-comprehension-object-model.json`, object rows, claim rows, evidence-specific authority ids, disclosure boundary ids, forbidden claim collapse ids, source-safe generated artifact freshness, protocol tests, docs, and workflow wiring. | Gate 2 |
 | Public and operator docs | Public docs, landing copy, README/operator docs, and route help stay accurate, source-safe, and non-overclaiming | draft-required | Existing docs inherit V45 law but need V46 claim-boundary audit. | Gate 3 |
 | Product route comprehension | `/packs`, `/read`, and `/deposit` expose low-detail default UX with expandable proof and consistent commercial terms | implemented prerequisite | V43-V45 product routes exist; V46 must audit copy, state labels, and proof readback against commercial comprehension. | Gate 4 |
 | Machine and conversation interfaces | API/MCP, ChatGPT App, Bitcode Chat, and package consumers expose the same claim boundaries as website routes | draft-required | Prior interface parity exists, but V46 needs launch-facing readback contracts. | Gate 5 |
@@ -78,6 +78,7 @@ source files and generated artifacts that implement or explain each row.
 | Source safety | No V46 explanatory surface may expose protected source, unpaid AssetPack source, raw prompts, raw responses, credentials, or wallet-private material | accepted boundary | V45 source-safety law remains binding. | Gate 2+ |
 | Value-bearing mainnet | V46 launch comprehension work must not imply value-bearing mainnet authority | accepted boundary | V45 value-bearing mainnet block remains binding. | Gate 2+ |
 | Implementation scope | Runtime work begins only after formal specification and parity gates authorize it | accepted boundary | Gate 1 is roadmap/spec/checking only. | Gate 4+ |
+| Protocol comprehension object model | V46 explanation surfaces share object ids, claim categories, claim authority ids, disclosure boundaries, and forbidden interpretation ids | implemented prerequisite | `V46ProtocolComprehensionObjectModel` binds AssetPack, BTD, BTC, preview, quote, settlement, rights, delivery, compensation, proof, repair, and InterfaceClaim rows without source-bearing payloads. | Gate 2 |
 
 ## Grouped Closure Gates
 

BITCODE_SPEC_V46_PARITY_MATRIX.md

@@ -429,6 +429,28 @@ promotion, protected source, unpaid AssetPack source, raw prompts, provider
 payloads, credentials, wallet private material, private settlement payloads,
 live logs, and value-bearing mainnet operation.
 
+V46 Gate 1 opens commercial protocol comprehension work over the promoted
+`V45` active, `V46` draft posture with the V46 specification family and
+`check:v46-gate1`. It keeps `BITCODE_SPEC.txt` pointed at `V45` while naming
+V46's launch-facing focus: public/operator explanation, `/packs`, `/read`,
+`/deposit`, API/MCP, ChatGPT App, Bitcode Chat, proof readback, and source-safe
+claim boundaries for Bitcode as the knowledge commoditization system.
+
+V46 Gate 2 adds `V46ProtocolComprehensionObjectModel`,
+`.bitcode/v46-protocol-comprehension-object-model.json`,
+`generate:v46-protocol-comprehension-object-model`,
+`check:v46-protocol-comprehension-object-model`, and `check:v46-gate2`.
+It binds source-safe object rows for AssetPack, deposit options, Depository
+AssetPacks, Read Requests, reviewed Needs, Finding Fits, selected Fit sets,
+Need-Fit AssetPacks, previews, BTD scalar volume, BTC quotes/settlement,
+rights, delivery, source-to-shares compensation, proof, repair, and
+`InterfaceClaim`; it also separates protocol law, product guidance, operator
+evidence, investor framing, telemetry, preview, quote, settlement, rights,
+delivery, compensation, and repair claims without exposing protected source,
+unpaid AssetPack source, prompts, provider payloads, credentials, wallet
+private material, private settlement payloads, or value-bearing mainnet
+authority.
+
 Exchange is inherited V36 canon: market-wide activity master-detail, buy/sell/
 bid/ask/cancel/accept/settle/history flows, AssetPack range trading,
 rights-transfer review, pricing/liquidity/wrapper analysis, settlement