v120.0.0

The current registry appends v120 from the exact immutable v119 predecessor digest, and every active developer surface binds 120.0.0, the v120 registry digest, and the v120 operation-matrix digest.

Why

A coordinated identity prevents an older runtime, manifest, or agent instruction from claiming authority over a v120 living-subject transition.

Capability enabled

Developers can use the application, SDK, MCP, AI Skills, schemas, verifier, registry, and operation matrix as one coordinated v120 toolchain.

Compatibility

Current authority-bearing runtime values must remain within 120.0.0, while historical sealed proof objects remain exact-byte verifiable under their own release law.

Migration

No historical object is rewritten; applications adopt the exact v120 coordinated package and registry identity for new living-subject transitions.

The exact canonical head commits the complete content-addressed history through Kai, Merkle, and Fibonacci structures; bounded indexes retrieve references, then the Twin resolves and verifies exact primary proof-object bytes before reasoning and citing provenance.

Why

Continuity across millions of proof objects requires compact heads and bounded retrieval without abbreviating or replacing primary history.

Capability enabled

Twins and narration can stream relevant exact proof-object bytes from complete history while preserving near-instant first response and independently verifiable citations.

Compatibility

The former 96-object value remains a maximum reasoning window only and cannot truncate, summarize away, or replace canonical history.

Migration

Existing exact proof objects remain unchanged and become addressable through the v120 append-only brain index after verified admission.

Typed commands validate subject and world heads, owner capability or a current digest-bound mandate, registry and reducer digests, idempotency, and deterministic decision output before atomically appending events and receipts; rejection advances nothing.

Why

Model output must remain non-authoritative while autonomous characters still act through bounded, replayable, independently verifiable law.

Capability enabled

Relationships, battles, gifts, trades, memory, autonomous ticks, replay, checkpoints, and subscriptions operate through one typed zero-write-on-failure authority boundary.

Compatibility

Loose v119 jobs and model statements cannot authorize v120 subject events; current mandate, reducer, registry, application, tenant, and exact-head bindings are required.

Migration

Autonomous applications must use typed v120 subject ticks and reauthorize exact v120 mandates rather than carrying forward loose job authority.

A sealed one-time instrument binds subject and ownership heads, expiry, recipient policy, pending custody, inventory disposition, private-memory policy, registry, reducer, and claim capability; claim revokes former-owner mandates and private authority in the same admitted transition.

Why

Transfer must not fork ownership, lose unknown namespaces, leave queued former-owner authority active, or confuse possession with canonical ownership.

Capability enabled

Offline-verifiable instruments can be claimed later online with replay protection, idempotent receipts, explicit bundled inventory handling, newly sealed successor artifacts, and zero-write failure.

Compatibility

A stale, cancelled, expired, replayed, mismatched-recipient, or non-current-ownership instrument cannot transfer or partially modify the subject.

Migration

Transferred v120 subjects retain prior exact bytes and history; the new owner must explicitly activate a new mandate before autonomy resumes.

Twin input binds owner, subject digest, exact context head, client message identity, and response mode; output separates speech, proposed intentions, observed facts, proof-derived memories, and performance while portable mind artifacts bind subject, prior mind, event, and memory heads with explicit public/private policy.

Why

A living character must remain the same subject through time while model narration and animation remain non-authoritative projections.

Capability enabled

Applications can stream text, voice, visemes, gaze, blink, breath, emotion, gesture, intentions, and completion over exact proof context, then export or import the subject mind without rewriting identity or discarding forks.

Compatibility

A v120 model response, performance cue, summary, index, or mind projection cannot admit an event or replace exact proof bytes.

Migration

Applications that multiplexed a person Twin through thread keys adopt subject-scoped Twin and portable mind operations while preserving existing proof history.

Mandates bind actions, regions, subjects and owners, privacy, battle, inventory and value exposure, approvals, frequency, daily limits, memory visibility, expiry, providers, safety, application, and tenant; durable leases reverify mandate and exact heads at execution time with deterministic Kai, crash recovery, budgets, and bounded catch-up.

Why

Autonomy must survive process failure without widening authority, duplicating events, or inventing success after a model timeout.

Capability enabled

Subjects can explore and interact while an owner is absent, with exact revocation, stale-head rejection, idempotent admission, and zero action after expiry, owner change, provider mismatch, timeout, or malformed intent.

Compatibility

Loose generic jobs cannot authorize living-subject execution; a current v120 mandate digest and exact tick contract are required.

Migration

Replace loose subject jobs with subjects.runtime.enqueueTick and activate a new exact v120 mandate before autonomous execution.

Conversation, episodic, relationship, battle, discovery, ownership/care, and inventory/trade memories cite event IDs; relationship edges and inventory/trade projections rebuild from exact heads, and multi-subject changes use one transaction receipt.

Why

A summary or model assertion cannot become factual memory, and social or inventory state cannot become one-sided during conflict or retry.

Capability enabled

Creatures can meet, build trust or rivalry, battle, gift, use, and trade items with privacy, blocklists, mandate limits, owner approval thresholds, exact citations, and atomic participant histories.

Compatibility

Factual v120 memory without admitted event citations and one-sided social or inventory updates are invalid.

Migration

Rebuild factual memory and social/inventory projections from admitted events through an exact head rather than importing latest snapshots as authority.

Subject and world additions expose exact after-head cursors, causal parents, SSE, signed webhooks, duplicate delivery, partition recovery, deterministic convergence, and fork preservation; narrow delegated scopes keep ownership distinct from private-memory disclosure.

Why

Portable beings require live delivery and recovery without granting the network, application, or latest snapshot authority over sealed history.

Capability enabled

Multiple applications and devices can follow one subject and world timeline, recover from delayed or duplicate delivery, and converge deterministically while preserving unresolved forks.

Compatibility

Latest-snapshot-wins reconciliation and ownership-implies-all-private-memory access are forbidden.

Migration

Consumers resume from exact subject/world heads, accept duplicate delivery idempotently, and preserve conflicts for proof-native reconciliation.

The append-only sealed composite Showcase head owns the complete 469-object count and full authority while presentation remains bounded; each publish must settle one successor head, proof-brain admission binds exact primary bytes, narration access reuses payload_b64 anchor fallback beneath enclosing proof verification and exact text-digest readiness, and Identity Artwork protection binds reserved filenames plus image media evidence rather than incidental claim prose.

Why

A stale Showcase count, on-visit full-history hydration, abbreviated Twin history, missing legacy anchor, speculative Play control, or prose-driven PDF reclassification would replace stronger carried proof with weaker UI or route policy state.

Capability enabled

Public profiles paint a stable 469-object authority immediately, Twins retrieve any admitted proof memory at scale, long-form readers preserve access and media truth without background remounts, and eligible PDFs return their exact `.receized.pdf` bytes without an unrelated PBI gate.

Compatibility

The visible 24/18 window remains a presentation bound only; it cannot truncate the 469-object composite or proof brain.

Migration

Rebuild the released first-paint projection at the exact composite head, stop automatically rediscovering history already carried by the sealed Showcase proof object, and classify protected Identity Artwork from exact artifact evidence rather than free-form document prose.

The SDK exposes complete subject/world/bearer namespaces; MCP exposes nine enclosing-artifact tools plus 37 living-subject tools with source primitive and registry/reducer digests; the AI package ships 39 skills, 33 manifests, and 30 OpenAI prompts; Receiz Docs projects exact package mechanics, schemas, conformance, compatibility, and release evidence.

Why

Surface parity prevents an agent or application from inventing a second authority mechanism to fill a missing SDK, MCP, AI, or documentation gap.

Capability enabled

One typed and documented workflow spans subject resolution, proof retrieval, Twin proposals, world admission, mandates, runtime, memory, social state, bearer transfer, replay, and independent conformance.

Compatibility

Current SDK, MCP, AI Skills, schemas, registry, operation matrix, and docs must all remain exactly v120; historical artifacts remain immutable read/verify/export inputs only.

Migration

Adopt coordinated 120.0.0 packages and regenerate package/reference projections; do not mix current authority-bearing runtime objects across release identities.

Draft 2020-12 schemas, durable tamper-evident snapshots, deterministic model/world/Kai stubs, atomic transactions, partitions, delayed and duplicate delivery, artifact portability, tamper/substitution vectors, and checkpoint equivalence feed a 19-check living-subject and bearer suite.

Why

A proof-native runtime needs reproducible failure evidence for authority, atomicity, identity continuity, and replay—not only happy-path API examples.

Capability enabled

SDK and MCP implementers can independently reproduce the ten core living-subject laws and nine bearer-transfer laws with exact registry and reducer bindings.

Compatibility

Emulator evidence is deterministic sandbox evidence and cannot be relabeled as package publication, deployment, production smoke, or signed attestation.

Migration

Integrations add the v120 schema bundle and living-subject conformance suite to release qualification while retaining separate production evidence dimensions.