Receiz · Reality Grade Infrastructure

Proof you can check. History you do not lose. One original, new experiences.

This repository freezes the public claims, compositional ontology, deterministic laws and evidence for the v126 disclosure boundary. Build through the SDK and documentation, explore 1,348 capabilities, and verify the disclosed evidence locally.

One underlying ontology

Primitives → Relations → Invariants → Laws → Operations → Capabilities → Experiences

Receiz capabilities compose from shared primitives governed by invariant relations and deterministic transition laws. A proof object carries its source; identity binds an actor; Kai orders changes; verified appends preserve transitions; carried memory lets another experience continue from the held history.

Inspect the frozen ontology and counting scope · Read the 133-law registry · Inspect all ten captured conformance reports

Verify this disclosure

npm ci --ignore-scripts
npm test
npm run verify:release
npm run conformance:sdk

The release verifier checks the owner-designated Receiz identity source, carried governance history and exact disclosed file inventory. It rejects altered bytes, substituted owners and unsupported release envelopes. Installing dependencies requires transport; verification of held package and release bytes runs locally. A GitHub badge is not release authority.

Build on the primitives

Integration guide · Full documentation · Capability directory · Public interfaces

The offline-verifier v126 release and immutable product history provide product continuity. This disclosure has its own release boundary; it does not rewrite that history.

Audit scope

This is a disclosure of contracts, evidence and read-only audit tools. It is not the proprietary application runtime or a full private-code audit. Hosted conformance reports retain their individual revision identities; their capture is not an independent rerun. The original preparation inventory remains under disclosure/ as historical evidence and does not authenticate this release.

See release scope, license, and security reporting. No private identity, signer secret, deployment credential, database data or proprietary application runtime is included.