@receiz/ai-skills 110.0.0 → 111.0.0

package/receiz-cross-app-state/SKILL.md

@@ -7,7 +7,7 @@ description: Use when carrying verified namespaced account state between Receiz
 
 Continue the same Receiz identity across applications by restoring portable account truth and appending isolated namespaces. Cross-app continuation is an identity primitive, not session sharing.
 
-## Binding v110 artifact law
+## Binding v111 artifact law
 
 A Receiz artifact is the exact byte sequence returned by native Record -> Seal. The inner payload is never an acceptable substitute.
 
@@ -38,7 +38,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 signed v110 registry and `ARTIFACT-001` through `ARTIFACT-010`.
+2. Load the active signed v111 registry and `ARTIFACT-001` through `ARTIFACT-010`.
 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.
@@ -152,7 +152,7 @@ Call `receiz_artifact_verify` and `receiz_artifact_extract_verified` for input,
 
 Run current native artifact round-trip, destination reopen, namespace-preservation, and artifact-substitution rejection contracts. Historical obsolete-versioned reconcile fixtures are archival evidence only.
 
-## v110 unified admission and recovery
+## v111 unified admission and recovery
 
 Use `receiz.artifacts.admit(file)` to verify the complete artifact before classification. Verdicts are exactly `canonical-identity`, `bearer-recovery`, `verified-legacy-read`, `foreign-owner`, or `invalid`. Every verified result must report `canRestore`, `canSign`, `canClaimOwnership`, `canPublish`, and `canSettle` without inferring stronger authority from possession.
 
@@ -177,3 +177,13 @@ Recovery plan digest:
 Operation identity:
 Atomic commit result:
 ```
+
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.

package/receiz-cross-app-state/manifest.json

@@ -1,14 +1,14 @@
 {
-  "schema": "receiz.ai-skill-contract.v110",
+  "schema": "receiz.ai-skill-contract.v111",
   "name": "receiz-cross-app-state",
-  "version": "110.0.0",
+  "version": "111.0.0",
   "requires": {
-    "sdk": ">=110.0.0 <111.0.0",
-    "mcp": ">=110.0.0 <111.0.0",
-    "ruleset": "110.0.0",
-    "registryDigest": "824aa4af849c4840ba94535798eab36e45d514703b6ae0cd30d4aa53f3c896e4"
+    "sdk": ">=111.0.0 <112.0.0",
+    "mcp": ">=111.0.0 <112.0.0",
+    "ruleset": "111.0.0",
+    "registryDigest": "cf02d0bce6ad1541cfe84e27bfb1036777b29616bf8a1e5aeafb899a945e359a"
   },
-  "artifactLawVersion": "110.0.0",
+  "artifactLawVersion": "111.0.0",
   "artifactLaws": [
     "ARTIFACT-001",
     "ARTIFACT-002",
@@ -24,7 +24,12 @@
     "ARTIFACT-012",
     "ARTIFACT-013",
     "ARTIFACT-014",
-    "ARTIFACT-015"
+    "ARTIFACT-015",
+    "ARTIFACT-016",
+    "ARTIFACT-017",
+    "ARTIFACT-018",
+    "ARTIFACT-019",
+    "ARTIFACT-020"
   ],
   "laws": [
     "receiz.identity.cross-app-continuity",
@@ -79,7 +84,12 @@
     "hidden-recovery-mutation",
     "explanation-as-authority",
     "raw-capability-authority",
-    "card-payload-admission"
+    "card-payload-admission",
+    "structural-object-as-authority",
+    "caller-verifier-as-history-authority",
+    "parseable-key-as-signing-authority",
+    "terminal-mcp-confirmation-reuse",
+    "historical-runtime-object-as-current-authority"
   ],
   "requiredEvidence": [
     "same-account-uid-result",
@@ -103,7 +113,13 @@
     "zero-network-read-only-coordinator",
     "atomic-recovery-commit",
     "operation-identity-parity",
-    "multi-application-convergence"
+    "multi-application-convergence",
+    "canonical-exact-byte-readmission",
+    "complete-verifier-context-digest",
+    "independent-proof-history-evidence-roots",
+    "domain-separated-signing-challenge",
+    "distinct-plan-and-attempt-identities",
+    "structured-zero-write-failures"
   ],
   "requiredCompletionFields": [
     "sdk-version",
@@ -132,7 +148,7 @@
     "release-lock-pass",
     "zero-network-verification",
     "local-verifier-result",
-    "v110-admission-recovery-conformance",
+    "v111-artifact-authority-conformance",
     "no-hidden-mutation",
     "explanation-remains-non-authoritative"
   ],

package/receiz-deterministic-replay/SKILL.md

@@ -51,3 +51,12 @@ Request: Recompute admitted history from canonical inputs and prove checkpoint,
 
 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.
 
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.

package/receiz-deterministic-replay/manifest.json

@@ -1,12 +1,12 @@
 {
-  "schema": "receiz.ai-skill-contract.v110",
+  "schema": "receiz.ai-skill-contract.v111",
   "name": "receiz-deterministic-replay",
-  "version": "110.0.0",
+  "version": "111.0.0",
   "requires": {
-    "sdk": ">=110.0.0 <111.0.0",
-    "mcp": ">=110.0.0 <111.0.0",
-    "ruleset": "110.0.0",
-    "registryDigest": "824aa4af849c4840ba94535798eab36e45d514703b6ae0cd30d4aa53f3c896e4"
+    "sdk": ">=111.0.0 <112.0.0",
+    "mcp": ">=111.0.0 <112.0.0",
+    "ruleset": "111.0.0",
+    "registryDigest": "cf02d0bce6ad1541cfe84e27bfb1036777b29616bf8a1e5aeafb899a945e359a"
   },
   "laws": [
     "receiz.replay.deterministic",
@@ -23,7 +23,12 @@
   "forbiddenOperations": [
     "direct-state-write",
     "history-rewrite",
-    "authority-bypass"
+    "authority-bypass",
+    "structural-object-as-authority",
+    "caller-verifier-as-history-authority",
+    "parseable-key-as-signing-authority",
+    "terminal-mcp-confirmation-reuse",
+    "historical-runtime-object-as-current-authority"
   ],
   "requiredInputs": [
     "repository-root",
@@ -39,7 +44,13 @@
     "replay-equivalence",
     "compatibility",
     "mcp-conformance",
-    "independent-verifier"
+    "independent-verifier",
+    "canonical-exact-byte-readmission",
+    "complete-verifier-context-digest",
+    "independent-proof-history-evidence-roots",
+    "domain-separated-signing-challenge",
+    "distinct-plan-and-attempt-identities",
+    "structured-zero-write-failures"
   ],
   "completionCriteria": [
     "written-implementation-contract",

package/receiz-domain-builder/SKILL.md

@@ -51,3 +51,12 @@ Request: Model aggregate identities, commands, events, projections, privacy clas
 
 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.
 
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.

package/receiz-domain-builder/manifest.json

@@ -1,12 +1,12 @@
 {
-  "schema": "receiz.ai-skill-contract.v110",
+  "schema": "receiz.ai-skill-contract.v111",
   "name": "receiz-domain-builder",
-  "version": "110.0.0",
+  "version": "111.0.0",
   "requires": {
-    "sdk": ">=110.0.0 <111.0.0",
-    "mcp": ">=110.0.0 <111.0.0",
-    "ruleset": "110.0.0",
-    "registryDigest": "824aa4af849c4840ba94535798eab36e45d514703b6ae0cd30d4aa53f3c896e4"
+    "sdk": ">=111.0.0 <112.0.0",
+    "mcp": ">=111.0.0 <112.0.0",
+    "ruleset": "111.0.0",
+    "registryDigest": "cf02d0bce6ad1541cfe84e27bfb1036777b29616bf8a1e5aeafb899a945e359a"
   },
   "laws": [
     "receiz.command-only-mutation",
@@ -23,7 +23,12 @@
   "forbiddenOperations": [
     "direct-state-write",
     "history-rewrite",
-    "authority-bypass"
+    "authority-bypass",
+    "structural-object-as-authority",
+    "caller-verifier-as-history-authority",
+    "parseable-key-as-signing-authority",
+    "terminal-mcp-confirmation-reuse",
+    "historical-runtime-object-as-current-authority"
   ],
   "requiredInputs": [
     "repository-root",
@@ -39,7 +44,13 @@
     "replay-equivalence",
     "compatibility",
     "mcp-conformance",
-    "independent-verifier"
+    "independent-verifier",
+    "canonical-exact-byte-readmission",
+    "complete-verifier-context-digest",
+    "independent-proof-history-evidence-roots",
+    "domain-separated-signing-challenge",
+    "distinct-plan-and-attempt-identities",
+    "structured-zero-write-failures"
   ],
   "completionCriteria": [
     "written-implementation-contract",

package/receiz-identity-profile/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: receiz-identity-profile
-description: Use when checking username availability or updating a Receiz profile through the authenticated same-account v110 operation.
+description: Use when checking username availability or updating a Receiz profile through the authenticated same-account v111 operation.
 ---
 
 # Receiz Identity Profile
@@ -52,7 +52,7 @@ On `username_taken`, keep the same account and request another username. Preserv
 
 ## Result verification
 
-Require `status === "updated"`, an `accountUid` equal to the authenticated actor, the returned profile projection, and a `/u/` profile path. The current v110 outcome has no caller proof-head or receipt prerequisite.
+Require `status === "updated"`, an `accountUid` equal to the authenticated actor, the returned profile projection, and a `/u/` profile path. The current v111 outcome has no caller proof-head or receipt prerequisite.
 
 ## User confirmation
 
@@ -66,6 +66,16 @@ Call `receiz_identity_profile_update_plan` with `{ profile }` only. Show the pla
 
 Run `username-race`. Require one commit-time winner, unchanged account UID, and no identity-key dependency. Emulator evidence is simulation evidence, never production verification.
 
-## v110 identity recovery
+## v111 identity recovery
 
 `canonical-identity` is an identity continuity verdict from a verified enclosing artifact. Use its explicit permitted actions; do not infer publishing or settlement authority. `foreign-owner` and `verified-legacy-read` remain read-only. `admitAndRecover` plans locally and performs no session, network, database, or hidden mutation.
+
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.

package/receiz-identity-profile/manifest.json

@@ -1,14 +1,61 @@
 {
-  "schema": "receiz.ai-skill-contract.v110",
+  "schema": "receiz.ai-skill-contract.v111",
   "name": "receiz-identity-profile",
-  "version": "110.0.0",
-  "requires": { "sdk": ">=110.0.0 <111.0.0", "mcp": ">=110.0.0 <111.0.0", "ruleset": "110.0.0", "registryDigest": "824aa4af849c4840ba94535798eab36e45d514703b6ae0cd30d4aa53f3c896e4" },
-  "laws": ["receiz.identity.continuity", "receiz.profile.same-account-uid", "receiz.profile.commit-time-username-uniqueness"],
-  "sdkOperations": ["identity.checkUsernameAvailability", "profile.update", "artifacts.admit", "artifacts.planRecovery", "artifacts.commitRecovery"],
-  "allowedTools": ["receiz_identity_profile_update_plan", "receiz_identity_profile_update_execute", "receiz_artifact_admit", "receiz_artifact_recovery_plan", "receiz_artifact_recovery_commit"],
-  "requiredScopes": ["profile"],
-  "emulatorFixtures": ["username-race"],
-  "forbiddenOperations": ["direct-state-write", "identity-replacement", "identity-key-prerequisite", "caller-proof-head-prerequisite", "receipt-authority", "authority-bypass"],
-  "requiredEvidence": ["same-account-uid-result", "emulator-conformance", "release-lock-pass"],
+  "version": "111.0.0",
+  "requires": {
+    "sdk": ">=111.0.0 <112.0.0",
+    "mcp": ">=111.0.0 <112.0.0",
+    "ruleset": "111.0.0",
+    "registryDigest": "cf02d0bce6ad1541cfe84e27bfb1036777b29616bf8a1e5aeafb899a945e359a"
+  },
+  "laws": [
+    "receiz.identity.continuity",
+    "receiz.profile.same-account-uid",
+    "receiz.profile.commit-time-username-uniqueness"
+  ],
+  "sdkOperations": [
+    "identity.checkUsernameAvailability",
+    "profile.update",
+    "artifacts.admit",
+    "artifacts.planRecovery",
+    "artifacts.commitRecovery"
+  ],
+  "allowedTools": [
+    "receiz_identity_profile_update_plan",
+    "receiz_identity_profile_update_execute",
+    "receiz_artifact_admit",
+    "receiz_artifact_recovery_plan",
+    "receiz_artifact_recovery_commit"
+  ],
+  "requiredScopes": [
+    "profile"
+  ],
+  "emulatorFixtures": [
+    "username-race"
+  ],
+  "forbiddenOperations": [
+    "direct-state-write",
+    "identity-replacement",
+    "identity-key-prerequisite",
+    "caller-proof-head-prerequisite",
+    "receipt-authority",
+    "authority-bypass",
+    "structural-object-as-authority",
+    "caller-verifier-as-history-authority",
+    "parseable-key-as-signing-authority",
+    "terminal-mcp-confirmation-reuse",
+    "historical-runtime-object-as-current-authority"
+  ],
+  "requiredEvidence": [
+    "same-account-uid-result",
+    "emulator-conformance",
+    "release-lock-pass",
+    "canonical-exact-byte-readmission",
+    "complete-verifier-context-digest",
+    "independent-proof-history-evidence-roots",
+    "domain-separated-signing-challenge",
+    "distinct-plan-and-attempt-identities",
+    "structured-zero-write-failures"
+  ],
   "maximumAutonomousAuthority": "inspect-plan-simulate"
 }

package/receiz-mcp-agent-skill/SKILL.md

@@ -88,6 +88,6 @@ Resources:
 - [Action confirmation rules](resources/action-confirmation-rules.md)
 - [Response templates](resources/response-templates.md)
 
-## v110 artifact recovery tools
+## v111 artifact recovery tools
 
 Use `receiz_artifact_admit`, `receiz_artifact_recovery_plan`, and `receiz_artifact_admit_and_recover` as read-only SDK orchestration. For `receiz_artifact_recovery_commit`, pass only the plan digest, exact confirmation, stable idempotency key, and expected head. Never put a capability or store object in MCP JSON; the host resolves verified authority out of band.

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

@@ -1,6 +1,6 @@
 # MCP Tool Map
 
-## v110 Application Compiler
+## v111 Application Compiler
 
 | Need | Tool | Mutation |
 |---|---|---|
@@ -22,7 +22,7 @@ verification verdict or proof authority.
 
 Source: `packages/receiz-mcp-server/src/index.ts`.
 
-## v110 Current Profile And Ownership Outcomes
+## v111 Current Profile And Ownership Outcomes
 
 | Need | Tool | Mutation |
 |---|---|---|
@@ -37,7 +37,7 @@ The bearer plan verifies the complete sealed artifact with `client.artifacts.ver
 
 A verified proof object is not limited to the platform that created it. Any lawful platform may append authenticated ownership and history only while preserving the same immutable object identity, payload, provenance root, prior history, and unknown namespaces, then returning a complete verified proof object. These MCP tools invoke that same SDK continuity and never create an origin-platform lock or parallel chain.
 
-## v110 Complete Artifact Custody
+## v111 Complete Artifact Custody
 
 | Need | Tool | Boundary |
 |---|---|---|
@@ -111,7 +111,7 @@ Emulator output is labeled `sandboxVerified`; never translate it into Receiz ver
 - `receiz://sdk/docs`
 - `receiz://schemas/proof-object-v1`
 
-## v110 artifact admission and recovery
+## v111 artifact admission and recovery
 
 - `receiz_artifact_admit` — exact-byte local admission and typed authority verdict; zero writes.
 - `receiz_artifact_recovery_plan` — deterministic plan from the runtime-held SDK admission; zero writes.

package/receiz-migrations/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: receiz-migrations
-description: Use when upgrading Receiz schemas, commands, events, projections, rulesets, registries, artifacts, or applications to the active v110 contract.
+description: Use when upgrading Receiz schemas, commands, events, projections, rulesets, registries, artifacts, or applications to the active v111 contract.
 ---
 
 # receiz-migrations
 
 Inventory every write, classify its disposition, preserve historical readers, and fail closed on ambiguous authority. Receiz is a proof-native artifact system; this skill operates beneath sealed proof and verified local history.
 
-## Binding v110 artifact law
+## Binding v111 artifact law
 
 A Receiz artifact is the exact byte sequence returned by native Record -> Seal. The inner payload is never an acceptable substitute.
 
@@ -38,7 +38,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 signed v110 registry and `ARTIFACT-001` through `ARTIFACT-010`.
+2. Load the active signed v111 registry and `ARTIFACT-001` through `ARTIFACT-010`.
 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.
@@ -92,7 +92,7 @@ Network calls during verification: 0
 Local verifier result:
 ```
 
-## v110 unified admission and recovery
+## v111 unified admission and recovery
 
 Use `receiz.artifacts.admit(file)` to verify the complete artifact before classification. Verdicts are exactly `canonical-identity`, `bearer-recovery`, `verified-legacy-read`, `foreign-owner`, or `invalid`. Every verified result must report `canRestore`, `canSign`, `canClaimOwnership`, `canPublish`, and `canSettle` without inferring stronger authority from possession.
 
@@ -161,3 +161,13 @@ Refuse completion when any manifest input, law, test, conformance result, indepe
 Request: Inventory every write, classify its disposition, preserve historical readers, and fail closed on ambiguous authority.
 
 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.
+
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.

package/receiz-migrations/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Receiz Migrations"
   short_description: "Migrate constitutional applications"
-  default_prompt: "Use $receiz-migrations to migrate v110 artifact workflows without payload fallback, byte repacking, or admitted-history rewrite."
+  default_prompt: "Use $receiz-migrations to migrate v111 artifact workflows without payload fallback, byte repacking, or admitted-history rewrite."

package/receiz-migrations/manifest.json

@@ -1,14 +1,14 @@
 {
-  "schema": "receiz.ai-skill-contract.v110",
+  "schema": "receiz.ai-skill-contract.v111",
   "name": "receiz-migrations",
-  "version": "110.0.0",
+  "version": "111.0.0",
   "requires": {
-    "sdk": ">=110.0.0 <111.0.0",
-    "mcp": ">=110.0.0 <111.0.0",
-    "ruleset": "110.0.0",
-    "registryDigest": "824aa4af849c4840ba94535798eab36e45d514703b6ae0cd30d4aa53f3c896e4"
+    "sdk": ">=111.0.0 <112.0.0",
+    "mcp": ">=111.0.0 <112.0.0",
+    "ruleset": "111.0.0",
+    "registryDigest": "cf02d0bce6ad1541cfe84e27bfb1036777b29616bf8a1e5aeafb899a945e359a"
   },
-  "artifactLawVersion": "110.0.0",
+  "artifactLawVersion": "111.0.0",
   "artifactLaws": [
     "ARTIFACT-001",
     "ARTIFACT-002",
@@ -24,7 +24,12 @@
     "ARTIFACT-012",
     "ARTIFACT-013",
     "ARTIFACT-014",
-    "ARTIFACT-015"
+    "ARTIFACT-015",
+    "ARTIFACT-016",
+    "ARTIFACT-017",
+    "ARTIFACT-018",
+    "ARTIFACT-019",
+    "ARTIFACT-020"
   ],
   "laws": [
     "receiz.migration.forward-only",
@@ -64,7 +69,12 @@
     "hidden-recovery-mutation",
     "explanation-as-authority",
     "raw-capability-authority",
-    "card-payload-admission"
+    "card-payload-admission",
+    "structural-object-as-authority",
+    "caller-verifier-as-history-authority",
+    "parseable-key-as-signing-authority",
+    "terminal-mcp-confirmation-reuse",
+    "historical-runtime-object-as-current-authority"
   ],
   "requiredInputs": [
     "repository-root",
@@ -101,7 +111,13 @@
     "zero-network-read-only-coordinator",
     "atomic-recovery-commit",
     "operation-identity-parity",
-    "multi-application-convergence"
+    "multi-application-convergence",
+    "canonical-exact-byte-readmission",
+    "complete-verifier-context-digest",
+    "independent-proof-history-evidence-roots",
+    "domain-separated-signing-challenge",
+    "distinct-plan-and-attempt-identities",
+    "structured-zero-write-failures"
   ],
   "requiredCompletionFields": [
     "sdk-version",
@@ -132,7 +148,7 @@
     "release-lock-pass",
     "zero-network-verification",
     "local-verifier-result",
-    "v110-admission-recovery-conformance",
+    "v111-artifact-authority-conformance",
     "no-hidden-mutation",
     "explanation-remains-non-authoritative"
   ],

package/receiz-observability/SKILL.md

@@ -51,3 +51,12 @@ Request: Emit lower-authority operational evidence keyed by command, receipt, te
 
 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.
 
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.

package/receiz-observability/manifest.json

@@ -1,12 +1,12 @@
 {
-  "schema": "receiz.ai-skill-contract.v110",
+  "schema": "receiz.ai-skill-contract.v111",
   "name": "receiz-observability",
-  "version": "110.0.0",
+  "version": "111.0.0",
   "requires": {
-    "sdk": ">=110.0.0 <111.0.0",
-    "mcp": ">=110.0.0 <111.0.0",
-    "ruleset": "110.0.0",
-    "registryDigest": "824aa4af849c4840ba94535798eab36e45d514703b6ae0cd30d4aa53f3c896e4"
+    "sdk": ">=111.0.0 <112.0.0",
+    "mcp": ">=111.0.0 <112.0.0",
+    "ruleset": "111.0.0",
+    "registryDigest": "cf02d0bce6ad1541cfe84e27bfb1036777b29616bf8a1e5aeafb899a945e359a"
   },
   "laws": [
     "receiz.observability.lower-authority",
@@ -23,7 +23,12 @@
   "forbiddenOperations": [
     "direct-state-write",
     "history-rewrite",
-    "authority-bypass"
+    "authority-bypass",
+    "structural-object-as-authority",
+    "caller-verifier-as-history-authority",
+    "parseable-key-as-signing-authority",
+    "terminal-mcp-confirmation-reuse",
+    "historical-runtime-object-as-current-authority"
   ],
   "requiredInputs": [
     "repository-root",
@@ -39,7 +44,13 @@
     "replay-equivalence",
     "compatibility",
     "mcp-conformance",
-    "independent-verifier"
+    "independent-verifier",
+    "canonical-exact-byte-readmission",
+    "complete-verifier-context-digest",
+    "independent-proof-history-evidence-roots",
+    "domain-separated-signing-challenge",
+    "distinct-plan-and-attempt-identities",
+    "structured-zero-write-failures"
   ],
   "completionCriteria": [
     "written-implementation-contract",

package/receiz-offline-command/SKILL.md

@@ -68,3 +68,13 @@ There is no current MCP queue mutation authority. Do not invent one and do not c
 ## Emulator fixture
 
 Run the current offline proof replay, durable queue, and artifact-substitution rejection contracts. Historical obsolete-versioned signed-command fixtures remain archival evidence only.
+
+## v111 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.
+
+Admission must retain and canonically reverify the exact enclosing artifact bytes under the complete frozen verifier context. Recovery-authoritative history requires explicit independently verified evidence roots and fails closed on divergent verified heads. Canonical identity and `canSign` require enclosing-owner binding, identity-owner binding, key identity, and a domain-separated private-key challenge. Recovery planning re-derives state from verified admission and verified history.
+
+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, capabilities, plans, or confirmations cannot authorize a current v111 receiver; re-admit the historical artifact's exact bytes under the current verifier.