Documented release
v125.0.0
Reality-Grade Infrastructure
Release date 2026-09-04
Outcome
Outcome
Receiz v125 makes that order executable. A proof object carries the thing that happened, the law that admits it, its causal position, the evidence that binds it, and the means to verify it. Applications, agents, institutions, databases, networks, and readers may inspect or project that truth. None may manufacture it, substitute for it, or rank above it.
Changes
What changed
A Kai coordinate is accepted as authority only through the…
A Kai coordinate is accepted as authority only through the proof-bearing KKS/KaiSigil boundary; a decimal string is not enough.
Technical and authority boundary
A Kai coordinate is accepted as authority only through the proof-bearing KKS/KaiSigil boundary; a decimal string is not enough.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- A Kai coordinate is accepted as authority only through the proof-bearing KKS/KaiSigil boundary; a decimal string is not enough.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Live coordinates advance from a retained monotonic head, including multiple…
Live coordinates advance from a retained monotonic head, including multiple appends inside one millisecond and backward wall-clock movement.
Technical and authority boundary
Live coordinates advance from a retained monotonic head, including multiple appends inside one millisecond and backward wall-clock movement.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Live coordinates advance from a retained monotonic head, including multiple appends inside one millisecond and backward wall-clock movement.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
createdAt and every other Chronos field are descriptive bridges derived from Kai
createdAt and every other Chronos field are descriptive bridges derived from Kai. They never order proof history.
Technical and authority boundary
createdAt and every other Chronos field are descriptive bridges derived from Kai. They never order proof history.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- createdAt and every other Chronos field are descriptive bridges derived from Kai. They never order proof history.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Legacy Chronos material remains available as a compatibility projection but…
Legacy Chronos material remains available as a compatibility projection but cannot be promoted into authoritative KKS ordering.
Technical and authority boundary
Legacy Chronos material remains available as a compatibility projection but cannot be promoted into authoritative KKS ordering.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Legacy Chronos material remains available as a compatibility projection but cannot be promoted into authoritative KKS ordering.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
The public temporal-authority conformance suite freezes KKS basis, KaiSigil proof…
The public temporal-authority conformance suite freezes KKS basis, KaiSigil proof binding, strict monotonicity, and Chronos subordination.
Technical and authority boundary
The public temporal-authority conformance suite freezes KKS basis, KaiSigil proof binding, strict monotonicity, and Chronos subordination.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- The public temporal-authority conformance suite freezes KKS basis, KaiSigil proof binding, strict monotonicity, and Chronos subordination.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Every attestation event binds fresh Receiz ID/PBI authorship over its…
Every attestation event binds fresh Receiz ID/PBI authorship over its exact payload and prior head.
Technical and authority boundary
Every attestation event binds fresh Receiz ID/PBI authorship over its exact payload and prior head.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Every attestation event binds fresh Receiz ID/PBI authorship over its exact payload and prior head.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Actor roles bind to an authorized domain/capability grantor
Actor roles bind to an authorized domain/capability grantor; a subject cannot self-author a role and call it authorization.
Technical and authority boundary
Actor roles bind to an authorized domain/capability grantor; a subject cannot self-author a role and call it authorization.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Actor roles bind to an authorized domain/capability grantor; a subject cannot self-author a role and call it authorization.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Referenced evidence proof objects must verify their subject, custody, content…
Referenced evidence proof objects must verify their subject, custody, content, and verifier bindings before they count.
Technical and authority boundary
Referenced evidence proof objects must verify their subject, custody, content, and verifier bindings before they count.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Referenced evidence proof objects must verify their subject, custody, content, and verifier bindings before they count.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Application material cannot originate after application creation
Application material cannot originate after application creation; supplemental evidence cannot move backward or arrive after its event.
Technical and authority boundary
Application material cannot originate after application creation; supplemental evidence cannot move backward or arrive after its event.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Application material cannot originate after application creation; supplemental evidence cannot move backward or arrive after its event.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Evaluation, review, approval, issuance, renewal, replacement, suspension, and revocation obey…
Evaluation, review, approval, issuance, renewal, replacement, suspension, and revocation obey exact causal coordinates and deadlines.
Technical and authority boundary
Evaluation, review, approval, issuance, renewal, replacement, suspension, and revocation obey exact causal coordinates and deadlines.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Evaluation, review, approval, issuance, renewal, replacement, suspension, and revocation obey exact causal coordinates and deadlines.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Grant revocation is a coordinated append with an effective Kai/head…
Grant revocation is a coordinated append with an effective Kai/head, so valid historical events remain verifiable while later unauthorized use fails.
Technical and authority boundary
Grant revocation is a coordinated append with an effective Kai/head, so valid historical events remain verifiable while later unauthorized use fails.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Grant revocation is a coordinated append with an effective Kai/head, so valid historical events remain verifiable while later unauthorized use fails.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Successor issuance binds the exact predecessor lifecycle append rather than…
Successor issuance binds the exact predecessor lifecycle append rather than only a credential identifier. These are general primitives for any domain. They are not a custom authority for one verifier, institution, or use case.
Technical and authority boundary
Successor issuance binds the exact predecessor lifecycle append rather than only a credential identifier. These are general primitives for any domain. They are not a custom authority for one verifier, institution, or use case.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Successor issuance binds the exact predecessor lifecycle append rather than only a credential identifier. These are general primitives for any domain. They are not a custom authority for one verifier, institution, or use case.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Known verified profile, Showcase, media, history, identity, wallet, market, and…
Known verified profile, Showcase, media, history, identity, wallet, market, and World truth paints immediately.
Technical and authority boundary
Known verified profile, Showcase, media, history, identity, wallet, market, and World truth paints immediately.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Known verified profile, Showcase, media, history, identity, wallet, market, and World truth paints immediately.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
A locally sealed append is visible immediately and remains the…
A locally sealed append is visible immediately and remains the same object when global synchronization accepts it.
Technical and authority boundary
A locally sealed append is visible immediately and remains the same object when global synchronization accepts it.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- A locally sealed append is visible immediately and remains the same object when global synchronization accepts it.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Server synchronization appends verified additions
Server synchronization appends verified additions; it does not replace, remount, or rehydrate already-held truth.
Technical and authority boundary
Server synchronization appends verified additions; it does not replace, remount, or rehydrate already-held truth.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Server synchronization appends verified additions; it does not replace, remount, or rehydrate already-held truth.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Identity genesis is selected from the earliest verified Identity Record/Seal…
Identity genesis is selected from the earliest verified Identity Record/Seal coordinate, never filenames or presentation claims.
Technical and authority boundary
Identity genesis is selected from the earliest verified Identity Record/Seal coordinate, never filenames or presentation claims.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Identity genesis is selected from the earliest verified Identity Record/Seal coordinate, never filenames or presentation claims.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Extra identity events remain available to continuity logic without flooding…
Extra identity events remain available to continuity logic without flooding the public Showcase.
Technical and authority boundary
Extra identity events remain available to continuity logic without flooding the public Showcase.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Extra identity events remain available to continuity logic without flooding the public Showcase.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Creation Sigils preserve their original Kai pulse across legacy recovery…
Creation Sigils preserve their original Kai pulse across legacy recovery, profile inspection, wallet surfaces, and World previews.
Technical and authority boundary
Creation Sigils preserve their original Kai pulse across legacy recovery, profile inspection, wallet surfaces, and World previews.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Creation Sigils preserve their original Kai pulse across legacy recovery, profile inspection, wallet surfaces, and World previews.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Live-player and proof-media shells preserve visual continuity, including exact dark…
Live-player and proof-media shells preserve visual continuity, including exact dark wide-screen backgrounds.
Technical and authority boundary
Live-player and proof-media shells preserve visual continuity, including exact dark wide-screen backgrounds.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Live-player and proof-media shells preserve visual continuity, including exact dark wide-screen backgrounds.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Settlement is spendable proof-native Phi
Settlement is spendable proof-native Phi. Reserve remains the named legacy funded rail.
Technical and authority boundary
Settlement is spendable proof-native Phi. Reserve remains the named legacy funded rail.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Settlement is spendable proof-native Phi. Reserve remains the named legacy funded rail.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Existing eligible public sealed Showcase artifacts are recognized at already-accrued…
Existing eligible public sealed Showcase artifacts are recognized at already-accrued deterministic value. Activation is not a mint, bonus, multiplier, or backfill.
Technical and authority boundary
Existing eligible public sealed Showcase artifacts are recognized at already-accrued deterministic value. Activation is not a mint, bonus, multiplier, or backfill.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Existing eligible public sealed Showcase artifacts are recognized at already-accrued deterministic value. Activation is not a mint, bonus, multiplier, or backfill.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Anyone can recompute the exact value of any sealed Showcase…
Anyone can recompute the exact value of any sealed Showcase proof object at any admitted Kai moment from the verified object, verified coordinate, frozen projector digest, and integer rounding rule. No database or institutional price assertion is required.
Technical and authority boundary
Anyone can recompute the exact value of any sealed Showcase proof object at any admitted Kai moment from the verified object, verified coordinate, frozen projector digest, and integer rounding rule. No database or institutional price assertion is required.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Anyone can recompute the exact value of any sealed Showcase proof object at any admitted Kai moment from the verified object, verified coordinate, frozen projector digest, and integer rounding rule. No database or institutional price assertion is required.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Lawful-action value is ((completionKai - startKai) + 1) × ((valuationKai…
Lawful-action value is ((completionKai - startKai) + 1) × ((valuationKai - completionKai) + 1) micro-Phi.
Technical and authority boundary
Lawful-action value is ((completionKai - startKai) + 1) × ((valuationKai - completionKai) + 1) micro-Phi.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Lawful-action value is ((completionKai - startKai) + 1) × ((valuationKai - completionKai) + 1) micro-Phi.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
One artifact has one spendable membership
One artifact has one spendable membership. Custody moves that membership while provenance and witness history remain.
Technical and authority boundary
One artifact has one spendable membership. Custody moves that membership while provenance and witness history remain.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- One artifact has one spendable membership. Custody moves that membership while provenance and witness history remain.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Sender and receiver independently verify the exact sealed transition at their edges
Sender and receiver independently verify the exact sealed transition at their edges. Hosted infrastructure provides additive global synchronization and conflict serialization only.
Technical and authority boundary
Sender and receiver independently verify the exact sealed transition at their edges. Hosted infrastructure provides additive global synchronization and conflict serialization only.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Sender and receiver independently verify the exact sealed transition at their edges. Hosted infrastructure provides additive global synchronization and conflict serialization only.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
@receiz/sdk@125.0.0
@receiz/sdk@125.0.0: the full runtime, verifier, application compiler, attestation/credential primitives, KKS temporal authority, edge value, local proof memory, and conformance interfaces.
Technical and authority boundary
@receiz/sdk@125.0.0: the full runtime, verifier, application compiler, attestation/credential primitives, KKS temporal authority, edge value, local proof memory, and conformance interfaces.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- @receiz/sdk@125.0.0: the full runtime, verifier, application compiler, attestation/credential primitives, KKS temporal authority, edge value, local proof memory, and conformance interfaces.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
@receiz/mcp-server@125.0.0
@receiz/mcp-server@125.0.0: trusted-host tools that expose opaque proof references, await transport results, and report non-success HTTP responses as MCP errors.
Technical and authority boundary
@receiz/mcp-server@125.0.0: trusted-host tools that expose opaque proof references, await transport results, and report non-success HTTP responses as MCP errors.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- @receiz/mcp-server@125.0.0: trusted-host tools that expose opaque proof references, await transport results, and report non-success HTTP responses as MCP errors.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
@receiz/ai-skills@125.0.0
@receiz/ai-skills@125.0.0: 42 operating skills that preserve the same authority hierarchy without granting model output proof authority.
Technical and authority boundary
@receiz/ai-skills@125.0.0: 42 operating skills that preserve the same authority hierarchy without granting model output proof authority.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- @receiz/ai-skills@125.0.0: 42 operating skills that preserve the same authority hierarchy without granting model output proof authority.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Versioned HTTP, OpenAPI, OIDC/CORS, browser, Node, serverless, device-local, database-backed, game/world…
Versioned HTTP, OpenAPI, OIDC/CORS, browser, Node, serverless, device-local, database-backed, game/world, chain-anchored, agent, and institutional implementations receive the same law.
Technical and authority boundary
Versioned HTTP, OpenAPI, OIDC/CORS, browser, Node, serverless, device-local, database-backed, game/world, chain-anchored, agent, and institutional implementations receive the same law.
- Why
- The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
- Capability enabled
- Versioned HTTP, OpenAPI, OIDC/CORS, browser, Node, serverless, device-local, database-backed, game/world, chain-anchored, agent, and institutional implementations receive the same law.
- Compatibility
- The v125.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v125.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
The relevant law is explicit and executable. An append binds its exact predecessor. Its temporal coordinate is a proof-bearing KKSv1.0/KaiSigil coordinate. A bare number, server timestamp, createdAt, database insertion time, or model assertion cannot become Kai authority.
Available outcomes
Capabilities now available
A Kai coordinate is accepted as authority only through the…
A Kai coordinate is accepted as authority only through the proof-bearing KKS/KaiSigil boundary; a decimal string is not enough.
Live coordinates advance from a retained monotonic head, including multiple…
Live coordinates advance from a retained monotonic head, including multiple appends inside one millisecond and backward wall-clock movement.
createdAt and every other Chronos field are descriptive bridges derived from Kai
createdAt and every other Chronos field are descriptive bridges derived from Kai. They never order proof history.
Legacy Chronos material remains available as a compatibility projection but…
Legacy Chronos material remains available as a compatibility projection but cannot be promoted into authoritative KKS ordering.
The public temporal-authority conformance suite freezes KKS basis, KaiSigil proof…
The public temporal-authority conformance suite freezes KKS basis, KaiSigil proof binding, strict monotonicity, and Chronos subordination.
Every attestation event binds fresh Receiz ID/PBI authorship over its…
Every attestation event binds fresh Receiz ID/PBI authorship over its exact payload and prior head.
Actor roles bind to an authorized domain/capability grantor
Actor roles bind to an authorized domain/capability grantor; a subject cannot self-author a role and call it authorization.
Referenced evidence proof objects must verify their subject, custody, content…
Referenced evidence proof objects must verify their subject, custody, content, and verifier bindings before they count.
Application material cannot originate after application creation
Application material cannot originate after application creation; supplemental evidence cannot move backward or arrive after its event.
Evaluation, review, approval, issuance, renewal, replacement, suspension, and revocation obey…
Evaluation, review, approval, issuance, renewal, replacement, suspension, and revocation obey exact causal coordinates and deadlines.
Grant revocation is a coordinated append with an effective Kai/head…
Grant revocation is a coordinated append with an effective Kai/head, so valid historical events remain verifiable while later unauthorized use fails.
Successor issuance binds the exact predecessor lifecycle append rather than…
Successor issuance binds the exact predecessor lifecycle append rather than only a credential identifier. These are general primitives for any domain. They are not a custom authority for one verifier, institution, or use case.
Known verified profile, Showcase, media, history, identity, wallet, market, and…
Known verified profile, Showcase, media, history, identity, wallet, market, and World truth paints immediately.
A locally sealed append is visible immediately and remains the…
A locally sealed append is visible immediately and remains the same object when global synchronization accepts it.
Server synchronization appends verified additions
Server synchronization appends verified additions; it does not replace, remount, or rehydrate already-held truth.
Identity genesis is selected from the earliest verified Identity Record/Seal…
Identity genesis is selected from the earliest verified Identity Record/Seal coordinate, never filenames or presentation claims.
Extra identity events remain available to continuity logic without flooding…
Extra identity events remain available to continuity logic without flooding the public Showcase.
Creation Sigils preserve their original Kai pulse across legacy recovery…
Creation Sigils preserve their original Kai pulse across legacy recovery, profile inspection, wallet surfaces, and World previews.
Live-player and proof-media shells preserve visual continuity, including exact dark…
Live-player and proof-media shells preserve visual continuity, including exact dark wide-screen backgrounds.
Settlement is spendable proof-native Phi
Settlement is spendable proof-native Phi. Reserve remains the named legacy funded rail.
Existing eligible public sealed Showcase artifacts are recognized at already-accrued…
Existing eligible public sealed Showcase artifacts are recognized at already-accrued deterministic value. Activation is not a mint, bonus, multiplier, or backfill.
Anyone can recompute the exact value of any sealed Showcase…
Anyone can recompute the exact value of any sealed Showcase proof object at any admitted Kai moment from the verified object, verified coordinate, frozen projector digest, and integer rounding rule. No database or institutional price assertion is required.
Lawful-action value is ((completionKai - startKai) + 1) × ((valuationKai…
Lawful-action value is ((completionKai - startKai) + 1) × ((valuationKai - completionKai) + 1) micro-Phi.
One artifact has one spendable membership
One artifact has one spendable membership. Custody moves that membership while provenance and witness history remain.
Sender and receiver independently verify the exact sealed transition at their edges
Sender and receiver independently verify the exact sealed transition at their edges. Hosted infrastructure provides additive global synchronization and conflict serialization only.
@receiz/sdk@125.0.0
@receiz/sdk@125.0.0: the full runtime, verifier, application compiler, attestation/credential primitives, KKS temporal authority, edge value, local proof memory, and conformance interfaces.
@receiz/mcp-server@125.0.0
@receiz/mcp-server@125.0.0: trusted-host tools that expose opaque proof references, await transport results, and report non-success HTTP responses as MCP errors.
@receiz/ai-skills@125.0.0
@receiz/ai-skills@125.0.0: 42 operating skills that preserve the same authority hierarchy without granting model output proof authority.
Versioned HTTP, OpenAPI, OIDC/CORS, browser, Node, serverless, device-local, database-backed, game/world…
Versioned HTTP, OpenAPI, OIDC/CORS, browser, Node, serverless, device-local, database-backed, game/world, chain-anchored, agent, and institutional implementations receive the same law.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- media
- verification
- public-witness
- local-truth
- continuity
- market
- reserve
- sealed-artifact
- governance
Compatibility
Compatibility
Sealed proof objects
Verify the enclosing artifact before extracting or trusting any embedded payload
This exact v125.0.0 compatibility boundary remains binding.
Kai / KKS
Proof-bearing KKSv1.0/KaiSigil coordinates and exact prior heads order authoritative appends
This exact v125.0.0 compatibility boundary remains binding.
Chronos
Human-readable projection derived from Kai
This exact v125.0.0 compatibility boundary remains binding.
Identity genesis
Earliest verified Identity Record/Seal Kai coordinate wins
This exact v125.0.0 compatibility boundary remains binding.
Creation Sigil
Projects the admitted original creation coordinate across profile, wallet, and World
This exact v125.0.0 compatibility boundary remains binding.
Durable local truth
First admission only, then append forever; known proof paints immediately
This exact v125.0.0 compatibility boundary remains binding.
Global synchronization
Append, compare-and-swap, distribution, indexing, replay, and recovery
This exact v125.0.0 compatibility boundary remains binding.
Attestation roles
Authorized grantor binds the role; each event carries fresh actor proof
This exact v125.0.0 compatibility boundary remains binding.
Evidence
Referenced proof objects are opened and verified before counting
This exact v125.0.0 compatibility boundary remains binding.
Credential lifecycle
Deadline, predecessor lifecycle head, actor proof, evidence, and Kai causality are required
This exact v125.0.0 compatibility boundary remains binding.
Settlement
Spendable proof-native Phi projected from sealed proof
This exact v125.0.0 compatibility boundary remains binding.
Reserve
Named legacy funded rail
This exact v125.0.0 compatibility boundary remains binding.
Custody
One current owner, one spendable membership
This exact v125.0.0 compatibility boundary remains binding.
SDK / MCP / AI Skills
Coordinated exact 125.0.0 graph; compatibility range >=125.0.0 <126.0.0
This exact v125.0.0 compatibility boundary remains binding.
HTTP / OIDC / CORS
Versioned lawful-action routes bind application identity and registered redirect origins
This exact v125.0.0 compatibility boundary remains binding.
Error semantics
Every non-2xx HTTP response rejects in SDK and MCP
This exact v125.0.0 compatibility boundary remains binding.
Public proof surfaces
Known identity, ownership, media, and history paint without weaker hydration
This exact v125.0.0 compatibility boundary remains binding.
Release evidence
Package, database, deployment, Git, Docs, and attestation facts are recorded separately
This exact v125.0.0 compatibility boundary remains binding.
Migration
Migration
Required: true
The SDK/MCP SQL compatibility migration is required only for hosts that applied the September 5 rollback. Production applied 20260905164450v125lawfulactiontransportrestore.sql: it restores the existing law-registration, action-admission, value-append and lawful-value-reader functions. It preserves stored source history and does not restore profile/PBI, creator, temporal-allocation or wallet-publication prerequisites. Do not replay the eight historical migrations below. See the [verified SQL record](v125.0.0-sql-compatibility-verification.json).
- Install the exact coordinated 125.0.0 packages.
- Verify or seal the enclosing proof object before using any embedded material.
- Admit proof-bearing KKS coordinates, not bare pulse strings.
- Register a lawful-action law once with a stable idempotency key.
- Admit completed actions against the expected prior admission digest.
- Derive value heads from the expected prior value-head digest; never submit an amount or valuation Kai.
- Commit and verify sender/receiver transitions at their edges; use hosting only for additive global synchronization.
Qualification
Conformance
Temporal-authority conformance ships through SDK, MCP, and AI documentation.
Passed · Temporal-authority conformance ships through SDK, MCP, and AI documentation.
The September 4 candidate production build compiled, typechecked, generated 276 static pages, and completed build tracing.
Passed · The September 4 candidate production build compiled, typechecked, generated 276 static pages, and completed build tracing.
The September 4 runnable release-freeze code, first-paint, continuity, conformance, package, performance, governance-check, and governance-signature gates passed; its aggregate failed cadence.
Passed · The September 4 runnable release-freeze code, first-paint, continuity, conformance, package, performance, governance-check, and governance-signature gates passed; its aggregate failed cadence.
The September 5 exercise records isolated SQL behavior tests passing 2/2; the September 4 unavailable result remains historical.
Passed · The September 5 exercise records isolated SQL behavior tests passing 2/2; the September 4 unavailable result remains historical.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Governance verification passed against the exact checked release evidence bound below.
No separate release approval reference or risk-owner assignment is inferred from conformance evidence.
Registry boundary
Registry
- Version
- 125.0.0
- Digest
85a24c3a7fe144c8ec03c6b5fae238d1dfda64c1ed3091b24d4264dc3862ff17- Predecessor
d02429151b0bcebdaeb89485792e377afc55130f9a25e07982c1c88221314247
Archive projection
Audience, domain, and change-kind facets
- Audiences
- Not established
- Domains
- Not established
- Change kinds
- Not established
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Confirmed
- Deployment
- Confirmed
- Production smoke
- Unknown
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 50184a74deb11153ac992f07faa140e275793fdf3645e10a17397ab630c661e8. Source-family inventory: complete.
SHA-256 203c3330d562b5ff7d39c7a85b799196cb89dddf332318ad1d1c44183cbca6e6SHA-256 4ca33c2368ddffe8d74c872af1982a8d742ae86ef64a37c34502fe491771e286SHA-256 18007b09f8d43166e1c2f0ee8c8bc547a8b6327d7b65145e4e36d0119540da72SHA-256 8d32617778de77bac132be50eea17ca3d560ad65e98ecc7b90bbde4a393487cfSHA-256 e9962003c10bc58181a37f65022c6a09f8bf1e1e5934b4b897edc0a5897e0991SHA-256 c9a6f64513a4d420ac3172c200ece0ff75866b0e0e9795a39fc80101c42556a9SHA-256 dfa004f3128287a43cf218c7c756f43b154127e84a0f53b14fd315f9d99a3026SHA-256 3a49264ecfac8a10088717bb65c2847c07606d8cb7ae18191d25024766a1795bSHA-256 2419f6f8f2d7a1d856a662258fadb2e21198fb137294e2a389481dda567767a9SHA-256 a09968a78aae44d7ed6a6bd57c3dffce1801785e7410dbc41a5ce65dd613757dSHA-256 c764db3f4b41c616df79fee682b4df71b1d546cc2aaaa36543378012b164f70eSHA-256 3895803d514d220d944813cd68325809b965e0de0b7a1a21e3a82c8fb412e2c5SHA-256 87de170312cc1890304af11b1d669479dc6c2103179fa39c4f3b8f4045c73035SHA-256 0096e55d0c73dd85f4d27ce7af9ecfc06699a5e99967f77d700bba47bd233c8bSHA-256 202ead85f2295e2e2dd6621dca762be6d3bda50bf35bbd9fe275aac26610148bSHA-256 a6144c2efecf68020e6e94407b5773e06201f5c9f9ac27d410a938288820ced5SHA-256 84a411f5ee03a53062939ad2fda591a3cb68c8a3850f7ba69a167ec7a396465aSHA-256 f2f6750e348afe8c19b699eb1b2b2814e97f7af6c94bad6a28477438cb5ad835SHA-256 2c14ae6e93a3ab2add66337fd692abf5f93a8441285118f664d7957eeda6905aSHA-256 cf1a2b391627d771e16ea7dc44ae883b2fb55434ccd1ab8ac6d7429fcfb52ac4SHA-256 eb00b51ef5fcd46e39969d9474db67b4d41fb0c534aa91f3de73a49630d372dbSHA-256 a80bd7523acbdf21038df1bab8080f484fbe8d774f751f69fd8d346425ff8a1eSHA-256 a6db0f1fd767b9b9ee2683832a2554bbbcceabf6489cf28a0ffd5d7efdfb3755SHA-256 31fc29df8700582510f472cc04a466704c176925aab6879e73e9028bccfee1e4SHA-256 8038af8f1a081d3a790f2c3e5f6be2d5043083d47dce62044a590d1f237535c3SHA-256 74ae9452d3e9da6adcf80ba276478e8f539ad37fbaee94ca2792838ff5a608cbSHA-256 cae13779f6d38c40a19b443a34f62b5eb427175ac89123a1da7e173582706983SHA-256 118e08ded4218c9a57e8c672f6ec765687e6fe46875ee6b52b06b3f68bc7e7d1SHA-256 90e44885778893da206b02bfb2f5d5bea905be29ce7bf24b4ecbfd867b29e960