Operate / Identity operators and account owners

Identity continuity

Recover and bind identity while preserving the distinction between account proof, local device identity, and session mechanics.

identity continuityReceiz ID and account recovery mechanicsComplete production checklist

Implementation rail · Receiz ID and account recovery mechanics

Exact execution and operator checks

01
Operator check
Hold accepted identity proof
Hold the complete PBI, passkey, Identity Record, Identity Seal, or Receiz Key proof and name its local device, account, key, replay, and recovery boundaries.
Substantive records: /learn/primitive-atlas · /reference/sdk
Expected: Accepted proof is available before session or server projection.
02
Exact mechanic
Publish signed Receiz ID proof
```
curl --fail-with-body --request POST "https://receiz.com/api/auth/receiz-id/continue"   --header "content-type: application/json"   --data "${RECEIZ_ID_CONTINUE_JSON:?RECEIZ_ID_CONTINUE_JSON is required}"
```
Mechanic
POST /api/auth/receiz-id/continue
Authentication and account boundary
No Auth
Exact source
receiz-docs/generated/openapi-reference.json · SHA-256 2278eb9ab1dfcc90d61d4a6f9daac1bc55e17aeeab0d2d5d39228f88654bc20a
Expected: The endpoint accepts signed key proof or returns an exact rejection; it does not manufacture identity proof.
03
Exact mechanic
Run test:identity-conformance
```
pnpm test:identity-conformance
```
Mechanic
pnpm test:identity-conformance
Authentication and account boundary
Authorized local repository checkout; the command proves only the checked repository boundary.
Exact source
package.json · SHA-256 132f99232dfaf26f7186b73752938d1377042808f42d60d374fe7b2e57c7646b
Expected: Invalid, revoked, replayed, bind, recovery, and projection contracts pass.
04
Operator check
Confirm immediate projection and synchronized binding
Confirm accepted local proof projects the recovered account immediately, then confirm online bind is idempotent and cannot restore the prior account.
Substantive records: /trust/hierarchy · /operate/key-custody-rotation-recovery
Expected: Local continuity is immediate; remote binding and session state remain weaker synchronized projections.

Complete operating anatomy

Every boundary required to ship.

Solved outcome: Accepted PBI, passkey, Identity Record, Identity Seal, or Receiz Key proof projects the recovered identity immediately and synchronizes an idempotent remote binding when available.
Prerequisites: Hold accepted identity proof, key ID and public material, local device identity, recovered account identity, replay boundary, bind operation identity, optional session issuance boundary, and recovery custody.
Exact primitive: identity continuity
Governing law: Identity continuity is governed by identity-boundary: Binding appends identity continuity. Accepted identity proof remains intact. identity-conformance: A passing execution confirms the checked identity continuity invariants for the exact repository state exercised. literal-product-law: Implemented primitives are named directly, stronger truth remains above weaker projections, and a contradiction is release-blocking.
Source-of-truth order: Receiz law → sealed artifact truth → deterministic proof object state → verified durable local or register truth → authenticated snapshot → server distribution, synchronization, indexing, and publication → database, session, observability, and interface projections.
Expected artifact, receipt, or state: A locally admitted identity binding and, when online, its synchronized idempotent remote binding; session state remains a weaker projection.
Inspection: Inspect the identity proof, key ID, recovered account binding, active account projection, and sync status. Inspection exposes structure and receipt fields; inspection never establishes verification.
Independent verification: Independent verification for identity-continuity: pnpm test:identity-conformance. This establishes only the identity continuity boundary named by the bound sources; Receiz ID and account recovery mechanics do not become proof authority.
Offline behavior: Accepted local proof projects immediately. Remote binding, wallet, ledger, and profile synchronization enrich later and cannot restore the prior account.
Identity and account boundary: Public Record Moment, Seal File, Verify, Export, and public proof reading are account-free. Identity is optional and adds continuity, custody, recovery, and governed private controls after proof admission.
Security boundary: Session issuance uses fresh proof and replay protection where required; idempotent binding never depends on Redis availability.
Conformance command: pnpm test:identity-conformance
Deployment checks: Qualify invalid and revoked proof rejection, replay protection, immediate local projection, idempotent server bind without Redis dependency, fresh recovered-account session issuance, prior-account exclusion, offline restore, and background synchronization of verified additions.
Production checklist: Test PBI, passkey, Identity Record, Identity Seal, and Receiz Key acceptance; invalid, revoked, replayed, and wrong-account proof; Redis outage during bind; fresh cookie issuance; offline projection; reconnect; and prior-account non-restoration.
Rollback and containment: Containment for identity-continuity: Recovery and binding are rejected. Obtain accepted proof for the intended identity. The replayed issuance is rejected. Issue and consume fresh proof through the session path. Identity continuity projection is wrong. Project the recovered identity immediately and synchronize bind, wallet, ledger, and profile projections later. Any true history change must be a separately verified successor or verified register addition against the exact current head. Preserve every stronger held artifact and admitted state while the named boundary is corrected.

Fail closed

Mutation and failure matrix

Identity proof is invalid, revoked, or bound to another account.

Effect: Recovery and binding are rejected.
Retry: Never downgrade to session or database assertion.
Recovery: Obtain accepted proof for the intended identity.

A login proof or session issuance token is replayed.

Effect: The replayed issuance is rejected.
Retry: Do not bypass replay protection.
Recovery: Issue and consume fresh proof through the session path.

Binding succeeds but the prior account or half-logged-in interface remains.

Effect: Identity continuity projection is wrong.
Retry: Do not wait on weaker sync to repair first paint.
Recovery: Project the recovered identity immediately and synchronize bind, wallet, ledger, and profile projections later. Any true history change must be a separately verified successor or verified register addition against the exact current head.

Exact authority

Claim-to-source bindings

Binding appends identity continuity. Accepted identity proof remains intact.
docs/pbi-recovery-receiz-id-binding.mdnormative-doctrine · SHA-256 f6e6e4177f6340924e59042d2f976dd4f6666340d80c0f1cee8b0f4180cea264
A passing execution confirms the checked identity continuity invariants for the exact repository state exercised.
scripts/test_identity_conformance.tsexecutable-conformance · SHA-256 699508b94d317a4d1ff1bae527b49e76e3dfda8f7e085316e9729b9afa23e36f
Implemented primitives are named directly, stronger truth remains above weaker projections, and a contradiction is release-blocking.
docs/literal-product-law.mdnormative-doctrine · SHA-256 5548a8f32bbdf35f2ba5e4545cd31ef6e2842d2c3127a3e39e10e6eb6bc5efa1

One complete system

Exact execution and operator checks

Hold accepted identity proof

Publish signed Receiz ID proof

Run test:identity-conformance

Confirm immediate projection and synchronized binding