@receiz/ai-skills 124.0.2 → 124.1.0

package/receiz-migrations/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-migrations",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1327,6 +1327,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1424,6 +1428,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1518,5 +1526,6 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
-  ]
+  ],
+  "v124_1CapabilityIds": []
 }

package/receiz-multi-subject-transaction/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-multi-subject-transaction",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1225,6 +1225,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1322,6 +1326,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1416,5 +1424,6 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
-  ]
+  ],
+  "v124_1CapabilityIds": []
 }

package/receiz-observability/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-observability",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1264,6 +1264,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1361,6 +1365,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1455,5 +1463,6 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
-  ]
+  ],
+  "v124_1CapabilityIds": []
 }

package/receiz-offline-command/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-offline-command",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1249,6 +1249,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1346,6 +1350,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1440,5 +1448,6 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
-  ]
+  ],
+  "v124_1CapabilityIds": []
 }

package/receiz-offline-first/SKILL.md

@@ -66,3 +66,9 @@ Historical sealed proof objects remain exact-byte verifiable evidence. Historica
 Use canonical head → entire proof history → bounded index retrieval → exact primary-object resolution → reasoning → provenance. The 96-object window is working context, never history truncation. AI speech and performance remain non-authoritative. Consequential actions require typed deterministic command admission; meetings, relationships, trades, gifts, and battles require atomic multi-subject transactions. Autonomous execution requires a current digest-bound mandate at lease time. Bearer transfer preserves identity, full history, memory policy, inventory disposition, and unknown namespace bytes while immediately revoking former-owner authority.
 
 Concrete v120 evidence must include: a creature speaking from exact long-form proof memory; absent-owner exploration inside a mandate; a mutual relationship; a bounded autonomous trade; an atomic battle; exact device restoration; queued-action revocation; partition convergence without history replacement; rejection of an AI-invented event; and cross-application subject continuity.
+
+<!-- receiz-v124.1-capability-map:start -->
+## V124.1 callable capability bindings
+
+- **portable-account-continuity.** Seal, verify, and immediately project complete account truth—including profile, showcase, wallet, market positions/history, media, and proof history—without waiting on a server or database. SDK: `appendReceizIdentityPortableState`, `verifyReceizIdentityPortableStateProof`, `projectReceizIdentityAccount`. MCP: none: private SDK boundary. Boundary: The verified Identity Seal, Identity Record, or Receiz Key carries account truth. Private portable state is not exposed through MCP; server synchronization may append verified additions only after immediate local projection.
+<!-- receiz-v124.1-capability-map:end -->

package/receiz-offline-first/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-offline-first",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1264,6 +1264,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1361,6 +1365,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1455,5 +1463,8 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
+  ],
+  "v124_1CapabilityIds": [
+    "portable-account-continuity"
   ]
 }

package/receiz-offline-verifier-skill/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-offline-verifier-skill",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1304,6 +1304,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1401,6 +1405,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1495,5 +1503,6 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
-  ]
+  ],
+  "v124_1CapabilityIds": []
 }

package/receiz-performance/SKILL.md

@@ -51,6 +51,22 @@ Request: Assign numeric fixture budgets and optimize beneath deterministic known
 
 Return a written implementation contract and read-only plan first. Execute only allowed commands after exact confirmation, then report registry digest, laws, authority, tests, independent evidence, release-lock status, and the exact remaining boundary.
 
+
+
+
+
+<!-- receiz-source-carried-law:start -->
+## Source-carried conversation and material law
+
+The enclosing sealed proof object is **enclosing-proof authority**. A source token, manifest digest, segment digest, family digest, local-custody marker, SDK projection, or MCP result can verify or coordinate a deterministic projection, but none may replace the enclosing proof object.
+
+Conversation participation uses **Receiz-ID participant binding** to exact subject and access-key heads. There is **no fixed total member or history cap**: canonical history remains complete, while retrieval, reasoning, epoch grants, and MCP output use bounded windows. Revoking a participant requires **epoch rotation on revoke** before later private messages. Use **bounded grant operations** through `planReceizConversationEpochGrantBatchesV1` or `receiz_conversation_epoch_grants_plan`; the clear epoch secret stays in trusted-host custody and never enters model output.
+
+Reconstruction is **held-first reconstruction**. Open complete locally held conversation sources with `openReceizConversationSourceFamilyV1` or `receiz_conversation_source_family_open`. Open complete locally held media sources with `openReceizMaterialSourceParts`, then project raw RMA3 material with `createReceizRawMaterialCapsuleBlobFromSourceParts`, or inspect bounded coordinates through `receiz_material_source_parts_open`. Complete custody is **no-fetch complete custody**: once every exact source is held, verification and reconstruction must perform zero network fetches and must not consult a database, session, or server before known-truth use.
+
+Legacy and whole-payload-SHA-only media preserves the **whole-artifact-required fallback**. Newly sealed audio/video may carry a compact `receiz.material.progressive-ranges.v1` commitment inside the enclosing Signature-V4 proof. Build and validate its carried ledger with `buildReceizMaterialProgressiveLedger`, `createReceizMaterialProgressiveCommitment`, and the source-family reader; accept it only when the full ledger recomputes the signed root, then verify every requested range digest before projection. Never infer range authority from unsigned offsets, container metadata, transport segment hashes, a manifest, or an MCP result. `receiz_material_source_parts_open` may expose only the compact progressive summary among **non-authoritative MCP projections**. Material bytes, content-bearing locators, exact conversation sources, clear message bodies, and epoch secrets stay outside model output.
+<!-- receiz-source-carried-law:end -->
+
 ## v120 artifact-derived authority
 
 Engineers remain free to build whatever they choose, but conforming Receiz receivers recognize authority only when every authority-bearing value is provably derived from independently verified artifact truth. Custom JavaScript objects, callbacks, normalized histories, local receipts, server rows, sessions, MCP memory, and AI explanations remain application data or inspection material; their shape never creates Receiz authority.
@@ -60,3 +76,10 @@ Admission begins from runtime-custodied verification of the exact enclosing arti
 Deterministic plan identity and unique execution-attempt identity are separate. MCP may reuse a confirmation digest only while the identical attempt is actively pending; committed and failed attempts are terminal and require a fresh confirmation. Expected authority failures are structured, immutable, machine-readable, and report zero writes.
 
 Historical sealed proof objects remain exact-byte verifiable evidence. Historical runtime admissions, histories, actors, capabilities, plans, candidates, stores, or confirmations cannot authorize a current v121 receiver; exact bytes crossing a process require `reverify-exact-bytes`, followed by current profile admission and `same-runtime-custody` through plan, capability, seal, stage, independent byte resolution, atomic named-domain acceptance, and report-only receipt.
+
+<!-- receiz-v124.1-capability-map:start -->
+## V124.1 callable capability bindings
+
+- **held-material-reconstruction.** Build, publish, hold, reopen, and reconstruct inline RMA2 or segmented RMC1/RMC2 with raw RMA3 projection while verifying the enclosing artifact before native media use. SDK: `buildReceizMaterialCompositeTransport`, `publishReceizMaterialCompositeTransport`, `resolveReceizMaterialCompositeTransport`, `createReceizMaterialSourceFamily`, `createReceizClosedMaterialPresentationUrl`, `openReceizMaterialSourceParts`, `createReceizRawMaterialCapsuleBlobFromSourceParts`, `decodeReceizRawMaterialCapsuleBytes`, `resolveReceizMaterialCompositeFromSources`, `openVerifiedReceizMaterialUrl`. MCP: `receiz_material_source_parts_open`, `receiz_material_url_open`. Boundary: Transport segments, locators, manifests, object URLs, and storage are projections only. Native bytes are admitted only beneath verification of the enclosing sealed artifact.
+- **progressive-range-playback.** Start verified first-frame playback from signed range commitments while remaining ranges settle behind the already playing media. SDK: `buildReceizMaterialProgressiveLedger`, `createReceizMaterialProgressiveCommitment`, `coerceReceizMaterialProgressiveLedger`, `coerceReceizMaterialProgressiveCommitment`, `openReceizMaterialSourceRangeReader`. MCP: `receiz_material_source_parts_open`. Boundary: Only a progressive ledger whose complete root is carried by the enclosing Signature-V4 proof can authorize range projection. Unsigned offsets, container metadata, or transport segments cannot.
+<!-- receiz-v124.1-capability-map:end -->

package/receiz-performance/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-performance",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -24,7 +24,9 @@
     "receiz_artifact_admit",
     "receiz_artifact_append_plan",
     "receiz_artifact_transition_seal_and_stage",
-    "receiz_artifact_transition_commit"
+    "receiz_artifact_transition_commit",
+    "receiz_conversation_source_family_open",
+    "receiz_material_source_parts_open"
   ],
   "forbiddenOperations": [
     "direct-state-write",
@@ -1264,6 +1266,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1361,6 +1367,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1455,5 +1465,9 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
+  ],
+  "v124_1CapabilityIds": [
+    "held-material-reconstruction",
+    "progressive-range-playback"
   ]
 }

package/receiz-portable-artifacts/SKILL.md

@@ -41,6 +41,10 @@ Independently hash the saved bytes and require equality with `sealedArtifact.art
 
 Portable playback uses either a fully inline `rma2` capsule or compact `rmc1` proof-object append segmentation. An `rmc1` public head is hard-bounded to 4,096 URL characters and commits the complete ordered append sequence that reconstructs the same exact capsule bytes without navigating to a giant textual URL. That bound applies only to the head and never truncates or limits lawful sealed truth. Consumers must verify segment order, length, digest, Merkle root, Fibonacci checkpoints, complete capsule digest, enclosing artifact digest, and the sealed proof object before rendering a browser-local media URL. Append transport, storage, SDK, MCP, server, and UI projections remain subordinate to the enclosing sealed artifact.
 
+`createReceizMaterialSourceFamily` turns the existing material composite into independently copyable content-bearing manifest and segment URLs. `createReceizClosedMaterialPresentationUrl` can fold the complete family into one long held presentation URL. `openVerifiedReceizMaterialUrl(headUrl, { sourceUrls })` reconstructs from the complete held family with zero remote fetches, then verifies the enclosing artifact before payload projection. Presenting any held source field commits the caller to held reconstruction: incomplete or conflicting families fail closed instead of falling back to a weaker remote source.
+
+For causal data, `openReceizSourceCarriedReplayFamilyV124` verifies exact sealed replay-segment artifacts, orders them by predecessor, preserves all heads, and computes a deterministic non-authoritative family set digest. Use `diffReceizSourceCarriedReplayFamiliesV124`, `mergeReceizSourceCarriedReplayFamiliesV124`, and `projectReceizSourceCarriedReplayBranchesV124` for transfer, convergence, and rebuildable projections. MCP parity is `receiz_source_carried_replay_open` over trusted-host `sealedSourceArtifactRefs`; exact source bytes never enter its result or persistence.
+
 ## Twelve-step artifact workflow
 
 1. Label the input bytes as `payload`; never call them an artifact.
@@ -171,6 +175,22 @@ Request: Bind payloads to the enclosing sealed artifact, preserve provenance and
 
 Return a written implementation contract and read-only plan first. Execute only allowed commands after exact confirmation, then report registry digest, laws, authority, tests, independent evidence, release-lock status, and the exact remaining boundary.
 
+
+
+
+
+<!-- receiz-source-carried-law:start -->
+## Source-carried conversation and material law
+
+The enclosing sealed proof object is **enclosing-proof authority**. A source token, manifest digest, segment digest, family digest, local-custody marker, SDK projection, or MCP result can verify or coordinate a deterministic projection, but none may replace the enclosing proof object.
+
+Conversation participation uses **Receiz-ID participant binding** to exact subject and access-key heads. There is **no fixed total member or history cap**: canonical history remains complete, while retrieval, reasoning, epoch grants, and MCP output use bounded windows. Revoking a participant requires **epoch rotation on revoke** before later private messages. Use **bounded grant operations** through `planReceizConversationEpochGrantBatchesV1` or `receiz_conversation_epoch_grants_plan`; the clear epoch secret stays in trusted-host custody and never enters model output.
+
+Reconstruction is **held-first reconstruction**. Open complete locally held conversation sources with `openReceizConversationSourceFamilyV1` or `receiz_conversation_source_family_open`. Open complete locally held media sources with `openReceizMaterialSourceParts`, then project raw RMA3 material with `createReceizRawMaterialCapsuleBlobFromSourceParts`, or inspect bounded coordinates through `receiz_material_source_parts_open`. Complete custody is **no-fetch complete custody**: once every exact source is held, verification and reconstruction must perform zero network fetches and must not consult a database, session, or server before known-truth use.
+
+Legacy and whole-payload-SHA-only media preserves the **whole-artifact-required fallback**. Newly sealed audio/video may carry a compact `receiz.material.progressive-ranges.v1` commitment inside the enclosing Signature-V4 proof. Build and validate its carried ledger with `buildReceizMaterialProgressiveLedger`, `createReceizMaterialProgressiveCommitment`, and the source-family reader; accept it only when the full ledger recomputes the signed root, then verify every requested range digest before projection. Never infer range authority from unsigned offsets, container metadata, transport segment hashes, a manifest, or an MCP result. `receiz_material_source_parts_open` may expose only the compact progressive summary among **non-authoritative MCP projections**. Material bytes, content-bearing locators, exact conversation sources, clear message bodies, and epoch secrets stay outside model output.
+<!-- receiz-source-carried-law:end -->
+
 ## v120 artifact-derived authority
 
 Engineers remain free to build whatever they choose, but conforming Receiz receivers recognize authority only when every authority-bearing value is provably derived from independently verified artifact truth. Custom JavaScript objects, callbacks, normalized histories, local receipts, server rows, sessions, MCP memory, and AI explanations remain application data or inspection material; their shape never creates Receiz authority.
@@ -180,3 +200,12 @@ Admission begins from runtime-custodied verification of the exact enclosing arti
 Deterministic plan identity and unique execution-attempt identity are separate. MCP may reuse a confirmation digest only while the identical attempt is actively pending; committed and failed attempts are terminal and require a fresh confirmation. Expected authority failures are structured, immutable, machine-readable, and report zero writes.
 
 Historical sealed proof objects remain exact-byte verifiable evidence. Historical runtime admissions, histories, actors, capabilities, plans, candidates, stores, or confirmations cannot authorize a current v121 receiver; exact bytes crossing a process require `reverify-exact-bytes`, followed by current profile admission and `same-runtime-custody` through plan, capability, seal, stage, independent byte resolution, atomic named-domain acceptance, and report-only receipt.
+
+<!-- receiz-v124.1-capability-map:start -->
+## V124.1 callable capability bindings
+
+- **source-carried-replay.** Open, compare, merge, and project every verified replay branch from exact sealed sources without a database or last-write-wins collapse. SDK: `openReceizSourceCarriedReplayFamilyV124`, `diffReceizSourceCarriedReplayFamiliesV124`, `mergeReceizSourceCarriedReplayFamiliesV124`, `projectReceizSourceCarriedReplayBranchesV124`. MCP: `receiz_source_carried_replay_open`. Boundary: Each sealed replay source is verified independently. Family and branch projections coordinate exact admitted sources but never replace the enclosing proof objects.
+- **receiz-id-conversation.** Compose direct or unlimited invited-member conversations from complete causal history, bounded retrieval windows, encrypted epoch grants, and exact Receiz-ID participant bindings. SDK: `parseReceizConversationParticipantBindingV1`, `createReceizConversationEventV1`, `parseReceizConversationEventV1`, `reduceReceizConversationEventsV1`, `openReceizConversationSourceFamilyV1`, `createReceizConversationEpochSecretV1`, `planReceizConversationEpochGrantBatchesV1`, `openReceizConversationEpochGrantV1`, `encryptReceizConversationMessageV1`, `decryptReceizConversationMessageV1`. MCP: `receiz_conversation_source_family_open`, `receiz_conversation_epoch_grants_plan`. Boundary: Receiz identity bindings and sealed conversation events remain authority. MCP returns safe coordinates and encrypted grant envelopes only; clear messages and epoch secrets stay in trusted-host custody.
+- **held-material-reconstruction.** Build, publish, hold, reopen, and reconstruct inline RMA2 or segmented RMC1/RMC2 with raw RMA3 projection while verifying the enclosing artifact before native media use. SDK: `buildReceizMaterialCompositeTransport`, `publishReceizMaterialCompositeTransport`, `resolveReceizMaterialCompositeTransport`, `createReceizMaterialSourceFamily`, `createReceizClosedMaterialPresentationUrl`, `openReceizMaterialSourceParts`, `createReceizRawMaterialCapsuleBlobFromSourceParts`, `decodeReceizRawMaterialCapsuleBytes`, `resolveReceizMaterialCompositeFromSources`, `openVerifiedReceizMaterialUrl`. MCP: `receiz_material_source_parts_open`, `receiz_material_url_open`. Boundary: Transport segments, locators, manifests, object URLs, and storage are projections only. Native bytes are admitted only beneath verification of the enclosing sealed artifact.
+- **progressive-range-playback.** Start verified first-frame playback from signed range commitments while remaining ranges settle behind the already playing media. SDK: `buildReceizMaterialProgressiveLedger`, `createReceizMaterialProgressiveCommitment`, `coerceReceizMaterialProgressiveLedger`, `coerceReceizMaterialProgressiveCommitment`, `openReceizMaterialSourceRangeReader`. MCP: `receiz_material_source_parts_open`. Boundary: Only a progressive ledger whose complete root is carried by the enclosing Signature-V4 proof can authorize range projection. Unsigned offsets, container metadata, or transport segments cannot.
+<!-- receiz-v124.1-capability-map:end -->

package/receiz-portable-artifacts/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-portable-artifacts",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -71,7 +71,11 @@
     "receiz_artifact_verify",
     "receiz_artifact_append_plan",
     "receiz_artifact_transition_seal_and_stage",
-    "receiz_artifact_transition_commit"
+    "receiz_artifact_transition_commit",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open"
   ],
   "forbiddenOperations": [
     "direct-state-write",
@@ -1323,6 +1327,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1420,6 +1428,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1514,5 +1526,11 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
+  ],
+  "v124_1CapabilityIds": [
+    "source-carried-replay",
+    "receiz-id-conversation",
+    "held-material-reconstruction",
+    "progressive-range-playback"
   ]
 }

package/receiz-portable-continuity/SKILL.md

@@ -92,3 +92,10 @@ Historical sealed proof objects remain exact-byte verifiable evidence. Historica
 Use canonical head → entire proof history → bounded index retrieval → exact primary-object resolution → reasoning → provenance. The 96-object window is working context, never history truncation. AI speech and performance remain non-authoritative. Consequential actions require typed deterministic command admission; meetings, relationships, trades, gifts, and battles require atomic multi-subject transactions. Autonomous execution requires a current digest-bound mandate at lease time. Bearer transfer preserves identity, full history, memory policy, inventory disposition, and unknown namespace bytes while immediately revoking former-owner authority.
 
 Concrete v120 evidence must include: a creature speaking from exact long-form proof memory; absent-owner exploration inside a mandate; a mutual relationship; a bounded autonomous trade; an atomic battle; exact device restoration; queued-action revocation; partition convergence without history replacement; rejection of an AI-invented event; and cross-application subject continuity.
+
+<!-- receiz-v124.1-capability-map:start -->
+## V124.1 callable capability bindings
+
+- **receiz-id-conversation.** Compose direct or unlimited invited-member conversations from complete causal history, bounded retrieval windows, encrypted epoch grants, and exact Receiz-ID participant bindings. SDK: `parseReceizConversationParticipantBindingV1`, `createReceizConversationEventV1`, `parseReceizConversationEventV1`, `reduceReceizConversationEventsV1`, `openReceizConversationSourceFamilyV1`, `createReceizConversationEpochSecretV1`, `planReceizConversationEpochGrantBatchesV1`, `openReceizConversationEpochGrantV1`, `encryptReceizConversationMessageV1`, `decryptReceizConversationMessageV1`. MCP: `receiz_conversation_source_family_open`, `receiz_conversation_epoch_grants_plan`. Boundary: Receiz identity bindings and sealed conversation events remain authority. MCP returns safe coordinates and encrypted grant envelopes only; clear messages and epoch secrets stay in trusted-host custody.
+- **portable-account-continuity.** Seal, verify, and immediately project complete account truth—including profile, showcase, wallet, market positions/history, media, and proof history—without waiting on a server or database. SDK: `appendReceizIdentityPortableState`, `verifyReceizIdentityPortableStateProof`, `projectReceizIdentityAccount`. MCP: none: private SDK boundary. Boundary: The verified Identity Seal, Identity Record, or Receiz Key carries account truth. Private portable state is not exposed through MCP; server synchronization may append verified additions only after immediate local projection.
+<!-- receiz-v124.1-capability-map:end -->

package/receiz-portable-continuity/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-portable-continuity",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1259,6 +1259,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1356,6 +1360,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1450,5 +1458,9 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
+  ],
+  "v124_1CapabilityIds": [
+    "receiz-id-conversation",
+    "portable-account-continuity"
   ]
 }

package/receiz-proof-authority/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": "receiz.ai-skill-contract.v124",
   "name": "receiz-proof-authority",
-  "version": "124.0.2",
+  "version": "124.1.0",
   "requires": {
     "sdk": ">=124.0.0 <125.0.0",
     "mcp": ">=124.0.0 <125.0.0",
@@ -1214,6 +1214,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed"
@@ -1311,6 +1315,10 @@
     "receiz_v124_domain_verified_private_additions",
     "receiz_v124_domain_replay_proof_object_export",
     "receiz_v124_domain_replay_proof_object_restore",
+    "receiz_source_carried_replay_open",
+    "receiz_conversation_source_family_open",
+    "receiz_conversation_epoch_grants_plan",
+    "receiz_material_source_parts_open",
     "receiz_v124_subject_namespaces_resolve",
     "receiz_v124_identity_public_recipient_resolve",
     "receiz_v124_source_publish_sealed",
@@ -1405,5 +1413,6 @@
     "receiz_v122_multi_world_execute",
     "receiz_v122_value_plan_settlement",
     "receiz_v122_value_plan_reserve"
-  ]
+  ],
+  "v124_1CapabilityIds": []
 }

package/receiz-proof-media/SKILL.md

@@ -49,6 +49,8 @@ Store and render the known verified artifact immediately when available. Do not
 
 Content-bearing Receiz proof URLs carry exact sealed material either fully inline as `#material=rma2:...` or through a compact `#material=rmc1:...` proof-object append-segmentation head. Open both forms with `openVerifiedReceizMaterialUrl(url)`. Inline capsules open fully offline. Composite heads are hard-bounded to 4,096 URL characters and resolve and verify their ordered append segments, reconstruct the exact original capsule locally, then verify the enclosing sealed proof object with the pinned canonical verifier before exposing native payload bytes. The 4,096-character boundary applies only to the public head: it never truncates the artifact or its append segments and is never a truth-size limit. Render the returned `payloadBytes` according to `playableKind` and `payloadMimeType`; `createReceizPlayableMaterialObjectUrl(verified)` creates a browser-local image, audio, video, PDF, text, or download URL. Append transport never outranks the sealed proof object.
 
+For large held material, create a content-bearing source family with `createReceizMaterialSourceFamily({ proofUrl, transport })`. Carry its head URL plus manifest and segment URLs independently, or use `createReceizClosedMaterialPresentationUrl(family)` when one long copied URL is desired. Reopen whole-artifact paths with `openVerifiedReceizMaterialUrl(headUrl, { sourceUrls })`. For signed progressive playback, keep only `createReceizMaterialProgressiveCommitment(ledger)` inside the Signature-V4 proof and carry the complete ledger in the source manifest. `openReceizMaterialSourceRangeReader` keeps source segments lazy; its ledger must recompute the signed commitment before any requested range digest is verified and projected. Once any held source fields are presented, incomplete, conflicting, cross-package, ledger-root-mismatched, or digest-invalid input fails closed and must not fall through to remote transport. This enables browser-local playback from exact held bytes without a database, media CDN, or storage authority.
+
 Developers may carry the same `#material` coordinate on their own domain and render it there. The external route is a presentation wrapper only: reconstruct the inline capsule or committed proof-object append sequence, verify the enclosing artifact locally, render the returned exact payload, and expose `canonicalReceizUrl` as the direct link back to the Receiz public proof surface. Do not let an upload, database row, media CDN, SDK, or server response become proof authority.
 
 For identity artwork and sigil projection, use `receizKaiMomentFromSealedPulse(accountCreationPulse)`. The sealed account-creation pulse is creation authority. Device clock, browser clock, process uptime, SDK state, session state, device-enrollment time, and PBI evidence cannot replace or reinterpret it. `receizKaiNow()` is only the live freshness coordinate for short-lived challenges and must never be used to reconstruct an existing identity glyph.
@@ -67,12 +69,28 @@ Show the source media, artifact filename, proof-object type, public URL if one i
 
 ## MCP parity
 
-Use `receiz_material_url_open` to verify and reconstruct a content-bearing proof URL locally. Set `includePayloadBytes: true` only when the agent host needs exact base64url payload bytes for rendering or playback. `rma2` needs no transport lookup. `rmc1` resolves only committed proof-object append segments, reconstructs exact capsule bytes locally, and rejects substitutions before canonical proof verification. Use `receiz_sealed_kai_moment` with the verified account-creation pulse when rendering identity artwork; never use the live-clock tool for an existing proof object. Neither media form may use device time to re-project an existing proof object. Use the SDK artifact-custody workflow for media Record -> Seal; MCP does not introduce a parallel media authority or a direct profile-mutation adapter. Project an already verified media URL through the canonical SDK `receiz.profile.update(profile)` operation and require the same-UID result. Never substitute an unrelated MCP tool or a model-carried projection for the sealed media proof object.
+Use `receiz_material_url_open` to verify and reconstruct a content-bearing proof URL locally. Pass the complete `sourceUrls` family when the host already holds it; those URLs are forwarded once to the local opener and are never persisted by MCP. Set `includePayloadBytes: true` only when the agent host needs exact base64url payload bytes for rendering or playback. `rma2` needs no transport lookup. `rmc1` with held source fields reconstructs locally and fails closed; remote segment resolution is allowed only when no held source fields exist. Use `receiz_material_source_parts_open` to inspect bounded verified source coordinates and the compact progressive commitment summary without returning bytes or locators. Progressive byte reads remain in trusted host/browser custody through the SDK, not model output. Use `receiz_source_carried_replay_open` separately for sealed causal replay sources associated with media provenance or conversation history; it does not open media bytes. Use `receiz_sealed_kai_moment` with the verified account-creation pulse when rendering identity artwork; never use the live-clock tool for an existing proof object. Neither media form may use device time to re-project an existing proof object. Use the SDK artifact-custody workflow for media Record -> Seal; MCP does not introduce a parallel media authority or a direct profile-mutation adapter. Project an already verified media URL through the canonical SDK `receiz.profile.update(profile)` operation and require the same-UID result. Never substitute an unrelated MCP tool or a model-carried projection for the sealed media proof object.
 
 ## Emulator fixture
 
 Run `profile-media-atomic-rollback`. Require no partial profile projection after injected failure while preserving any independently completed sealed media proof object.
 
+
+
+
+
+<!-- receiz-source-carried-law:start -->
+## Source-carried conversation and material law
+
+The enclosing sealed proof object is **enclosing-proof authority**. A source token, manifest digest, segment digest, family digest, local-custody marker, SDK projection, or MCP result can verify or coordinate a deterministic projection, but none may replace the enclosing proof object.
+
+Conversation participation uses **Receiz-ID participant binding** to exact subject and access-key heads. There is **no fixed total member or history cap**: canonical history remains complete, while retrieval, reasoning, epoch grants, and MCP output use bounded windows. Revoking a participant requires **epoch rotation on revoke** before later private messages. Use **bounded grant operations** through `planReceizConversationEpochGrantBatchesV1` or `receiz_conversation_epoch_grants_plan`; the clear epoch secret stays in trusted-host custody and never enters model output.
+
+Reconstruction is **held-first reconstruction**. Open complete locally held conversation sources with `openReceizConversationSourceFamilyV1` or `receiz_conversation_source_family_open`. Open complete locally held media sources with `openReceizMaterialSourceParts`, then project raw RMA3 material with `createReceizRawMaterialCapsuleBlobFromSourceParts`, or inspect bounded coordinates through `receiz_material_source_parts_open`. Complete custody is **no-fetch complete custody**: once every exact source is held, verification and reconstruction must perform zero network fetches and must not consult a database, session, or server before known-truth use.
+
+Legacy and whole-payload-SHA-only media preserves the **whole-artifact-required fallback**. Newly sealed audio/video may carry a compact `receiz.material.progressive-ranges.v1` commitment inside the enclosing Signature-V4 proof. Build and validate its carried ledger with `buildReceizMaterialProgressiveLedger`, `createReceizMaterialProgressiveCommitment`, and the source-family reader; accept it only when the full ledger recomputes the signed root, then verify every requested range digest before projection. Never infer range authority from unsigned offsets, container metadata, transport segment hashes, a manifest, or an MCP result. `receiz_material_source_parts_open` may expose only the compact progressive summary among **non-authoritative MCP projections**. Material bytes, content-bearing locators, exact conversation sources, clear message bodies, and epoch secrets stay outside model output.
+<!-- receiz-source-carried-law:end -->
+
 ## v120 artifact-derived authority
 
 Engineers remain free to build whatever they choose, but conforming Receiz receivers recognize authority only when every authority-bearing value is provably derived from independently verified artifact truth. Custom JavaScript objects, callbacks, normalized histories, local receipts, server rows, sessions, MCP memory, and AI explanations remain application data or inspection material; their shape never creates Receiz authority.
@@ -82,3 +100,10 @@ Admission begins from runtime-custodied verification of the exact enclosing arti
 Deterministic plan identity and unique execution-attempt identity are separate. MCP may reuse a confirmation digest only while the identical attempt is actively pending; committed and failed attempts are terminal and require a fresh confirmation. Expected authority failures are structured, immutable, machine-readable, and report zero writes.
 
 Historical sealed proof objects remain exact-byte verifiable evidence. Historical runtime admissions, histories, actors, capabilities, plans, candidates, stores, or confirmations cannot authorize a current v121 receiver; exact bytes crossing a process require `reverify-exact-bytes`, followed by current profile admission and `same-runtime-custody` through plan, capability, seal, stage, independent byte resolution, atomic named-domain acceptance, and report-only receipt.
+
+<!-- receiz-v124.1-capability-map:start -->
+## V124.1 callable capability bindings
+
+- **held-material-reconstruction.** Build, publish, hold, reopen, and reconstruct inline RMA2 or segmented RMC1/RMC2 with raw RMA3 projection while verifying the enclosing artifact before native media use. SDK: `buildReceizMaterialCompositeTransport`, `publishReceizMaterialCompositeTransport`, `resolveReceizMaterialCompositeTransport`, `createReceizMaterialSourceFamily`, `createReceizClosedMaterialPresentationUrl`, `openReceizMaterialSourceParts`, `createReceizRawMaterialCapsuleBlobFromSourceParts`, `decodeReceizRawMaterialCapsuleBytes`, `resolveReceizMaterialCompositeFromSources`, `openVerifiedReceizMaterialUrl`. MCP: `receiz_material_source_parts_open`, `receiz_material_url_open`. Boundary: Transport segments, locators, manifests, object URLs, and storage are projections only. Native bytes are admitted only beneath verification of the enclosing sealed artifact.
+- **progressive-range-playback.** Start verified first-frame playback from signed range commitments while remaining ranges settle behind the already playing media. SDK: `buildReceizMaterialProgressiveLedger`, `createReceizMaterialProgressiveCommitment`, `coerceReceizMaterialProgressiveLedger`, `coerceReceizMaterialProgressiveCommitment`, `openReceizMaterialSourceRangeReader`. MCP: `receiz_material_source_parts_open`. Boundary: Only a progressive ledger whose complete root is carried by the enclosing Signature-V4 proof can authorize range projection. Unsigned offsets, container metadata, or transport segments cannot.
+<!-- receiz-v124.1-capability-map:end -->