v114.0.0

Receiz v114.0.0

Release-candidate date: 2026-07-27

Receiz v114.0.0 makes the profile showcase itself a sealed composite proof object and applies the same recursive law to the global economy showcase. A post no longer becomes globally complete because a database row or display projection exists. The accepted profile successor is the authority; the economy appends that exact admitted profile proof object; Market is a digest-bound projection beneath the economy proof.

Release baseline: v113.5.0 (8f081b1eeee10c2cb9445686116d5120828cfe1a). ddd66cd59 records the first fixed-code release-candidate checkpoint; the final release tree additionally includes the review-closure changes documented below.

Durable proof memory remains first admission only, then append forever.

The Architectural Correction

The profile showcase has stable proof identity profile-showcase:<Receiz ID>. Every accepted state is itself a sealed successor proof object. The successor carries one bounded direct delta, the exact predecessor commitment, compact Merkle frontier state, sparse Fibonacci checkpoints, immutable segment references, a carried history head, and a sealed first-paint window.

The economy uses the same law one level higher under stable proof identity economy-showcase:receiz.com. It appends exact admitted profile showcase heads, not re-discovered profile arrays. Each economy successor binds the admitted profile artifact digest, version, carried-history head, and admission-evidence root. Market derives from that verified economy state.

This is the same recursive operation from one Original to one profile, from profiles to the economy, and from the economy to deterministic public projection:

1. verify the stronger enclosing proof object
2. admit its exact identity and carried history
3. append one bounded proof delta
4. seal the resulting composite as the next proof object
5. project beneath the sealed result
6. reconcile verified additions without re-finding known truth

Merkle roots, Fibonacci checkpoints, IndexedDB indexes, database rows, session state, published manifests, and Market snapshots remain mechanics or projections. None becomes authority above the sealed proof object.

Posting and Composer Settlement

• The composer preserves the existing anchor, render, seal, upload, and publication ritual.
• A successfully sealed Original is admitted as an exact profile child before the profile successor is constructed.
• Identity Record custody supplies the exact actor authority required to seal the profile transition.
• Identity Record exports forward their passphrase into custody instead of silently storing an unusable record.
• Receiz Key restores admit the accepted Identity Record into the same custody used by newly created identities.
• Composer publication no longer silently skips a showcase append when custody is unavailable. It reopens persisted custody or reports an explicit proof-settlement failure.
• A new browser must migrate the complete admitted legacy showcase before it may append. It cannot manufacture an empty genesis that erases earlier Originals.
• Migration uses the complete owner showcase, including already-hidden Originals. Hidden child proof truth remains in sealed custody while the public first-paint projection remains visible-only.
• Once the profile successor is admitted, it is durably queued into the browser economy. Transient economy failure is retained for retry instead of being discarded.

Local sealed settlement remains true when a weaker projection or global synchronization path is unavailable. The weaker failure cannot revoke the accepted proof object.

Deterministic First Paint

• A verified held profile head paints before network discovery, database reconstruction, session lookup, or global synchronization.
• Profile projection preserves the verified visibleChildren placement order exactly; derivative createdAt timestamps cannot undo a sealed reorder or merge.
• A verified held economy head paints its digest-bound Market projection before weaker refresh work.
• The bounded first-paint window reuses already admitted proof truth; pages do not rescan complete profile history to recover facts they already hold.
• Successor admission reuses already-verified child and segment custody for unchanged window members. It verifies the new direct delta without re-proving or dropping settled predecessors.
• Missing edge custody does not blank stronger server-rendered public truth.
• A held bounded head cannot replace the route with an incomplete or unverified child projection.
• Visibility transitions quarantine a known-stale bounded predecessor before the database write. First paint may not resurrect a hidden Original while the exact sealed successor is still being produced.
• The quarantine is released only after the visibility successor is sealed, admitted, published, and enqueued.
• A definitive rejected visibility request, including insufficient Settlement, cancels its transition marker so rejected work cannot suppress the last verified first paint.
• An ambiguous fetch rejection remains in durable transition custody and is replayed on reconnect or the next bounded route read; an in-memory held projection cannot bypass that quarantine.
• Every server-affected sibling receives its own transition marker before any sibling settles. The showcase remains quarantined until the complete batch has sealed.
• Visibility recovery admits either creator/current-owner custody or an exact verified-possession receipt bound to the Original slug, code, Kai pulse, and anchor ID.

No first-paint path waits for economy retries, migration, profile reconstruction, or session rediscovery.

Scale and Storage

Foreground profile and economy appends are bounded by the compact head and the one new delta, not by the total number of prior posts or users.

The executable scale contracts prove:

• a bounded append after 100,000 profile children
• a bounded append after 1,000,000 profile children
• a bounded economy append after 1,000,000 admitted profile heads
• one direct delta operation, bounded Merkle carry work, sparse Fibonacci checkpoint work, one coordination write, and one derivative effect
• no artifact bytes, private URLs, credentials, or full historical arrays in scale metrics

The physical archive-compaction soak remains a separate linear maintenance operation. It is not part of first paint or the foreground posting contract.

Receiz can therefore store, reopen, project, and extend million-object proof state without treating a database as proof authority. Database and object-storage services remain useful for subordinate coordination, discovery, transport, and projection, but the proof object carries the settled truth.

Economy Concurrency and Recovery

• Economy head advancement uses compare-and-advance semantics.
• The first economy append bootstraps atomically from a null active pointer even when a verified genesis or legacy sealed head already exists.
• Later appends compare the exact active digest against their predecessor.
• Overlapping sibling appends cannot silently replace one another. Conflicts retry or enter verified merge/reconciliation.
• Recovered historical economy members require sealed history or membership evidence; count and direct-child checks alone are insufficient.
• Market projection selects the newest verified descendant for each stable profile identity rather than retaining the first historical version.
• Projection rebuild remains exact-digest and derivative.

Visibility, Signed Originals, and Public Projection

• Signing an already-published Original refreshes the canonical public and Market projections.
• Stable signed-artifact download routes are persisted instead of expiring signed URLs.
• Hide and re-show operations update the published projection and append the matching bounded showcase/economy transition.
• Hidden-Original recovery follows pagination rather than assuming the first owner page contains the target.
• A visibility change for an Original inside the sealed legacy-migration composite creates a new sealed composite child with that one projection changed, appends it, and hides the prior composite in the next causal operation. The nested Original is never fabricated as an independent child placement.
• Repeating an already-hidden request is an idempotent successful transition.
• Updating an existing Original preserves canonical creation ordering instead of moving it to the top.
• Composer PNG children are projected through their actual sealed child payload contract; JSON-only test assumptions cannot erase normal published Originals.

Identity Custody and Verification Memory

• Identity custody retains proof authority only for the active accepted session/account.
• Explicit logout clears the held Identity Record key file and passphrase closure.
• Slow legacy custody finalization runs outside successful sign-in navigation.
• Every async custody admission is generation-bound. Logout or a newer admission invalidates the older finalizer, so stale work cannot repopulate cleared signing custody.
• Device-certificate verification and imported Ed25519 key caches are bounded.
• Invalid certificate results are not retained without limit.

These changes preserve the Identity Record as the authority while preventing session mechanics and long-lived runtime memory from extending that authority beyond its accepted boundary.

SDK, Registry, and Compatibility

The committed SDK source and distribution expose the profile showcase persistent state, bounded composite transport, recursive composite kernel, artifact admission, transition authority, profile/economy carriers, migration, projection, custody, and conformance surfaces together.

The deterministic unsigned v114 registry is:

• artifact: docs/releases/v114.0.0-constitution-registry.json
• digest: ae912154d97b695464c3a19361bceb9440bc5d703a1d9129edac92c64192e29a
• previous registry digest: 4c4aa85f9785d205dcf7e4e5109837a83f8c3bf8e166130ae7e87353f299c637
• compatibility interval: >=114.0.0 <115.0.0

The registry adds exact profile-showcase and economy-showcase carriers, append namespaces, reducers, stable identities, effects-derived operations, and carried-history requirements. It does not replace v113 proof objects. Existing sealed artifacts and the v113 coordination rail remain verifiable and unchanged.

At fixed-code head ddd66cd59, the app, SDK, MCP, and verifier package manifests still identify the coordinated distribution as 113.5.0, and the current release identity still points to the frozen v113 ruleset. V114 law is present additively. Coordinated package/runtime promotion to 114.0.0 remains an explicit release action and must move every distribution label, generated artifact, service-worker identity, compatibility contract, and release lock together.

Service Worker and Mobile Continuity

• A waiting service worker activates when the page exits, allowing normal Safari/PWA continuity without replacing a settled visible surface mid-session.
• iOS form zoom/typography corrections preserve reachable composer controls without changing proof logic.
• These browser mechanics remain beneath deterministic first paint and do not remount known truth.

Evidence

Fresh gates from the final release-candidate tree:

• focused migration/visibility/proof suite: 11/11 passing
• focused network-replay, sibling-quarantine, and received-custody visibility suite: 8/8 passing
• focused sealed-order and visibility closure suite: 13/13 passing
• profile release contracts: 130/130 passing
• current profile-showcase suite: passing, including 100,000-child append, verified migration custody, projection outage, and reconciliation cases
• committed SDK suite: passing
• economy conformance: 28/28 requirements and 23/23 checks passing
• TypeScript: passing
• lint: zero errors; 27 unused-symbol warnings remain in test/SDK files
• production build: passing with the existing Groth16 dynamic-dependency warning
• page-first-paint, deterministic-surfaces, primitive-binding, repo-only-reasoning, and visual-evidence contracts: passing

The repository contains v114 Market, Original-proof, and profile first-paint captures. The Market and Original-proof captures confirm settled public proof surfaces. The profile capture confirms the settled identity/shell but does not prove completed media paint. The original composer screenshot showing Could not render the anchored receiz artifact. remains historical failing evidence until a fresh authenticated end-to-end composer capture explicitly contradicts it.

Release Boundary

This release book documents the completed fixed-code candidate. It does not claim that version promotion, signed attestation, package publication, deployment, production migration, or production smoke verification has occurred.

Canonical release records: product truth, checklist, process, regression lessons, commit history, and the profile/economy composite proof record.

Full Changelog: v113.5.0...v114.0.0