@receiz/ai-skills 102.0.0

package/receiz-mcp-agent-skill/resources/mcp-tool-map.md

@@ -0,0 +1,61 @@
+# MCP Tool Map
+
+Source: `packages/receiz-mcp-server/src/index.ts`.
+
+## Diagnostics And Setup
+
+- `receiz_doctor`: SDK doctor for app/tenant diagnostics.
+- `receiz_capabilities`: inspect SDK capability readiness.
+- `receiz_required_scopes`: return stable scope constants by rail.
+- `receiz_runtime_blueprint`: return app runtime blueprint.
+- `receiz_authorize_url`: build Connect/OIDC authorize URL.
+- `receiz_mcp_login`: return delegated agent-token setup path.
+- `receiz_ensure_tenant_session`: build tenant customer-session entry path.
+
+## App-State And Store
+
+- `receiz_app_state_publish`: publish durable public app-state projection. Delegated write.
+- `receiz_app_state_resolve`: resolve by URL, host, namespace, ID, or creator.
+- `receiz_app_state_by_url`
+- `receiz_app_state_by_creator`
+- `receiz_app_state_by_namespace`
+- `receiz_app_state_by_id`
+- `receiz_public_store_publish`: publish typed public-store projection. Delegated write.
+- `receiz_public_store_resolve`: resolve public-store projection.
+
+## Resolution, Inspection, And Proof
+
+- `receiz_inspect_offline_file`: shape inspection only; never a verified artifact verdict.
+- `receiz_asset_by_url`
+- `receiz_asset_by_id`
+- `receiz_inspect_proof_object`
+- `receiz_proof_query`: delegated proof query projection.
+
+Use SDK `verification.verifyArtifact(file)` for verification; it requires enclosing integrity and ownership continuity.
+
+## Sports, Wallet, World
+
+- `receiz_pitch_proof_by_witness_id`
+- `receiz_card_history`
+- `receiz_sports_conformance`
+- `receiz_wallet_public_ledger`
+- `receiz_action_ledger`
+- `receiz_world_public_snapshot`
+
+## Preview And Sandbox
+
+- `receiz_transfer_preview`: preview only.
+- `receiz_transfer_requires_confirmation`: confirmation policy.
+- `receiz_pack_open_preview`: preview only.
+- `receiz_marketplace_template_generate`: template envelope only.
+- `receiz_sandbox_seed_store`: deterministic sandbox store.
+- `receiz_sandbox_checkout`: deterministic sandbox checkout.
+
+## Resource Templates
+
+- `receiz://asset/{id}`
+- `receiz://proof/{id}`
+- `receiz://pitch/{witnessId}`
+- `receiz://store/{tenantHost}`
+- `receiz://sdk/docs`
+- `receiz://schemas/proof-object-v1`

package/receiz-mcp-agent-skill/resources/response-templates.md

@@ -0,0 +1,38 @@
+# Response Templates
+
+## Tool Success
+
+```md
+Tool:
+Action class:
+Source:
+Primitive:
+Result:
+Authority boundary: MCP is tooling below Receiz proof truth.
+What is proven:
+What is not proven:
+Next safe action:
+```
+
+## Tool Failure
+
+```md
+Tool:
+Action class:
+Failure:
+Inputs used:
+What can still be reasoned:
+What cannot be claimed:
+Required next evidence:
+```
+
+## Confirmation Request
+
+```md
+Before I run this write action, confirm:
+Tool:
+Primitive affected:
+Inputs:
+Expected effect:
+Risk:
+```

package/receiz-mcp-agent-skill/resources/safe-tool-calling.md

@@ -0,0 +1,45 @@
+# Safe Tool Calling
+
+## Read-Only Tools
+
+Usually safe after input validation:
+
+- `receiz_doctor`
+- `receiz_capabilities`
+- `receiz_required_scopes`
+- `receiz_app_state_resolve`
+- `receiz_app_state_by_url`
+- `receiz_app_state_by_creator`
+- `receiz_app_state_by_namespace`
+- `receiz_app_state_by_id`
+- `receiz_public_store_resolve`
+- `receiz_inspect_offline_file`
+- `receiz_asset_by_url`
+- `receiz_asset_by_id`
+- `receiz_inspect_proof_object`
+- `receiz_wallet_public_ledger`
+- `receiz_action_ledger`
+- `receiz_sports_conformance`
+- `receiz_world_public_snapshot`
+
+## Preview-Only Tools
+
+These do not mutate proof, ownership, or settlement state:
+
+- `receiz_transfer_preview`
+- `receiz_transfer_requires_confirmation`
+- `receiz_pack_open_preview`
+- `receiz_marketplace_template_generate`
+- `receiz_runtime_blueprint`
+- `receiz_sandbox_seed_store`
+- `receiz_sandbox_checkout`
+
+## Write Or Delegated Tools
+
+Require explicit user confirmation and delegated runtime authority:
+
+- `receiz_app_state_publish`
+- `receiz_public_store_publish`
+- `receiz_proof_query` when using delegated private proof rails
+
+If a host adds more write tools later, classify by effect, not by name.

package/receiz-offline-verifier-skill/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: receiz-offline-verifier-skill
+description: Use when an agent must verify, explain, debug, or build Receiz offline verification for local files, sealed artifacts, manifests, embedded proof, airplane-mode workflows, or artifact-over-server truth boundaries.
+---
+
+# receiz-offline-verifier-skill
+
+Offline verification is a Receiz primitive. It verifies artifact truth without requiring the server, database, session, or marketplace to answer first.
+
+## When To Use This Skill
+
+- Use for local proof files, sealed artifacts, offline verifier flows, airplane-mode explanations, artifact-over-server questions, and verification failure debugging.
+- Use when the user asks whether a Receiz object remains verifiable without network access.
+- Use before building local verifier UI or offline proof diagnostics.
+
+## When Not To Use This Skill
+
+- Do not use to publish, transfer, sell, or append proof. Use `receiz-mcp-agent-skill` for writes.
+- Do not use for commerce language unless paired with `receiz-commerce-skill`.
+- Do not use to bypass access controls or expose private payloads.
+
+## Core Receiz Laws
+
+- Offline proof is not fallback mode. It is a proof primitive.
+- Artifact truth outranks server, database, session, and UI state.
+- Verify the enclosing artifact before trusting embedded subpayloads.
+- A failed server lookup does not make sealed artifact truth false.
+- Never treat a database, server, marketplace, UI, model response, or cache as final authority.
+- If offline verification fails, report the exact failed boundary.
+- Read [resources/offline-verification-law.md](resources/offline-verification-law.md) before explaining offline proof.
+
+## Required Behavior
+
+1. Identify artifact type and strongest available local proof.
+2. Verify local bytes or manifest with SDK/MCP/local verifier mechanics.
+3. Validate enclosing artifact before parsing embedded payloads.
+4. Report pass, fail, or incomplete evidence with exact boundary.
+5. Keep network checks as append or comparison, never as stronger truth than sealed proof.
+6. Use [resources/verifier-flow.md](resources/verifier-flow.md) for the step order.
+
+## Forbidden Behavior
+
+- Do not call offline proof a fallback, cache, preview, or degraded mode.
+- Do not require a server round trip before admitting known artifact truth.
+- Do not trust an embedded subpayload when the enclosing artifact fails.
+- Do not expose private identity, recovery, or sealed private payload contents.
+- Do not claim failure globally when only a specific verifier boundary failed.
+
+## MCP Usage Rules
+
+Use `receiz_inspect_offline_file` for local JSON manifest shape inspection and `receiz_inspect_proof_object` or `receiz_asset_by_id` when public proof resolution is available. MCP inspection is not verification. Use SDK `verification.verifyArtifact(file)` or the downloadable verifier for the same integrity-and-continuity verdict. If MCP is unavailable, name the exact local SDK or file evidence still available.
+
+## SDK Usage Rules
+
+Use `receiz.verification.verifyArtifact(file)`, `assertReceizProofBundle`, `assertReceizAssetManifest`, `assertReceizSportsCardManifest`, `readReceizIdentityArtifact`, `verifyReceizIdentityLoginProof`, proof register helpers, proof memory helpers, and offline proof queue helpers. See [resources/artifact-over-server.md](resources/artifact-over-server.md).
+
+## Output Format
+
+Use this format:
+
+```md
+## Offline Verification
+Artifact:
+Primitive:
+Verification mode:
+Strongest source of truth:
+Enclosing proof:
+Embedded payload:
+Result:
+Failed boundary:
+Network dependency:
+Safe next action:
+```
+
+## Safety And Security Boundaries
+
+Never print private keys, passphrases, bearer tokens, private identity artifact payloads, or recovery material. Do not upload private artifacts unless the user explicitly asks and the target verifier is trusted. Offline verification may inspect local proof, but private contents remain private.
+
+## Examples
+
+- [Verify offline asset](examples/verify-offline-asset.md)
+- [Explain offline proof](examples/explain-offline-proof.md)
+- [Debug verification failure](examples/debug-verification-failure.md)
+
+Load resources as needed:
+
+- [Offline verification law](resources/offline-verification-law.md)
+- [Verifier flow](resources/verifier-flow.md)
+- [Artifact over server](resources/artifact-over-server.md)
+- [Airplane mode principle](resources/airplane-mode-principle.md)
+- [Security boundaries](resources/security-boundaries.md)

package/receiz-offline-verifier-skill/examples/debug-verification-failure.md

@@ -0,0 +1,17 @@
+# Debug Verification Failure
+
+## Agent Steps
+
+1. Identify the failed verifier step.
+2. Separate file read failure, schema failure, integrity failure, seal failure, embedded payload failure, and network absence.
+3. State whether any verified truth remains.
+4. Give the next safe diagnostic step.
+
+## Output
+
+```md
+Failure class:
+Boundary:
+Verified truth still present:
+Next diagnostic:
+```

package/receiz-offline-verifier-skill/examples/explain-offline-proof.md

@@ -0,0 +1,9 @@
+# Explain Offline Proof
+
+Use this explanation:
+
+```md
+Offline proof means the artifact carries verification material. The server can help discover additions or public witness state, but the sealed artifact remains the stronger truth when verified.
+```
+
+Do not describe offline proof as degraded mode.

package/receiz-offline-verifier-skill/examples/verify-offline-asset.md

@@ -0,0 +1,19 @@
+# Verify Offline Asset
+
+## Agent Steps
+
+1. Read the local file or manifest.
+2. Identify the enclosing proof boundary.
+3. Run SDK `verification.verifyArtifact(file)` for verification; use `receiz_inspect_offline_file` only for manifest shape inspection.
+4. Report exact pass or failure.
+5. Avoid network dependency unless comparison is requested.
+
+## Output
+
+```md
+Artifact:
+Verification result:
+Source of truth:
+Failed boundary:
+Network required:
+```

package/receiz-offline-verifier-skill/resources/airplane-mode-principle.md

@@ -0,0 +1,15 @@
+# Airplane Mode Principle
+
+Receiz proof should remain legible when network access is absent.
+
+## Agent Rule
+
+When asked about airplane mode, explain that proof objects can carry their own verification material. The network may add public witness context, but the artifact does not become meaningless when offline.
+
+## UI Rule
+
+Offline verifier UI must show known verified truth immediately. It may show a separate area for network comparison when connectivity returns.
+
+## Failure Rule
+
+If a verification step needs network data, state that exact step. Do not say the whole artifact cannot be verified unless the artifact proof itself fails.

package/receiz-offline-verifier-skill/resources/artifact-over-server.md

@@ -0,0 +1,22 @@
+# Artifact Over Server
+
+Artifact truth outranks server confirmation.
+
+## Correct Order
+
+1. Verify artifact.
+2. Parse proof payload.
+3. Project identity, ownership, provenance, or settlement state.
+4. Optionally compare to server or public registry.
+5. Append verified additions when discovered.
+
+## Incorrect Order
+
+- Ask the database whether a local sealed proof is real before verifying the proof.
+- Treat server absence as artifact invalidity.
+- Replace artifact proof with session state.
+- Call verified local truth cache.
+
+## Agent Reporting
+
+If server and artifact disagree, say which layer is stronger and which projection needs correction.

package/receiz-offline-verifier-skill/resources/offline-verification-law.md

@@ -0,0 +1,17 @@
+# Offline Verification Law
+
+Offline verification is a Receiz proof primitive.
+
+## Law
+
+- Sealed artifact truth can be verified without waiting for a server.
+- Known verified local truth must be used immediately.
+- Network checks may append, compare, or discover additions.
+- Network checks may not erase sealed local proof.
+- Durable local truth is not cache.
+
+## Required Language
+
+Say "offline proof", "sealed artifact truth", "local verified truth", and "artifact-over-server" when those boundaries apply.
+
+Do not say "fallback", "best effort", "cached copy", or "offline preview" as product truth.

package/receiz-offline-verifier-skill/resources/security-boundaries.md

@@ -0,0 +1,20 @@
+# Security Boundaries
+
+Offline verification may inspect proof, but it must protect private material.
+
+## Never Print
+
+- Bearer tokens.
+- Private keys.
+- Passphrases.
+- Private identity artifact payloads.
+- Recovery material.
+- Hidden private proof payloads.
+
+## Safe Output
+
+Report hashes, public proof IDs, public URLs, schema names, verification status, and exact failure classes when those fields are not secret.
+
+## Upload Rule
+
+Do not upload private artifacts to an external verifier unless the user explicitly requests it and accepts the target boundary.

package/receiz-offline-verifier-skill/resources/verifier-flow.md

@@ -0,0 +1,25 @@
+# Verifier Flow
+
+## Local Verification
+
+1. Read the artifact or manifest.
+2. Identify the enclosing proof boundary.
+3. Validate schema and required proof fields.
+4. Verify integrity, signature, seal, witness, or register material when present.
+5. Project embedded payload only after the enclosing proof passes.
+6. Report exact missing or failed evidence.
+
+## Online Comparison
+
+Use online checks only to compare public proof state, discover appends, or inspect public witness surfaces. Do not make online response the stronger truth.
+
+## Failure Classes
+
+- Missing file.
+- Invalid schema.
+- Integrity mismatch.
+- Signature or seal failure.
+- Enclosing proof failure.
+- Embedded payload mismatch.
+- Unknown public proof route.
+- Network unavailable.

package/receiz-proof-skill/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: receiz-proof-skill
+description: Use when an agent must verify, inspect, explain, or report on Receiz proof objects, cards, packs, products, posts, receipts, vaults, profiles, marketplace listings, live sports objects, or offline proof artifacts.
+---
+
+# receiz-proof-skill
+
+Receiz proof inspection starts from the artifact, manifest, proof bundle, verified append, or admitted local register. Do not start from a database row, marketplace card, UI state, or model memory.
+
+## When To Use This Skill
+
+- Use for Card, Pack, Product, Post, Receipt, Vault, Profile, marketplace listing, live sports object, event proof, or offline artifact verification.
+- Use when asked "is this real", "who owns this", "what proves this", "what changed", "can I trust this", or "what can be safely done next".
+- Use before any skill that wants to create, publish, sell, transfer, inspect, or explain a Receiz object.
+
+## When Not To Use This Skill
+
+- Do not use as the only skill for building a new app. Use `receiz-builder-skill` after proof boundaries are named.
+- Do not use to execute live MCP write actions. Use `receiz-mcp-agent-skill` for tool calls and confirmation rules.
+- Do not use to invent missing proof. Missing proof must be reported as missing truth or appended through an existing Receiz rail.
+
+## Core Receiz Laws
+
+- A Receiz object is a proof-carrying artifact. Its witnessed history is the truth boundary.
+- Verify before claiming.
+- Never invent ownership, witness IDs, rarity, transfer history, or verification status.
+- Never treat a database, server, marketplace, UI, model response, or cache as final authority.
+- Never mutate witnessed history. Append new truth only.
+- If a view is wrong, rebuild the projection from witnessed history.
+- If history is missing, append the missing truth through an existing Receiz primitive.
+- Read [resources/receiz-laws.md](resources/receiz-laws.md) before explaining product truth.
+
+## Required Behavior
+
+1. Name the primitive: proof object, artifact system, ownership surface, settlement primitive, identity primitive, public proof surface, offline proof, or sports event proof.
+2. Name the strongest source of truth available.
+3. Use MCP reads or local manifest validators only for resolution and inspection; use SDK `verification.verifyArtifact(file)` for artifact verification.
+4. Separate proven facts from absent or unverified facts.
+5. Use the standard output in [resources/output-templates.md](resources/output-templates.md).
+6. Keep projection language lower than artifact truth.
+
+## Forbidden Behavior
+
+- Do not say an object is verified because a server, UI, marketplace, or model says so.
+- Do not fill unknown fields from pattern, memory, copy, filename, price, team, user handle, or visual similarity.
+- Do not call an implemented proof object a card, content item, database row, metadata wrapper, or generic share.
+- Do not treat a self-hashable subpayload as authority when it sits inside a stronger artifact.
+- Do not change proof language to soften an implemented primitive.
+
+## MCP Usage Rules
+
+Use MCP only when a live agent host has the Receiz MCP server available. MCP resolution and inspection are not artifact verification. Use `receiz_inspect_offline_file` for local JSON shape inspection, `receiz_asset_by_url` for public proof resolution, `receiz_card_history` for Sports card memory, and `receiz_pitch_proof_by_witness_id` for pitch witnesses. Use SDK `verification.verifyArtifact(file)` for the integrity-and-continuity verdict. If the MCP tool is unavailable, say what can be reasoned from available data and what still needs live verification. See [resources/mcp-tool-map.md](resources/mcp-tool-map.md).
+
+## SDK Usage Rules
+
+Use SDK validators and projectors for local proof objects: `assertReceizAssetManifest`, `assertReceizSportsCardManifest`, `assertReceizWebhookEvent`, `projectReceizAssetManifest`, `projectReceizSportsCardManifest`, `createReceizProofMemory`, and `receizProofMemoryAdditionsQuery`. Use `receiz.verification.verifyArtifact(file)` when artifact bytes need Receiz verification. See [resources/sdk-reference.md](resources/sdk-reference.md).
+
+## Output Format
+
+Use the verified object format exactly:
+
+```md
+## Verified Object
+Object:
+Status:
+Identity:
+Current controller / owner:
+Proof present:
+Witness history:
+Provenance:
+Media:
+Transfer state:
+What is proven:
+What is not proven:
+Safe next action:
+```
+
+## Safety And Security Boundaries
+
+Read-only verification is safe when it does not expose private payloads. Writes, transfers, settlement actions, publishing, or proof appends require explicit user confirmation and an existing Receiz write rail. Never request or print private keys, bearer tokens, passphrases, private proof material, or hidden recovery payloads.
+
+## Examples
+
+- [Verify card](examples/verify-card.md)
+- [Verify product](examples/verify-product.md)
+- [Verify post](examples/verify-post.md)
+- [Verify pack](examples/verify-pack.md)
+- [Verify vault](examples/verify-vault.md)
+
+Load resources as needed:
+
+- [Receiz laws](resources/receiz-laws.md)
+- [Proof object model](resources/proof-object-model.md)
+- [Verification flow](resources/verification-flow.md)
+- [Output templates](resources/output-templates.md)
+- [Failure modes](resources/failure-modes.md)
+- [MCP tool map](resources/mcp-tool-map.md)
+- [SDK reference](resources/sdk-reference.md)

package/receiz-proof-skill/examples/verify-card.md

@@ -0,0 +1,21 @@
+# Verify Card
+
+Use `assertReceizSportsCardManifest` or MCP `receiz_inspect_offline_file` only to inspect a local card manifest shape. Use SDK `verification.verifyArtifact(file)` for verification. Use `receiz_card_history` when the user provides local card memory or asks for append history.
+
+Report:
+
+```md
+## Verified Object
+Object: Sports card proof object
+Status: verified, inspected, or not verified
+Identity: collectible ID and claim hash from the manifest
+Current controller / owner: ownership owner label only if present
+Proof present: card manifest, value basis, append summary, event proof summary, links
+Witness history: append and event proof summary counts
+Provenance: sport, source links, verify link
+Media: deterministic card image or media URL when present
+Transfer state: only from ownership or appends
+What is proven: fields validated from the manifest
+What is not proven: any missing owner, rarity, transfer, or event data
+Safe next action: inspect event proofs, resolve card history, or append missing truth
+```

package/receiz-proof-skill/examples/verify-pack.md

@@ -0,0 +1,14 @@
+# Verify Pack
+
+A pack is an artifact/proof object when it carries stable pack identity, pack-open receipt, card claim outputs, reward lane, ownership, and append history.
+
+Use `receiz_pack_open_preview` only for preview. A preview does not append pack truth and does not prove issuance.
+
+A verified pack report must distinguish:
+
+- pack preview
+- issued pack
+- opened pack
+- claimed cards
+- verified run receipt when Pack Derby issued the pack
+- missing proof or missing append state

package/receiz-proof-skill/examples/verify-post.md

@@ -0,0 +1,7 @@
+# Verify Post
+
+Treat a Receiz post as public proof only when it carries proof object identity, public proof record, provenance, source URL, verification affordance, or admitted local truth.
+
+Use `receiz_asset_by_url` or SDK `publicProof.byUrl` to resolve public proof rails, then SDK `verification.verifyArtifact(file)` for verification. If the post is visible only as a UI projection, report that the public proof surface still needs proof-object continuity evidence.
+
+Never claim global visibility or canonical profile truth from an owner-only view or DB row alone.

package/receiz-proof-skill/examples/verify-product.md

@@ -0,0 +1,7 @@
+# Verify Product
+
+Treat a product as a proof-carrying object when it has product identity, media, provenance, ownership/custody, receipt or listing state, verify link, or public-store proof state.
+
+Use `receiz_public_store_resolve` or SDK `publicStore.resolve` for storefront projection. Use artifact verification or manifest validation for the actual proof object.
+
+Do not prove price, seller, stock, ownership, or purchase status from storefront copy alone.

package/receiz-proof-skill/examples/verify-vault.md

@@ -0,0 +1,7 @@
+# Verify Vault
+
+A Receiz vault is an artifact system. It carries owned proof objects, custody state, provenance, media, action affordances, and public/private projection surfaces.
+
+Verify vault objects by inspecting each carried proof object or admitted proof register entry. Do not reduce the vault to a content grid or account dashboard.
+
+Report transferred-out, listed, held, certified, verified, or claimable states only when the vault proof, ownership append, or route output carries that state.

package/receiz-proof-skill/resources/failure-modes.md

@@ -0,0 +1,31 @@
+# Failure Modes
+
+## Hallucinated Truth
+
+Symptom: the agent says ownership, rarity, transfer state, witness ID, or verification status without tool output or artifact evidence.
+
+Correction: state the exact missing evidence and stop at "not proven".
+
+## Server-As-Authority Drift
+
+Symptom: a DB row, API response, marketplace state, UI label, or server availability is treated as final proof.
+
+Correction: identify it as projection and ask for the sealed artifact, manifest, verified append, public proof rail, or admitted register.
+
+## Projection Replaces Artifact
+
+Symptom: display rows, generated app state, or marketplace copy overrides the proof object.
+
+Correction: rebuild the projection from the artifact history.
+
+## Subpayload Overreach
+
+Symptom: a hashable embedded payload is treated as admission, ownership, transfer, settlement, or access authority.
+
+Correction: verify the enclosing stronger artifact first.
+
+## Missing Tool Honesty
+
+Symptom: the agent says verification happened even when MCP, SDK, or artifact bytes were unavailable.
+
+Correction: report what was inspected and what still needs live or local verification.

package/receiz-proof-skill/resources/mcp-tool-map.md

@@ -0,0 +1,49 @@
+# Receiz MCP Tool Map For Proof Work
+
+Source: `packages/receiz-mcp-server/src/index.ts`.
+
+## Authority Boundary
+
+MCP is not authority. It calls canonical Receiz SDK/API rails and reports the source primitive. Its responses remain beneath sealed artifact truth, deterministic proof object state, verified local truth, verified register append, and authenticated SDK/API projection.
+
+## Verification And Inspection
+
+| Need | Tool | Boundary |
+| --- | --- | --- |
+| Public proof by URL or ID | `receiz_asset_by_url`, `receiz_asset_by_id` | Resolves through SDK public proof rails; does not claim verification. |
+| Local JSON manifest inspection | `receiz_inspect_offline_file` | Uses SDK shape validators and always reports `verified: false`. |
+| Public asset by URL | `receiz_asset_by_url` | Public proof surface read. |
+| Public asset by ID | `receiz_asset_by_id` | Public proof surface read. |
+| Payload inspection | `receiz_inspect_proof_object` | Structural inspection, not final verifier authority. |
+| Proof query | `receiz_proof_query` | Delegated proof query projection; requires delegated write/read authority in runtime. |
+
+## Sports Proof
+
+| Need | Tool | Boundary |
+| --- | --- | --- |
+| Sports card history | `receiz_card_history` | Local-first SDK card memory rail. |
+| Pitch witness | `receiz_pitch_proof_by_witness_id` | Requires already-admitted local pitch day proof truth. |
+| Sports conformance | `receiz_sports_conformance` | Reads conformance status. |
+| Pack preview | `receiz_pack_open_preview` | Preview only; does not append card truth. |
+
+## Settlement And Ownership
+
+| Need | Tool | Boundary |
+| --- | --- | --- |
+| Transfer preview | `receiz_transfer_preview` | Deterministic preview; no settlement mutation. |
+| Transfer confirmation policy | `receiz_transfer_requires_confirmation` | Confirmation requirement only. |
+| Wallet ledger | `receiz_wallet_public_ledger` | Settlement projection over ledger truth. |
+| Action ledger | `receiz_action_ledger` | Provenance projection. |
+
+## App And Store Proof Surfaces
+
+| Need | Tool |
+| --- | --- |
+| App-state resolve | `receiz_app_state_resolve`, `receiz_app_state_by_url`, `receiz_app_state_by_creator`, `receiz_app_state_by_namespace`, `receiz_app_state_by_id` |
+| Public store resolve | `receiz_public_store_resolve` |
+| Template envelope | `receiz_marketplace_template_generate` |
+| Runtime blueprint | `receiz_runtime_blueprint` |
+
+## Writes
+
+`receiz_app_state_publish`, `receiz_public_store_publish`, and `receiz_proof_query` can require delegated runtime authority. Ask for explicit confirmation before any action that appends, publishes, changes settlement, changes ownership, or affects public state.