@receiz/ai-skills 119.0.0 → 121.0.0

package/README.md

@@ -1,10 +1,10 @@
 # Receiz AI Skills
 
-The `119.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.
+The `121.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.
 
-## V119 artifact authority chain
+## V120 artifact authority chain
 
-V119 carries two established proof-object laws unchanged:
+V120 carries two established proof-object laws unchanged:
 `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
@@ -18,20 +18,22 @@ 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. V119 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.
+The same v120 package carries 37 living-subject MCP tools: subject resolve/state/history/memory/relationships/inventory; subject Twin profile/message/mind export/import planning; mandate get/plan/activate/pause/revoke; world additions/command plan/validate/execute/transaction plan/execute/receipt/replay; subject runtime enqueue/status/cancel; living-subject conformance; proof-brain head/search/resolve/stream; and bearer preview/issue/inspect/claim/cancel/status. Each generated skill map binds those exact names to SDK primitives, strict input/output types, source primitive, registry/reducer digests, zero-write failure, and the non-authority boundary.
+
+`client.admission.browserStore` is durable admission coordination only: it stores no proof object or sealed artifact bytes and never blocks known-artifact first paint. V120 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 v119 outcomes for identity profiles, portable continuity, bearer ownership, offline transport,
+describe current v121 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 `119.0.0`, requires SDK/MCP `>=119.0.0 <120.0.0`, and binds ruleset `119.0.0` to registry digest `49c167a437ec7c0e486412dd62c54af4abdf94eda1ebc18d263a027d105cecd9` and operation-matrix digest `53cf9d6862b2396e2fe7864f8607c00c4e3b6e31b082ab5c5c8dff088fcb52c1` 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 `121.0.0`, requires SDK/MCP `>=121.0.0 <122.0.0`, and binds ruleset `121.0.0` to registry digest `29a793a5bcc0195ab41d30614d37ac51df66023af354fa4335460764eb0af413` and operation-matrix digest `208553829ba78a5536524b864577ce59989e2d0a994fad9598d39ae3d557c4f5` from SDK source.
 
 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 all 32 skills under `node_modules/@receiz/ai-skills`: 26 manifests and 23 OpenAI agent prompts are included 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 39 skills under `node_modules/@receiz/ai-skills`: 33 manifests and 30 OpenAI agent prompts are included for explicit loading by an agent host.
 
 Receiz is a proof-native artifact system. Sealed proof/object truth is strongest: a Receiz object is not a database row, but a proof-carrying artifact whose witnessed history is the truth boundary. The proof object carries continuity; SDK and MCP may verify, extract, append, or project beneath that carried truth. Receiz.com reference behavior comes before SDK, MCP, AI, and other developer rails. 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.
 
@@ -40,16 +42,16 @@ A verified proof object is not limited to the platform that created it. Any lawf
 ## SDK, MCP, And Skills
 
 - SDK: `@receiz/sdk` is the universal runtime; `@receiz/sdk/react` is React-only; `@receiz/sdk/compiler` is Node-only; `@receiz/sdk/testing` is browser-safe sandbox and conformance support.
-- MCP: `@receiz/mcp-server` is for agent tool access. Its current nine artifact tools expose the transition and reconciliation orchestration contracts through the same SDK authority types. Diagnostics, public reads, app-state/public-store actions, previews, and delegated writes remain beneath proof truth.
+- MCP: `@receiz/mcp-server` is for agent tool access. Its current nine artifact tools and 37 living-subject tools expose transition, reconciliation, proof-brain, Twin, mandate, runtime, world, memory, social, inventory, and bearer contracts through the same SDK authority types. Diagnostics, public reads, app-state/public-store actions, previews, and delegated writes remain beneath proof truth.
 - Skills: this package is operating doctrine. It tells an AI which Receiz primitive is active, which source of truth wins, which SDK or MCP rail to use, and what must never be assumed.
 
 Agents may acquire scoped delegated access through the official Receiz Connect/OIDC Authorization Code + PKCE flow or through the MCP delegated-agent setup path exposed by `receiz_mcp_login`. That acquired access is permission to call scoped SDK/MCP rails after user consent. It is not proof authority and must never outrank artifact truth.
 
 ## 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 v119 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 v120 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 v119 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 v120 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.
 
@@ -78,3 +80,17 @@ When SDK or MCP changes:
 - If history is missing, append the missing truth.
 - Generated apps must preserve Receiz proof semantics.
 - Generated apps should not require a traditional database unless the user explicitly asks for one.
+
+## v121 living-subject skills
+
+- `receiz-living-subject` governs immutable subject identity, byte-preserved namespaces, ownership continuity, state, history, additions, and portable proof artifacts.
+- `receiz-subject-twin` governs subject-scoped profile, exact-head messaging, complete proof-brain retrieval, portable mind export/import, memory summaries, and the separation between speech, intentions, facts, memories, and performance.
+- `receiz-autonomous-mandate` governs exact-digest owner authorization, bounded actions and regions, privacy, battle, inventory/value exposure, rate limits, provider/safety/application scope, expiry, pause, and immediate revocation.
+- `receiz-world-event-runtime` governs typed command planning, exact-head validation, deterministic decision, event admission, receipts, durable ticks, idempotency, replay, and structured zero-write failure.
+- `receiz-multi-subject-transaction` governs atomic meetings, relationships, battles, gifts, and trades so every participant head advances together or none do.
+- `receiz-event-derived-memory` governs factual memories with admitted event citations and rebuildable AI summaries/projections.
+- `receiz-live-proof-character` governs streamed reply, audio, viseme, gaze, blink, breath, emotion, gesture, proposed intention, and completion events as non-authoritative performance over exact proof context.
+
+Every living-subject skill carries its SDK map, MCP map, authority rules, examples, tests, manifest, OpenAI metadata, and the exact v121 registry and operation-matrix digests. The skills teach the same sequence as the implementation: canonical head → entire proof history → compact indexes → relevant references → exact primary proof objects → reasoning → cited answer. They never authorize a world event, transfer, mandate, or release claim by prose.
+
+The updated constitutional skills bind living-subject behavior into app building, command construction, deterministic replay, causal sync, global reconciliation, portable continuity, authority/security, MCP operation, testing, release, constitutional law, and offline-first operation. Their examples cover exact proof-memory speech, absent-owner exploration, mutual relationship formation, bounded trade, atomic battle, cross-device restoration, mandate revocation during a queued action, partition convergence, rejection of an AI-invented event, and cross-application subject continuity.

package/SKILLS.md

@@ -1,13 +1,13 @@
-# Receiz AI Skills v119
+# Receiz AI Skills v120
 
-V119 preserves sealed proof/object authority and adds
+V120 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 `49c167a437ec7c0e486412dd62c54af4abdf94eda1ebc18d263a027d105cecd9` and application-operation-matrix digest `53cf9d6862b2396e2fe7864f8607c00c4e3b6e31b082ab5c5c8dff088fcb52c1` from the v119 SDK source.
+This package ships 39 skills, 33 machine-readable manifests, and 30 OpenAI agent prompts. Every current manifest binds registry digest `29a793a5bcc0195ab41d30614d37ac51df66023af354fa4335460764eb0af413` and application-operation-matrix digest `208553829ba78a5536524b864577ce59989e2d0a994fad9598d39ae3d557c4f5` from the v120 SDK source.
 
 ## Current MCP artifact inventory: nine tools
 
@@ -25,6 +25,12 @@ The single current inventory is:
 
 The first five tools are also the historical v112 compatibility inventory. That historical label preserves the v112 contract; it does not define a second current surface.
 
+## Current MCP living-subject inventory: 37 tools
+
+The exact v121 living-subject inventory covers `receiz_subject_resolve`, `receiz_subject_state`, `receiz_subject_history`, `receiz_subject_memory_query`, `receiz_subject_relationships`, `receiz_subject_inventory`, `receiz_subject_twin_profile`, `receiz_subject_twin_message`, `receiz_subject_twin_mind_export`, `receiz_subject_twin_mind_import_plan`, `receiz_subject_mandate_get`, `receiz_subject_mandate_plan`, `receiz_subject_mandate_activate`, `receiz_subject_mandate_pause`, `receiz_subject_mandate_revoke`, `receiz_world_additions`, `receiz_world_command_plan`, `receiz_world_command_validate`, `receiz_world_command_execute`, `receiz_world_transaction_plan`, `receiz_world_transaction_execute`, `receiz_world_receipt`, `receiz_world_replay`, `receiz_subject_runtime_enqueue`, `receiz_subject_runtime_status`, `receiz_subject_runtime_cancel`, `receiz_living_subject_conformance`, `receiz_subject_brain_head`, `receiz_subject_brain_search`, `receiz_subject_brain_resolve`, `receiz_subject_brain_stream`, `receiz_bearer_transfer_preview`, `receiz_bearer_instrument_issue`, `receiz_bearer_instrument_inspect`, `receiz_bearer_instrument_claim`, `receiz_bearer_transfer_cancel`, and `receiz_bearer_transfer_status`.
+
+Every tool calls the SDK primitive named by its skill map, returns the source primitive and v120 registry/reducer digests, requires exact plan/permit/instrument confirmation for writes, resolves exact bytes before commit, and returns structured zero-write failure. MCP and skill prose never become authority.
+
 ## Skill inventory
 
 The canonical machine-readable index is [skills.json](skills.json). Start with `receiz-build-production-system` for multi-domain work, `receiz-global-reconciliation` for named-domain head resolution and offline reconciliation, or a focused primitive skill for narrower work.
@@ -34,3 +40,13 @@ The canonical machine-readable index is [skills.json](skills.json). Start with `
 All current skills forbid: `last-write-wins`, `timestamp-as-head-authority`, `connect-token-as-proof-authority`, `local-receipt-as-global-authority`, `projection-as-current-owner`, `silent-divergence-resolution`, `remote-reconciliation-before-first-paint`, `unverified-server-artifact-render`, `environment-player-token-fallback`, `accepted-means-effects-delivered`, and `indeterminate-means-failed`.
 
 These instructions remain beneath exact sealed artifact bytes, independently verified history, verified identity evidence, plan-bound capability authority, and atomic named-domain acceptance.
+
+## v121 living-subject skills
+
+- `receiz-living-subject`: immutable identity, byte-preserved namespaces, ownership continuity, state, history, additions, and portable artifacts.
+- `receiz-subject-twin`: complete exact-head proof retrieval, speech/intention/fact/memory separation, subject mind portability, and provenance.
+- `receiz-autonomous-mandate`: owner-confirmed digest scope, runtime re-verification, expiration, pause, and revocation.
+- `receiz-world-event-runtime`: typed command admission, deterministic receipts, durable ticks, retries, replay, and zero-write failure.
+- `receiz-multi-subject-transaction`: atomic meetings, relationships, battles, gifts, inventory, and trades.
+- `receiz-event-derived-memory`: admitted-event citations and rebuildable projections.
+- `receiz-live-proof-character`: streamed voice and performance cues that never become canonical fact.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@receiz/ai-skills",
-  "version": "119.0.0",
+  "version": "121.0.0",
   "description": "Registry-bound Receiz AI operating contracts beneath proof authority for SDK and MCP agents.",
   "type": "module",
   "files": [
@@ -39,7 +39,14 @@
     "receiz-proof-media",
     "receiz-cross-app-state",
     "receiz-receipt-admission",
-    "receiz-global-reconciliation"
+    "receiz-global-reconciliation",
+    "receiz-living-subject",
+    "receiz-subject-twin",
+    "receiz-autonomous-mandate",
+    "receiz-world-event-runtime",
+    "receiz-multi-subject-transaction",
+    "receiz-event-derived-memory",
+    "receiz-live-proof-character"
   ],
   "keywords": [
     "receiz",

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 v119 artifact law
+## Binding v120 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 v119 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.
+The exact v121 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`, `receiz.economy-showcase.merge.plan`, `receiz.subject.resolve`, `receiz.subject.brain.retrieve`, `receiz.subject.twin.message`, `receiz.subject.mandate.activate`, `receiz.world.command.plan`, `receiz.world.command.execute`, `receiz.world.transaction.plan`, `receiz.world.transaction.execute`, `receiz.subject.runtime.enqueue`, `receiz.subject.memory.project`, `receiz.bearer.transfer.plan`, `receiz.bearer.instrument.issue`, `receiz.bearer.instrument.claim`, `receiz.bearer.transfer.cancel`. 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 v119 registry and `ARTIFACT-001` through `ARTIFACT-030`.
+2. Load the active canonical v120 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)
 
-## v119 unified admission and recovery
+## v120 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:
 ```
 
-## v119 artifact-derived authority
+## 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.
 
@@ -241,4 +241,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 v119 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 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.
+
+## v121 living-subject contract
+
+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.