@receiz/ai-skills 105.0.0 → 107.0.0

package/README.md

@@ -1,12 +1,17 @@
 # Receiz AI Skills
 
-`receiz-app-builder-skill` is the authoritative v105 workflow for starting,
-integrating, upgrading, diagnosing, and repairing repositories through the typed
-Receiz app contract, shared SDK compiler, CLI, and MCP tools.
+`receiz-build-production-system` remains the constitutional orchestration skill for substantial
+Receiz applications. Fourteen focused constitutional skills supply architecture,
+domain, law, command, authority, replay, offline, causal, artifact, migration,
+performance, observability, testing, and release contracts. The earlier nine
+domain skills remain packaged for compatibility. v107 adds seven executable
+operation skills for identity profiles, portable continuity, generic bearer
+ownership, offline commands, proof media, cross-app state, and receipt admission.
+Every current manifest requires SDK/MCP `>=107.0.0 <108.0.0`, ruleset `107.0.0`, and registry digest `4d0caa6172a69c3bf5817c1c35db5630e555b5d6d824091d45a90fb426b86ef6`.
 
 This package teaches AI agents how to understand, verify, build with, and operate Receiz from the existing repository surfaces.
 
-It is published as `@receiz/ai-skills` and is an exact-version dependency of both `@receiz/sdk` and `@receiz/mcp-server`. Installing either package places these nine skill directories under `node_modules/@receiz/ai-skills` for explicit loading by an agent host.
+It is published as `@receiz/ai-skills` and is an exact-version dependency of both `@receiz/sdk` and `@receiz/mcp-server`. Installing either package places all thirty-one skill directories under `node_modules/@receiz/ai-skills` for explicit loading by an agent host.
 
 Receiz is a proof-native artifact system. A Receiz object is not a database row. It is a proof-carrying artifact. The artifact's witnessed history is the truth boundary. Server state, database state, UI state, marketplace state, and model memory are projections only. Old witnessed truth is not stale. If a projection is wrong, rebuild it from object history. If truth is missing, append new truth. Never mutate witnessed truth.
 
@@ -20,7 +25,12 @@ Agents may acquire scoped delegated access through the official Receiz Connect/O
 
 ## How Agents Should Use This Package
 
-Start with `receiz-skill-bundle` when the request spans multiple Receiz domains. Use `receiz-proof-skill` for any verification, proof object, vault, profile, pack, card, post, product, listing, receipt, marketplace, or offline artifact question. Use narrower skills only after the primitive is named.
+Start with `receiz-build-production-system` when work spans multiple constitutional domains. Its machine-readable manifest requires the exact active signed registry digest, command-only mutation, independent verification, MCP conformance, and a passing release lock. Use a focused v107 operation skill for SDK/MCP implementation and a constitutional skill for broader system law. The compatibility router `receiz-skill-bundle` and proof/domain skills remain available for earlier workflows.
+
+The v107 operation skills are executable contracts. Each binds exact SDK calls,
+MCP plan/execute tools, delegated scopes, proof heads, idempotency, offline and
+conflict behavior, receipt verification, confirmation boundaries, and deterministic
+emulator fixtures. They never grant autonomous mutation authority.
 
 Do not invent APIs. Use the SDK and MCP maps inside the skills, then inspect the repo when a requested operation is not listed.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@receiz/ai-skills",
-  "version": "105.0.0",
+  "version": "107.0.0",
   "description": "Authoritative Receiz AI operating skills for proof-native SDK and MCP agents.",
   "type": "module",
   "files": [
@@ -13,7 +13,29 @@
     "receiz-offline-verifier-skill",
     "receiz-proof-skill",
     "receiz-skill-bundle",
-    "receiz-sports-card-skill"
+    "receiz-sports-card-skill",
+    "receiz-architecture",
+    "receiz-domain-builder",
+    "receiz-constitutional-laws",
+    "receiz-command-builder",
+    "receiz-authority-security",
+    "receiz-deterministic-replay",
+    "receiz-offline-first",
+    "receiz-causal-sync",
+    "receiz-portable-artifacts",
+    "receiz-migrations",
+    "receiz-performance",
+    "receiz-observability",
+    "receiz-testing",
+    "receiz-release",
+    "receiz-build-production-system",
+    "receiz-identity-profile",
+    "receiz-portable-continuity",
+    "receiz-bearer-ownership",
+    "receiz-offline-command",
+    "receiz-proof-media",
+    "receiz-cross-app-state",
+    "receiz-receipt-admission"
   ],
   "keywords": [
     "receiz",

package/receiz-architecture/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: receiz-architecture
+description: Use when inspecting or changing Receiz domains, system boundaries, truth hierarchy, state machines, or constitutional architecture.
+---
+
+# receiz-architecture
+
+Map domains, sources of truth, state machines, dependency direction, and cross-domain authority before design or refactoring. Receiz is a proof-native artifact system; this skill operates beneath sealed proof and verified local history.
+
+## Constitutional workflow
+
+1. Inspect the repository and installed SDK version.
+2. Load the active signed 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.
+6. Add law, mutation, replay, and compatibility tests.
+7. Run MCP conformance checks.
+8. Require independent verifier evidence.
+9. Refuse completion until the release lock passes.
+
+Focused outcome: Map domains, sources of truth, state machines, dependency direction, and cross-domain authority before design or refactoring.
+
+## Machine contract
+
+Read [manifest.json](manifest.json) before acting. Its package range, ruleset, active registry digest requirement, laws, allowed tools, forbidden operations, evidence, escalation conditions, and autonomous-authority ceiling are executable constraints. Use plan/permit/execute for any admitted command and obtain explicit confirmation for the exact permit digest. The skill and MCP context are never proof authority.
+
+## Quick reference
+
+| Boundary | Required result |
+|---|---|
+| Stronger truth | Sealed artifact and verified local history remain above SDK, MCP, server, DB, session, and UI projections. |
+| Mutation | Canonical state changes only through an allowed SDK command and atomic receipt-producing admission. |
+| Evidence | MCP output and agent assertions do not count; independent verification and release-lock evidence do. |
+| Escalation | Stop on digest skew, authority bypass, missing capability, ambiguous migration, or absent independent evidence. |
+
+## Common mistakes
+
+- Treating a larger or newer server snapshot as permission to replace stronger admitted truth.
+- Calling an MCP plan, simulation, hash, model response, or passing UI check verification.
+- Appending an event without a command admission receipt.
+- Marking the task complete while required evidence is missing.
+
+## Completion refusal
+
+Refuse completion when any manifest input, law, test, conformance result, independent-verifier result, or release-lock result is absent or failing. Never reduce the evidence list, change a test to bless a visible regression, invent authority, or accept “the AI said it is valid” as evidence.
+
+## Example
+
+Request: Map domains, sources of truth, state machines, dependency direction, and cross-domain authority before design or refactoring.
+
+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.
+

package/receiz-architecture/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Receiz Architecture"
+  short_description: "Inspect constitutional architecture"
+  default_prompt: "Use -architecture to inspect a Receiz system's domains, truth hierarchy, and authority boundaries."

package/receiz-architecture/manifest.json

@@ -0,0 +1,57 @@
+{
+  "schema": "receiz.ai-skill-contract.v106",
+  "name": "receiz-architecture",
+  "requires": {
+    "sdk": ">=107.0.0 <108.0.0",
+    "mcp": ">=107.0.0 <108.0.0",
+    "ruleset": "107.0.0",
+    "registryDigest": "4d0caa6172a69c3bf5817c1c35db5630e555b5d6d824091d45a90fb426b86ef6"
+  },
+  "laws": [
+    "receiz.truth.stronger-first",
+    "receiz.registry.digest-alignment",
+    "receiz.command-only-mutation"
+  ],
+  "allowedTools": [
+    "receiz_architecture_inspect",
+    "receiz_authority_inspect",
+    "receiz_history_trace",
+    "receiz_bypass_scan"
+  ],
+  "forbiddenOperations": [
+    "direct-state-write",
+    "history-rewrite",
+    "authority-bypass"
+  ],
+  "requiredInputs": [
+    "repository-root",
+    "installed-sdk-version",
+    "active-registry-digest",
+    "applicable-laws",
+    "authority-boundaries"
+  ],
+  "requiredEvidence": [
+    "typecheck",
+    "law-coverage",
+    "mutation-tests",
+    "replay-equivalence",
+    "compatibility",
+    "mcp-conformance",
+    "independent-verifier"
+  ],
+  "completionCriteria": [
+    "written-implementation-contract",
+    "constitutional-context-digest-match",
+    "all-required-evidence-pass",
+    "release-lock-pass"
+  ],
+  "escalationConditions": [
+    "authority-bypass-detected",
+    "registry-digest-mismatch",
+    "missing-independent-evidence",
+    "missing-capability",
+    "ambiguous-migration"
+  ],
+  "maximumAutonomousAuthority": "inspect-plan-scaffold-test"
+}
+

package/receiz-authority-security/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: receiz-authority-security
+description: Use when work touches capabilities, identity, PBI, tenancy, ownership, settlement, secrets, delegated access, or authority escalation.
+---
+
+# receiz-authority-security
+
+Audit actors, tenants, capabilities, proof domains, confused-deputy paths, escalation, and cross-boundary effects. Receiz is a proof-native artifact system; this skill operates beneath sealed proof and verified local history.
+
+## Constitutional workflow
+
+1. Inspect the repository and installed SDK version.
+2. Load the active signed 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.
+6. Add law, mutation, replay, and compatibility tests.
+7. Run MCP conformance checks.
+8. Require independent verifier evidence.
+9. Refuse completion until the release lock passes.
+
+Focused outcome: Audit actors, tenants, capabilities, proof domains, confused-deputy paths, escalation, and cross-boundary effects.
+
+## Machine contract
+
+Read [manifest.json](manifest.json) before acting. Its package range, ruleset, active registry digest requirement, laws, allowed tools, forbidden operations, evidence, escalation conditions, and autonomous-authority ceiling are executable constraints. Use plan/permit/execute for any admitted command and obtain explicit confirmation for the exact permit digest. The skill and MCP context are never proof authority.
+
+## Quick reference
+
+| Boundary | Required result |
+|---|---|
+| Stronger truth | Sealed artifact and verified local history remain above SDK, MCP, server, DB, session, and UI projections. |
+| Mutation | Canonical state changes only through an allowed SDK command and atomic receipt-producing admission. |
+| Evidence | MCP output and agent assertions do not count; independent verification and release-lock evidence do. |
+| Escalation | Stop on digest skew, authority bypass, missing capability, ambiguous migration, or absent independent evidence. |
+
+## Common mistakes
+
+- Treating a larger or newer server snapshot as permission to replace stronger admitted truth.
+- Calling an MCP plan, simulation, hash, model response, or passing UI check verification.
+- Appending an event without a command admission receipt.
+- Marking the task complete while required evidence is missing.
+
+## Completion refusal
+
+Refuse completion when any manifest input, law, test, conformance result, independent-verifier result, or release-lock result is absent or failing. Never reduce the evidence list, change a test to bless a visible regression, invent authority, or accept “the AI said it is valid” as evidence.
+
+## Example
+
+Request: Audit actors, tenants, capabilities, proof domains, confused-deputy paths, escalation, and cross-boundary effects.
+
+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.
+

package/receiz-authority-security/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Receiz Authority Security"
+  short_description: "Audit capabilities and authority"
+  default_prompt: "Use -authority-security to audit Receiz capabilities, tenancy, and authority boundaries."

package/receiz-authority-security/manifest.json

@@ -0,0 +1,58 @@
+{
+  "schema": "receiz.ai-skill-contract.v106",
+  "name": "receiz-authority-security",
+  "requires": {
+    "sdk": ">=107.0.0 <108.0.0",
+    "mcp": ">=107.0.0 <108.0.0",
+    "ruleset": "107.0.0",
+    "registryDigest": "4d0caa6172a69c3bf5817c1c35db5630e555b5d6d824091d45a90fb426b86ef6"
+  },
+  "laws": [
+    "receiz.authority.capability-bound",
+    "receiz.identity.proof-bound",
+    "receiz.truth.stronger-first"
+  ],
+  "allowedTools": [
+    "receiz_architecture_inspect",
+    "receiz_authority_inspect",
+    "receiz_bypass_scan",
+    "receiz_command_simulate",
+    "receiz_law_explain"
+  ],
+  "forbiddenOperations": [
+    "direct-state-write",
+    "history-rewrite",
+    "authority-bypass"
+  ],
+  "requiredInputs": [
+    "repository-root",
+    "installed-sdk-version",
+    "active-registry-digest",
+    "applicable-laws",
+    "authority-boundaries"
+  ],
+  "requiredEvidence": [
+    "typecheck",
+    "law-coverage",
+    "mutation-tests",
+    "replay-equivalence",
+    "compatibility",
+    "mcp-conformance",
+    "independent-verifier"
+  ],
+  "completionCriteria": [
+    "written-implementation-contract",
+    "constitutional-context-digest-match",
+    "all-required-evidence-pass",
+    "release-lock-pass"
+  ],
+  "escalationConditions": [
+    "authority-bypass-detected",
+    "registry-digest-mismatch",
+    "missing-independent-evidence",
+    "missing-capability",
+    "ambiguous-migration"
+  ],
+  "maximumAutonomousAuthority": "inspect-plan-scaffold-test"
+}
+

package/receiz-bearer-ownership/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: receiz-bearer-ownership
+description: Use when claiming ownership of any qualifying Receiz bearer artifact and invalidating its previous active owner projection.
+---
+
+# Receiz Bearer Ownership
+
+Claim the generic enclosing artifact, not a card-specific or subpayload-specific invention. Verify the stronger proof object before projecting its embedded payload.
+
+## Exact SDK operation
+
+Use `proofHead.get`, `ownership.claimBearerAsset`, and `receipts.verify` for every supported artifact type.
+
+```ts
+import { createReceizClient } from "@receiz/sdk";
+
+const receiz = createReceizClient({ accessToken });
+const expectedOwnershipHead = await receiz.proofHead.get({ aggregateId: `ownership:${artifactId}` });
+const result = await receiz.ownership.claimBearerAsset({
+  artifactBytes: new Uint8Array(await artifactFile.arrayBuffer()),
+  filename: artifactFile.name,
+  mimeType: artifactFile.type || "application/octet-stream",
+  claimantKeyId,
+  expectedOwnershipHead,
+  idempotencyKey: `claim:${artifactId}:${claimantKeyId}:${expectedOwnershipHead.digest}`,
+});
+if (!await receiz.receipts.verify(result.receipt)) throw new Error("receipt_invalid");
+if (result.previousOwnerProjection.active || !result.owner.active) throw new Error("custody_conflict");
+```
+
+## Required authority
+
+Require the claimant Receiz identity plus delegated `receiz:record` and `receiz:seal` scopes or the corresponding signed-in session. The enclosing sealed artifact remains ownership authority.
+
+## Required proof head
+
+Read `ownership:${artifactId}` immediately before planning. Pass that exact head; never use a subpayload hash as the ownership boundary.
+
+## Idempotency
+
+Bind the key to artifact identity, claimant identity, artifact bytes, and expected ownership head. Exact replay returns the original admitted artifact; changed input with the same key is a conflict.
+
+## Offline behavior
+
+Offline work may verify the artifact and queue signed claim intent, but cannot report global ownership. Display `queued`, preserve the original artifact, and admit only after reconnect.
+
+## Conflict behavior
+
+On `ownership_head_stale` or `custody_conflict`, fetch the canonical ownership head and show the current owner/custody chain. Never overwrite, silently retry against a new owner, or revive the previous active projection.
+
+## Receipt verification
+
+Verify the returned canonical receipt and confirm `previousOwnerProjection.active === false`, `owner.active === true`, and ownership-head continuity before reporting ownership.
+
+## User confirmation
+
+Show artifact ID/type, claimant key ID, prior owner, expected head, irreversible custody consequence, and idempotency key. Require explicit confirmation.
+
+## MCP parity
+
+Call `receiz_proof_head_get`, then `receiz_bearer_asset_claim_plan`. Require the exact digest, call `receiz_bearer_asset_claim_execute`, then call `receiz_receipt_verify`. MCP planning and subpayload hashes are not proof authority.
+
+## Emulator fixture
+
+Run `generic-bearer-transfer` and `previous-owner-projection-invalidation` across all supported artifact families.

package/receiz-bearer-ownership/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Receiz Bearer Ownership"
+  short_description: "Claim generic bearer proof artifacts"
+  default_prompt: "Use $receiz-bearer-ownership to claim a qualifying bearer artifact through its enclosing proof."

package/receiz-bearer-ownership/manifest.json

@@ -0,0 +1,14 @@
+{
+  "schema": "receiz.ai-skill-contract.v107",
+  "name": "receiz-bearer-ownership",
+  "version": "107.0.0",
+  "requires": { "sdk": ">=107.0.0 <108.0.0", "mcp": ">=107.0.0 <108.0.0", "ruleset": "107.0.0", "registryDigest": "4d0caa6172a69c3bf5817c1c35db5630e555b5d6d824091d45a90fb426b86ef6" },
+  "laws": ["receiz.ownership.enclosing-proof", "receiz.custody.single-active-owner", "receiz.receipt.verify"],
+  "sdkOperations": ["ownership.claimBearerAsset", "proofHead.get", "receipts.verify"],
+  "allowedTools": ["receiz_bearer_asset_claim_plan", "receiz_bearer_asset_claim_execute", "receiz_proof_head_get", "receiz_receipt_verify"],
+  "requiredScopes": ["receiz:record", "receiz:seal"],
+  "emulatorFixtures": ["generic-bearer-transfer", "previous-owner-projection-invalidation"],
+  "forbiddenOperations": ["direct-state-write", "subpayload-authority", "previous-owner-reactivation", "authority-bypass"],
+  "requiredEvidence": ["receipt-verification", "emulator-conformance", "release-lock-pass"],
+  "maximumAutonomousAuthority": "inspect-plan-simulate"
+}

package/receiz-build-production-system/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: receiz-build-production-system
+description: Use when building or materially changing a production Receiz application across multiple constitutional domains.
+---
+
+# receiz-build-production-system
+
+Coordinate the complete production workflow across architecture, domains, laws, commands, history, offline behavior, MCP, verification, migration, and release. Receiz is a proof-native artifact system; this skill operates beneath sealed proof and verified local history.
+
+## Constitutional workflow
+
+1. Inspect the repository and installed SDK version.
+2. Load the active signed 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.
+6. Add law, mutation, replay, and compatibility tests.
+7. Run MCP conformance checks.
+8. Require independent verifier evidence.
+9. Refuse completion until the release lock passes.
+
+## Orchestration
+
+1. Discover
+2. Model domain
+3. Compile laws
+4. Define commands
+5. Implement events
+6. Build projections
+7. Add offline behavior
+8. Expose safe MCP tools
+9. Generate tests
+10. Audit authority
+11. Verify performance
+12. Release-lock
+
+**REQUIRED SUB-SKILL:** Use receiz-architecture
+
+**REQUIRED SUB-SKILL:** Use receiz-domain-builder
+
+**REQUIRED SUB-SKILL:** Use receiz-constitutional-laws
+
+**REQUIRED SUB-SKILL:** Use receiz-command-builder
+
+**REQUIRED SUB-SKILL:** Use receiz-authority-security
+
+**REQUIRED SUB-SKILL:** Use receiz-deterministic-replay
+
+**REQUIRED SUB-SKILL:** Use receiz-offline-first
+
+**REQUIRED SUB-SKILL:** Use receiz-causal-sync
+
+**REQUIRED SUB-SKILL:** Use receiz-portable-artifacts
+
+**REQUIRED SUB-SKILL:** Use receiz-migrations
+
+**REQUIRED SUB-SKILL:** Use receiz-performance
+
+**REQUIRED SUB-SKILL:** Use receiz-observability
+
+**REQUIRED SUB-SKILL:** Use receiz-testing
+
+**REQUIRED SUB-SKILL:** Use receiz-release
+
+## Machine contract
+
+Read [manifest.json](manifest.json) before acting. Its package range, ruleset, active registry digest requirement, laws, allowed tools, forbidden operations, evidence, escalation conditions, and autonomous-authority ceiling are executable constraints. Use plan/permit/execute for any admitted command and obtain explicit confirmation for the exact permit digest. The skill and MCP context are never proof authority.
+
+## Quick reference
+
+| Boundary | Required result |
+|---|---|
+| Stronger truth | Sealed artifact and verified local history remain above SDK, MCP, server, DB, session, and UI projections. |
+| Mutation | Canonical state changes only through an allowed SDK command and atomic receipt-producing admission. |
+| Evidence | MCP output and agent assertions do not count; independent verification and release-lock evidence do. |
+| Escalation | Stop on digest skew, authority bypass, missing capability, ambiguous migration, or absent independent evidence. |
+
+## Common mistakes
+
+- Treating a larger or newer server snapshot as permission to replace stronger admitted truth.
+- Calling an MCP plan, simulation, hash, model response, or passing UI check verification.
+- Appending an event without a command admission receipt.
+- Marking the task complete while required evidence is missing.
+
+## Completion refusal
+
+Refuse completion when any manifest input, law, test, conformance result, independent-verifier result, or release-lock result is absent or failing. Never reduce the evidence list, change a test to bless a visible regression, invent authority, or accept “the AI said it is valid” as evidence.
+
+## Example
+
+Request: Build a production Receiz domain.
+
+Return the implementation contract and plan. Execute confirmed allowed commands, then report all evidence and the exact remaining boundary.

package/receiz-build-production-system/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Receiz Build Production System"
+  short_description: "Orchestrate production Receiz builds"
+  default_prompt: "Use -build-production-system to build and release-lock a substantial Receiz production system."

package/receiz-build-production-system/manifest.json

@@ -0,0 +1,67 @@
+{
+  "schema": "receiz.ai-skill-contract.v106",
+  "name": "receiz-build-production-system",
+  "requires": {
+    "sdk": ">=107.0.0 <108.0.0",
+    "mcp": ">=107.0.0 <108.0.0",
+    "ruleset": "107.0.0",
+    "registryDigest": "4d0caa6172a69c3bf5817c1c35db5630e555b5d6d824091d45a90fb426b86ef6"
+  },
+  "laws": [
+    "receiz.truth.stronger-first",
+    "receiz.registry.digest-alignment",
+    "receiz.command-only-mutation",
+    "receiz.release.locked-digest"
+  ],
+  "allowedTools": [
+    "receiz_architecture_inspect",
+    "receiz_domain_scaffold",
+    "receiz_command_scaffold",
+    "receiz_law_define",
+    "receiz_law_coverage",
+    "receiz_authority_inspect",
+    "receiz_command_simulate",
+    "receiz_receipt_replay",
+    "receiz_history_trace",
+    "receiz_merge_simulate",
+    "receiz_bypass_scan",
+    "receiz_conformance_run",
+    "receiz_release_verify"
+  ],
+  "forbiddenOperations": [
+    "direct-state-write",
+    "history-rewrite",
+    "authority-bypass"
+  ],
+  "requiredInputs": [
+    "repository-root",
+    "installed-sdk-version",
+    "active-registry-digest",
+    "applicable-laws",
+    "authority-boundaries"
+  ],
+  "requiredEvidence": [
+    "typecheck",
+    "law-coverage",
+    "mutation-tests",
+    "replay-equivalence",
+    "compatibility",
+    "mcp-conformance",
+    "independent-verifier"
+  ],
+  "completionCriteria": [
+    "written-implementation-contract",
+    "constitutional-context-digest-match",
+    "all-required-evidence-pass",
+    "release-lock-pass"
+  ],
+  "escalationConditions": [
+    "authority-bypass-detected",
+    "registry-digest-mismatch",
+    "missing-independent-evidence",
+    "missing-capability",
+    "ambiguous-migration"
+  ],
+  "maximumAutonomousAuthority": "inspect-plan-scaffold-test"
+}
+

package/receiz-causal-sync/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: receiz-causal-sync
+description: Use when implementing multi-device synchronization, partitions, causal ordering, conflicts, retries, merge, or regional convergence.
+---
+
+# receiz-causal-sync
+
+Carry causal parents and Kai ordering, simulate partitions, resolve declared conflicts, and preserve deterministic convergence. Receiz is a proof-native artifact system; this skill operates beneath sealed proof and verified local history.
+
+## Constitutional workflow
+
+1. Inspect the repository and installed SDK version.
+2. Load the active signed 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.
+6. Add law, mutation, replay, and compatibility tests.
+7. Run MCP conformance checks.
+8. Require independent verifier evidence.
+9. Refuse completion until the release lock passes.
+
+Focused outcome: Carry causal parents and Kai ordering, simulate partitions, resolve declared conflicts, and preserve deterministic convergence.
+
+## Machine contract
+
+Read [manifest.json](manifest.json) before acting. Its package range, ruleset, active registry digest requirement, laws, allowed tools, forbidden operations, evidence, escalation conditions, and autonomous-authority ceiling are executable constraints. Use plan/permit/execute for any admitted command and obtain explicit confirmation for the exact permit digest. The skill and MCP context are never proof authority.
+
+## Quick reference
+
+| Boundary | Required result |
+|---|---|
+| Stronger truth | Sealed artifact and verified local history remain above SDK, MCP, server, DB, session, and UI projections. |
+| Mutation | Canonical state changes only through an allowed SDK command and atomic receipt-producing admission. |
+| Evidence | MCP output and agent assertions do not count; independent verification and release-lock evidence do. |
+| Escalation | Stop on digest skew, authority bypass, missing capability, ambiguous migration, or absent independent evidence. |
+
+## Common mistakes
+
+- Treating a larger or newer server snapshot as permission to replace stronger admitted truth.
+- Calling an MCP plan, simulation, hash, model response, or passing UI check verification.
+- Appending an event without a command admission receipt.
+- Marking the task complete while required evidence is missing.
+
+## Completion refusal
+
+Refuse completion when any manifest input, law, test, conformance result, independent-verifier result, or release-lock result is absent or failing. Never reduce the evidence list, change a test to bless a visible regression, invent authority, or accept “the AI said it is valid” as evidence.
+
+## Example
+
+Request: Carry causal parents and Kai ordering, simulate partitions, resolve declared conflicts, and preserve deterministic convergence.
+
+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.
+

package/receiz-causal-sync/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Receiz Causal Sync"
+  short_description: "Build deterministic causal merging"
+  default_prompt: "Use -causal-sync to implement causal synchronization, conflicts, and deterministic merging."