Keep what you’ve built.
Do more with it.

Use when starting, integrating, upgrading, diagnosing, or repairing a TypeScript or Next.js repository that uses Receiz application contracts, SDK compiler commands, generated files, or MCP app tools.

Use when inspecting or changing Receiz domains, system boundaries, truth hierarchy, state machines, or constitutional architecture.

Use when building or verifying generic Receiz attestations, credentials, selective presentations, holder-presence ceremonies, subject coordination, or typed external execution.

Use when work touches capabilities, identity, PBI, tenancy, ownership, settlement, secrets, delegated access, or authority escalation.

Use when planning, activating, pausing, revoking, or explaining a digest-bound policy for bounded autonomous subject execution.

Use when claiming a qualifying Receiz bearer proof object from a complete verified artifact and returning its new native sealed artifact.

Use when building or materially changing a production Receiz application across multiple constitutional domains.

Use when an agent must build or modify Receiz-native apps, storefronts, marketplaces, proof pages, pack apps, profile vaults, claim flows, QR entry flows, templates, or custom domain apps with the Receiz SDK.

Use when implementing multi-device synchronization, partitions, causal ordering, conflicts, retries, merge, or regional convergence.

Use when adding or changing Receiz commands, admitted events, transactions, receipts, or canonical mutation paths.

Use when an agent must create, explain, inspect, or verify Receiz commerce surfaces, product proof objects, storefronts, no-database stores, checkout boundaries, buyer/seller language, product ownership, or receipt proof.

Use when defining, versioning, explaining, covering, or changing executable Receiz laws and rulesets.

Use when carrying verified namespaced account state between Receiz applications without a shared app database or identity fork.

Use when implementing or diagnosing history replay, checkpoints, receipts, projections, equivalence, or deterministic simulation.

Use when an agent must create, explain, or operate Receiz QR activation, Pack Derby, venue activation, restaurant or bar playbooks, affiliate boundaries, staff scripts, conversion language, or physical-to-proof distribution.

Use when creating or extending a Receiz domain, aggregate, event model, projection, schema, or generated domain scaffold.

Use when querying, projecting, citing, compacting, exporting, or rebuilding subject memory from admitted proof events.

Use when resolving a named Receiz coordination-domain head, reconciling independently verified offline history, handling structural divergence or contention, recovering an indeterminate attempt, or inspecting acceptance and effects without delaying known-artifact first paint.

Use when checking username availability or updating a Receiz profile through the authenticated same-account v120 operation.

Use when streaming a proof-grounded character with low-latency speech, audio, visemes, gaze, emotion, gesture, and structured intentions.

Use when creating, resolving, transferring, exporting, importing, or extending a proof-native creature, character, vehicle, agent, or collectible with immutable identity.

Use when an agent has or needs Receiz MCP tool access for verification routing, public reads, app-state actions, proof inspection, storefront operations, sports proof inspection, deterministic previews, or delegated writes.

Use when upgrading Receiz schemas, commands, events, projections, rulesets, registries, artifacts, or applications to the active v120 contract.

Use when a meeting, mutual relationship, battle, gift, or trade must modify two or more proof histories atomically.

Use when adding or reviewing logs, traces, metrics, diagnostics, incident evidence, audit records, or privacy-safe telemetry.

Use when durably queuing Receiz transport intent while preserving verified local truth and refusing to call queue settlement proof admission.

Use when implementing offline creation, verified local truth, reconnect, outbox, first paint, or device continuity.

Use when an agent must verify, explain, debug, or build Receiz offline verification for local files, sealed artifacts, manifests, embedded proof, airplane-mode workflows, or artifact-over-server truth boundaries.

Use when measuring or changing first paint, registry loading, admission latency, replay, bundles, memory, or mobile execution.

Use when creating, importing, exporting, inspecting, signing, or verifying portable Receiz proof objects and sealed files.

Use when restoring Record, Seal, Key, or Vault account truth and carrying verified additions across devices without a weaker reconciliation authority.

Use when exchanging a verified Receiz proof object for narrow application authority without a website redirect.

Use when creating native Receiz proof media, preserving its exact artifact bytes, or projecting its verified public URL onto the authenticated profile.

Use when an agent must verify, inspect, explain, or report on Receiz proof objects, cards, packs, products, posts, receipts, vaults, profiles, marketplace listings, live sports objects, or offline proof artifacts.

Use when inspecting admission evidence while preserving the rule that receipts and heads are witnesses beneath the verified proof object.

Use when qualifying, locking, packaging, attesting, or preparing publication of a coordinated Receiz release.

Use when an agent needs the complete Receiz skill router for choosing proof, builder, MCP agent, commerce, sports card, offline verifier, or distribution skills in one task.

Use when an agent must explain, verify, build, or operate Receiz sports card objects, card memory, live event appends, rarity language, MLB proof language, pack openings, card market surfaces, or game surfaces.

Use when grounding a subject-scoped Twin in the complete proof history at an exact Kai head and returning speech, cited memory, structured intentions, and provenance.

Use when designing or running Receiz conformance, law, mutation, replay, compatibility, property, fuzz, chaos, or adapter tests.

Use when deriving lawful-action Settlement from sealed proof or executing and recovering proof-native Phi movement through Settlement and Reserve.

Use when planning, displaying, validating, or executing proof-native Phi value movement through the distinct Settlement and Reserve rails.

Use when turning AI or application intent into typed deterministic world commands, admitted events, receipts, replay checkpoints, and live additions.