@receiz/ai-skills 113.5.0 → 115.0.0

package/README.md

@@ -1,8 +1,16 @@
 # Receiz AI Skills
 
-The `113.5.0` package is a registry-bound operating-contract distribution beneath Receiz proof authority. AI instructions, MCP confirmations, JSON objects, database rows, staging references, and receipts never become proof or runtime authority.
+The `115.0.0` package is a registry-bound operating-contract distribution beneath Receiz proof authority. AI instructions, MCP confirmations, JSON objects, database rows, staging references, and receipts never become proof or runtime authority.
 
-## V113 artifact authority chain
+## V115 artifact authority chain
+
+V115 teaches two additive proof-object laws:
+`receiz.native_capture.v1` binds exact bytes from Receiz's dedicated camera
+ceremony, and `receiz.pbi.proof-object-authorship.v1` appends verified PBI
+authorship to an already verified predecessor. Signing is unavailable before
+canonical verification. Multi-signer history remains ordered forever, local
+settlement completes before optional global publication, and authorship never
+changes ownership, media bytes, capture provenance, or prior proof.
 
 The exact current sequence is: verify exact bytes → profile admission → verified actor/history → transition → plan/domain/effects/idempotency → plan-bound capability → seal → durable stage → independent byte resolution → atomic named-domain acceptance → report-only receipt.
 
@@ -10,16 +18,16 @@ Exact bytes cross a process only as bytes and require `reverify-exact-bytes`. Ve
 
 The single current MCP artifact inventory contains nine tools: `receiz_artifact_verify`, `receiz_artifact_admit`, `receiz_artifact_append_plan`, `receiz_artifact_transition_seal_and_stage`, `receiz_artifact_transition_commit`, `receiz_artifact_global_resolve`, `receiz_artifact_reconcile_plan`, `receiz_artifact_reconcile_stage`, and `receiz_artifact_reconcile_commit`. The first five are also the explicitly historical v112 compatibility inventory, not a second current surface. A sealed candidate is a proof object but not the accepted head. Stage writes no head and its reference is non-authoritative. Commit resolves and reverifies staged bytes before atomic named-domain acceptance. `COMMIT_DOMAIN_MISMATCH` is distinct from same-domain `IDEMPOTENCY_CONFLICT`; registry-derived effects stay outside the portable transition digest; unknown namespaces remain byte-preserved.
 
-`client.admission.browserStore` is durable admission coordination only: it stores no proof object or sealed artifact bytes and never blocks known-artifact first paint. V113 production reconciliation uses the provider-neutral `client.coordination` rail and never exposes Supabase mechanics. Receiz-generated files retain declared ownership, while `receiz.extensions.ts` is developer-owned and must never be overwritten.
+`client.admission.browserStore` is durable admission coordination only: it stores no proof object or sealed artifact bytes and never blocks known-artifact first paint. V115 production reconciliation preserves the provider-neutral `client.coordination` rail and never exposes Supabase mechanics. Receiz-generated files retain declared ownership, while `receiz.extensions.ts` is developer-owned and must never be overwritten.
 
 `receiz-build-production-system` remains the constitutional orchestration skill for substantial
 Receiz applications. Fifteen focused constitutional skills supply architecture,
 domain, law, command, authority, replay, offline, causal, artifact, migration,
 performance, observability, testing, and release contracts. The earlier nine
 domain skill names remain packaged for compatibility. Seven operation skill names first introduced in obsolete-versioned now
-describe current v113 outcomes for identity profiles, portable continuity, bearer ownership, offline transport,
+describe current v115 outcomes for identity profiles, portable continuity, bearer ownership, offline transport,
 proof media, cross-app state, and admission evidence. Their retired obsolete-versioned mechanisms are not active defaults.
-One dedicated `receiz-global-reconciliation` skill governs accepted-head resolution, verified offline reconciliation, structural divergence, first paint, indeterminate recovery, and effects. Every current manifest uses package version `113.5.0`, requires SDK/MCP `>=113.0.0 <114.0.0`, and binds ruleset `113.0.0` to registry digest `4c4aa85f9785d205dcf7e4e5109837a83f8c3bf8e166130ae7e87353f299c637` and operation-matrix digest `091ab9e6b3acb05283510a19754e53c637dbd96b47b499a524dc44c34f8e783b` from SDK source.
+One dedicated `receiz-global-reconciliation` skill governs accepted-head resolution, verified offline reconciliation, structural divergence, first paint, indeterminate recovery, and effects. Every current manifest uses package version `115.0.0`, requires SDK/MCP `>=115.0.0 <116.0.0`, and binds ruleset `115.0.0` to registry digest `69b553d5ff8c1287ff33bfb2f3197ea3ec9bccf6a6ce9d3c47107d0819d3f246` and operation-matrix digest `0393000708aada33c9f8bbcc4b98c9aa202a9d37036e67e09fc34c6815f77c8a` from SDK source.
 
 This package teaches AI agents how to understand, verify, build with, and operate Receiz from the existing repository surfaces.
 
@@ -39,9 +47,9 @@ Agents may acquire scoped delegated access through the official Receiz Connect/O
 
 ## How Agents Should Use This Package
 
-Start with `receiz-build-production-system` when work spans multiple constitutional domains and `receiz-global-reconciliation` for named-domain coordination. Machine-readable manifests require the exact active canonical v113 registry and operation-matrix digests, command-only mutation, independent verification, MCP conformance, and a passing release lock. Use a focused operation skill for SDK/MCP implementation and a constitutional skill for broader system law. Stable obsolete-versioned wire schemas remain available only through the explicit historical `@receiz/sdk/obsolete-versioned` package entry; current skills never teach their key, head, receipt, reconcile, or signed-command mechanics as a current outcome.
+Start with `receiz-build-production-system` when work spans multiple constitutional domains and `receiz-global-reconciliation` for named-domain coordination. Machine-readable manifests require the exact active canonical v115 registry and operation-matrix digests, command-only mutation, independent verification, MCP conformance, and a passing release lock. Use a focused operation skill for SDK/MCP implementation and a constitutional skill for broader system law. Stable obsolete-versioned wire schemas remain available only through the explicit historical `@receiz/sdk/obsolete-versioned` package entry; current skills never teach their key, head, receipt, reconcile, or signed-command mechanics as a current outcome.
 
-The v113 operation skills are executable contracts. Current profile work uses the neutral authenticated same-UID profile operation. Current bearer ownership accepts a complete verified artifact, derives prior ownership from carried proof, and returns a native Record -> Seal artifact. Proof media uses the same native artifact custody and projects only a verified URL beneath it. These outcomes have no active identity-key, caller-head, claim-key, or receipt prerequisite. MCP calls the same SDK outcomes and never creates a parallel authority.
+The v115 operation skills are executable contracts. Current profile work uses the neutral authenticated same-UID profile operation. Current bearer ownership accepts a complete verified artifact, derives prior ownership from carried proof, and returns a native Record -> Seal artifact. Proof media uses the same native artifact custody and projects only a verified URL beneath it. These outcomes have no active identity-key, caller-head, claim-key, or receipt prerequisite. MCP calls the same SDK outcomes and never creates a parallel authority.
 
 Stable obsolete-versioned schema names and their head/receipt mechanics remain explicitly historical compatibility, not the active/default profile, bearer, or proof-media contract.
 

package/SKILLS.md

@@ -1,6 +1,13 @@
-# Receiz AI Skills v113
+# Receiz AI Skills v115
 
-This package ships 32 skills, 26 machine-readable manifests, and 23 OpenAI agent prompts. Every current manifest binds registry digest `4c4aa85f9785d205dcf7e4e5109837a83f8c3bf8e166130ae7e87353f299c637` and application-operation-matrix digest `091ab9e6b3acb05283510a19754e53c637dbd96b47b499a524dc44c34f8e783b` from the v113 SDK source.
+V115 preserves sealed proof/object authority and adds
+`receiz.native_capture.v1` plus
+`receiz.pbi.proof-object-authorship.v1`. Native Capture binds dedicated camera
+ceremony bytes. PBI authorship requires canonical predecessor verification,
+appends ordered history, settles locally before optional publication, and does
+not transfer ownership.
+
+This package ships 32 skills, 26 machine-readable manifests, and 23 OpenAI agent prompts. Every current manifest binds registry digest `69b553d5ff8c1287ff33bfb2f3197ea3ec9bccf6a6ce9d3c47107d0819d3f246` and application-operation-matrix digest `0393000708aada33c9f8bbcc4b98c9aa202a9d37036e67e09fc34c6815f77c8a` from the v115 SDK source.
 
 ## Current MCP artifact inventory: nine tools
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@receiz/ai-skills",
-  "version": "113.5.0",
+  "version": "115.0.0",
   "description": "Registry-bound Receiz AI operating contracts beneath proof authority for SDK and MCP agents.",
   "type": "module",
   "files": [

package/receiz-app-builder-skill/SKILL.md

@@ -8,7 +8,7 @@ description: Use when starting, integrating, upgrading, diagnosing, or repairing
 Build and upgrade Receiz applications from one typed contract. The compiler is
 integration tooling beneath Receiz proof truth; inspection is not verification.
 
-## Binding v113 artifact law
+## Binding v115 artifact law
 
 A Receiz artifact is the exact byte sequence returned by native Record -> Seal. The inner payload is never an acceptable substitute.
 
@@ -21,7 +21,7 @@ Label every byte sequence generated or consumed by the application:
 
 ## Required SDK artifact workflow
 
-The exact v113 application-operation inventory is `receiz.artifact.verify`, `receiz.artifact.admit`, `receiz.artifact.append.plan`, `receiz.identity.capability.sign`, `receiz.artifact.transition.seal`, `receiz.artifact.transition.stage`, `receiz.artifact.transition.commit`, `receiz.admission.command.execute`, `receiz.public-proof.projection.locate`, `receiz.artifact.global.resolve`, and `receiz.artifact.offline.reconcile`. These identifiers describe the application authority matrix; they do not create authority.
+The exact v115 application-operation inventory is `receiz.artifact.verify`, `receiz.artifact.admit`, `receiz.artifact.append.plan`, `receiz.identity.capability.sign`, `receiz.artifact.transition.seal`, `receiz.artifact.transition.stage`, `receiz.artifact.transition.commit`, `receiz.admission.command.execute`, `receiz.public-proof.projection.locate`, `receiz.artifact.global.resolve`, `receiz.artifact.offline.reconcile`, `receiz.profile-showcase.genesis.plan`, `receiz.profile-showcase.append.plan`, `receiz.economy-showcase.genesis.plan`, `receiz.economy-showcase.append.plan`, and `receiz.economy-showcase.merge.plan`. These identifiers describe the application authority matrix; they do not create authority.
 
 ```ts
 const payload = { bytes: applicationPayload, mimeType: applicationMimeType };
@@ -41,7 +41,7 @@ Independently hash the saved bytes and require equality with `sealedArtifact.art
 ## Twelve-step artifact workflow
 
 1. Label the input bytes as `payload`; never call them an artifact.
-2. Load the active canonical v113 registry and `ARTIFACT-001` through `ARTIFACT-030`.
+2. Load the active canonical v115 registry and `ARTIFACT-001` through `ARTIFACT-030`.
 3. Call `receiz.assets.createProofObject` so Receiz.com performs native Record -> Seal.
 4. Require an SDK-issued `receiz.native-record-seal`; failure returns no artifact and no payload fallback.
 5. Require complete enclosing-artifact verification, integrity, Signature V4, owner, claim, verify path, and payload binding.
@@ -207,7 +207,7 @@ Resources:
 - [Generated-file repair](resources/generated-file-repair.md)
 - [Upgrade rules](resources/upgrade-rules.md)
 
-## v113 unified admission and recovery
+## v115 unified admission and recovery
 
 First call `verifyReceizArtifact(file)`. Then call `receiz.artifacts.admit(verification, profileOptions)` in the same runtime. Admission reports profile membership and primitive-specific assessments; it does not authorize an operation. Verified actor evidence exists only after identity-profile admission, never from a caller constraint or structural object.
 
@@ -233,7 +233,7 @@ Operation identity:
 Atomic commit result:
 ```
 
-## v113 artifact-derived authority
+## v115 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.
 
@@ -241,4 +241,4 @@ 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 v113 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.
+Historical sealed proof objects remain exact-byte verifiable evidence. Historical runtime admissions, histories, actors, capabilities, plans, candidates, stores, or confirmations cannot authorize a current v115 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.

package/receiz-app-builder-skill/manifest.json

@@ -1,13 +1,13 @@
 {
-  "schema": "receiz.ai-skill-contract.v113",
+  "schema": "receiz.ai-skill-contract.v115",
   "name": "receiz-app-builder-skill",
-  "version": "113.5.0",
+  "version": "115.0.0",
   "requires": {
-    "sdk": ">=113.0.0 <114.0.0",
-    "mcp": ">=113.0.0 <114.0.0",
-    "ruleset": "113.0.0",
-    "registryDigest": "4c4aa85f9785d205dcf7e4e5109837a83f8c3bf8e166130ae7e87353f299c637",
-    "operationMatrixDigest": "091ab9e6b3acb05283510a19754e53c637dbd96b47b499a524dc44c34f8e783b"
+    "sdk": ">=115.0.0 <116.0.0",
+    "mcp": ">=115.0.0 <116.0.0",
+    "ruleset": "115.0.0",
+    "registryDigest": "69b553d5ff8c1287ff33bfb2f3197ea3ec9bccf6a6ce9d3c47107d0819d3f246",
+    "operationMatrixDigest": "0393000708aada33c9f8bbcc4b98c9aa202a9d37036e67e09fc34c6815f77c8a"
   },
   "artifactLawVersion": "113.0.0",
   "artifactLaws": [
@@ -211,7 +211,7 @@
       "outputAuthority": "verified-artifact-runtime",
       "processBoundary": "reverify-exact-bytes",
       "namespacePolicy": "not-applicable",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.admit",
@@ -225,7 +225,7 @@
       "outputAuthority": "verified-admission-runtime",
       "processBoundary": "same-runtime-custody",
       "namespacePolicy": "not-applicable",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.append.plan",
@@ -247,7 +247,7 @@
       "outputAuthority": "sdk-plan-runtime",
       "processBoundary": "same-runtime-custody",
       "namespacePolicy": "preserve-all-non-target",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "identity.capability.sign",
@@ -260,7 +260,7 @@
       "outputAuthority": "signed-capability-claim-not-yet-verified",
       "processBoundary": "local-identity-key-custody",
       "namespacePolicy": "not-applicable",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.transition.seal",
@@ -277,7 +277,7 @@
       "outputAuthority": "sealed-candidate-proof-object-not-accepted-head",
       "processBoundary": "same-runtime-custody",
       "namespacePolicy": "preserve-all-non-target",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.transition.stage",
@@ -294,7 +294,7 @@
       "outputAuthority": "staged-candidate-locator-non-authoritative",
       "processBoundary": "same-runtime-custody",
       "namespacePolicy": "preserve-all-non-target",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.transition.commit",
@@ -313,7 +313,7 @@
       "outputAuthority": "accepted-artifact-history-with-report-only-receipt",
       "processBoundary": "same-runtime-custody",
       "namespacePolicy": "preserve-all-non-target",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "admission.command.execute",
@@ -334,7 +334,7 @@
       "outputAuthority": "admission-receipt-non-authoritative",
       "processBoundary": "same-runtime-custody",
       "namespacePolicy": "not-applicable",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "public-proof.projection.locate",
@@ -348,7 +348,7 @@
       "outputAuthority": "exact-artifact-bytes-not-yet-verified",
       "processBoundary": "projection-only",
       "namespacePolicy": "not-applicable",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.global.resolve",
@@ -364,7 +364,7 @@
       "outputAuthority": "exact-artifact-bytes-not-yet-verified",
       "processBoundary": "reverify-exact-bytes",
       "namespacePolicy": "not-applicable",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     },
     {
       "operation": "artifact.offline.reconcile",
@@ -387,7 +387,136 @@
       "outputAuthority": "accepted-artifact-history-with-report-only-receipt",
       "processBoundary": "reverify-exact-bytes",
       "namespacePolicy": "preserve-all-non-target",
-      "compatibleSdkRange": ">=113.0.0 <114.0.0"
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
+    },
+    {
+      "operation": "profile-showcase.genesis.plan",
+      "authorityProfiles": [
+        "artifact-local"
+      ],
+      "inputAuthority": "verified-actor-runtime",
+      "requiredEvidence": [
+        "verified-actor-runtime",
+        "v115-registry-runtime",
+        "v115-operation-matrix-runtime",
+        "literal-artifact-identity",
+        "canonical-genesis-body",
+        "unaccepted-head-expectation",
+        "commit-domain",
+        "idempotency-identity",
+        "sdk-plan-runtime",
+        "verified-capability-runtime",
+        "transition-sealer-runtime"
+      ],
+      "outputAuthority": "sdk-plan-runtime",
+      "processBoundary": "same-runtime-custody",
+      "namespacePolicy": "preserve-all-non-target",
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
+    },
+    {
+      "operation": "profile-showcase.append.plan",
+      "authorityProfiles": [
+        "artifact-local"
+      ],
+      "inputAuthority": "verified-admission-runtime",
+      "requiredEvidence": [
+        "verified-admission-runtime",
+        "verified-history-runtime",
+        "verified-actor-runtime",
+        "v115-registry-runtime",
+        "v115-operation-matrix-runtime",
+        "canonical-event",
+        "expected-head",
+        "commit-domain",
+        "idempotency-identity",
+        "sdk-plan-runtime",
+        "verified-capability-runtime",
+        "transition-sealer-runtime",
+        "conforming-transition-store-runtime"
+      ],
+      "outputAuthority": "sdk-plan-runtime",
+      "processBoundary": "same-runtime-custody",
+      "namespacePolicy": "preserve-all-non-target",
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
+    },
+    {
+      "operation": "economy-showcase.genesis.plan",
+      "authorityProfiles": [
+        "global-shared"
+      ],
+      "inputAuthority": "verified-actor-runtime",
+      "requiredEvidence": [
+        "verified-actor-runtime",
+        "v115-registry-runtime",
+        "v115-operation-matrix-runtime",
+        "literal-artifact-identity",
+        "canonical-genesis-body",
+        "unaccepted-head-expectation",
+        "commit-domain",
+        "idempotency-identity",
+        "sdk-plan-runtime",
+        "verified-capability-runtime",
+        "transition-sealer-runtime"
+      ],
+      "outputAuthority": "sdk-plan-runtime",
+      "processBoundary": "same-runtime-custody",
+      "namespacePolicy": "preserve-all-non-target",
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
+    },
+    {
+      "operation": "economy-showcase.append.plan",
+      "authorityProfiles": [
+        "global-shared"
+      ],
+      "inputAuthority": "verified-admission-runtime",
+      "requiredEvidence": [
+        "verified-admission-runtime",
+        "verified-history-runtime",
+        "verified-actor-runtime",
+        "v115-registry-runtime",
+        "v115-operation-matrix-runtime",
+        "literal-artifact-identity",
+        "canonical-event",
+        "expected-head",
+        "commit-domain",
+        "idempotency-identity",
+        "sdk-plan-runtime",
+        "verified-capability-runtime",
+        "transition-sealer-runtime",
+        "conforming-transition-store-runtime"
+      ],
+      "outputAuthority": "sdk-plan-runtime",
+      "processBoundary": "same-runtime-custody",
+      "namespacePolicy": "preserve-all-non-target",
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
+    },
+    {
+      "operation": "economy-showcase.merge.plan",
+      "authorityProfiles": [
+        "global-shared"
+      ],
+      "inputAuthority": "verified-admission-runtime",
+      "requiredEvidence": [
+        "verified-admission-runtime",
+        "verified-history-runtime",
+        "verified-sibling-heads",
+        "verified-actor-runtime",
+        "v115-registry-runtime",
+        "v115-operation-matrix-runtime",
+        "literal-artifact-identity",
+        "canonical-event",
+        "expected-head",
+        "commit-domain",
+        "idempotency-identity",
+        "sdk-plan-runtime",
+        "verified-capability-runtime",
+        "transition-sealer-runtime",
+        "conforming-transition-store-runtime"
+      ],
+      "outputAuthority": "sdk-plan-runtime",
+      "processBoundary": "same-runtime-custody",
+      "namespacePolicy": "preserve-all-non-target",
+      "compatibleSdkRange": ">=115.0.0 <116.0.0"
     }
   ],
   "currentMcpArtifactTools": [

package/receiz-app-builder-skill/resources/workflow.md

@@ -13,7 +13,7 @@ After every mutation, run the returned verification commands and reinspect.
 The same repository must produce zero changes on the second run.
 Preserve the developer-owned `receiz.extensions.ts` sibling on every run. Finish with `receiz conformance` or `receiz_release_qualify`.
 
-For v113 artifact mutation, use the exact five-tool MCP sequence: `receiz_artifact_verify`, `receiz_artifact_admit`, `receiz_artifact_append_plan`, `receiz_artifact_transition_seal_and_stage`, then `receiz_artifact_transition_commit`. Planning and staging perform zero head writes; commit independently resolves and reverifies staged bytes before atomic named-domain acceptance.
+For v115 artifact mutation, use the exact five-tool MCP sequence: `receiz_artifact_verify`, `receiz_artifact_admit`, `receiz_artifact_append_plan`, `receiz_artifact_transition_seal_and_stage`, then `receiz_artifact_transition_commit`. Planning and staging perform zero head writes; commit independently resolves and reverifies staged bytes before atomic named-domain acceptance.
 
 Do not substitute inspection for verification, publication for settlement, or a
 successful write for proof admission.

package/receiz-architecture/SKILL.md

@@ -10,7 +10,7 @@ Map domains, sources of truth, state machines, dependency direction, and cross-d
 ## Constitutional workflow
 
 1. Inspect the repository and installed SDK version.
-2. Load the active canonical v113 registry and applicable constitutional laws.
+2. Load the active canonical v115 registry and applicable constitutional laws.
 3. Identify every authority boundary affected by the change.
 4. Write the implementation contract before implementation.
 5. Implement canonical changes only through SDK commands.
@@ -51,7 +51,7 @@ Request: Map domains, sources of truth, state machines, dependency direction, an
 
 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.
 
-## v113 artifact-derived authority
+## v115 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.
 
@@ -59,4 +59,4 @@ 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 v113 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.
+Historical sealed proof objects remain exact-byte verifiable evidence. Historical runtime admissions, histories, actors, capabilities, plans, candidates, stores, or confirmations cannot authorize a current v115 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.