Compatibility and version support

Solved outcome

What this enables

Accept current mechanics only when every coordinated surface agrees, while retaining immutable read, verify, and export compatibility for historical proof objects.

Exact form

Signature or request

application source 124.1.0 · coordinated package source 124.1.0 · public package evidence confirms 124.1.0 · ruleset 124.0.0 · supported current range >=124.0.0 <125.0.0 · 53 application operations · 169 MCP tools · six V124.1 capability families

Stable recovery

Failures

Permanent anchor · #compatibility-current-identity

Current identity

Current repository and independently observed public package conformance requires application, SDK, MCP server, AI skills, verifier, V124 registry digest, 53-operation matrix digest, 169-tool MCP registry, six-family capability inventory, and the complete v124 SDK surface to match 124.1.0.

Permanent anchor · #compatibility-version-matrix

Version matrix

Use coordinated source and public packages at 124.1.0 with ruleset 124.0.0 and supported current range >=124.0.0 <125.0.0. Upgrade the three public packages together. Stable v122/v123 wire schemas and method suffixes remain protocol identities. Do not combine current authority-bearing runtime objects across incompatible coordinated identities.

Permanent anchor · #compatibility-registry

Registry

Bind the current registry digest before admission, planning, capability verification, or commit. Registry projection is law input beneath the verified artifact and cannot rewrite historical bytes.

Permanent anchor · #compatibility-operation-matrix

Operation matrix

Bind operation identifiers, input authority, required evidence, output authority, process boundary, namespace policy, and compatible SDK range exactly.

Permanent anchor · #compatibility-historical-artifacts

Historical artifacts

Historical sealed proof objects remain exact-byte readable, verifiable, and exportable. Historical runtime admissions, plans, capabilities, stores, or confirmations do not authorize v124 operations.

Permanent anchor · #compatibility-upgrade-rules

Upgrade rules

Upgrade coordinated mechanics together, preserve immutable historical proof, regenerate projections, and rerun identity, verification, MCP, AI-skill, and release-identity conformance.

Permanent anchor · #compatibility-end-to-end-example

End-to-end example

The universal example compiles against v124 declarations. A future declaration change must fail the compile contract before published code can drift.

Copyable path

Authenticated SDK issuance → Verify → inspect receipt

import { createReceizClient } from "@receiz/sdk";

// Begin with the complete proof object already held by the person or runtime.
const encoded = process.env.RECEIZ_ARTIFACT_BASE64;
if (!encoded) throw new Error("RECEIZ_ARTIFACT_BASE64 is required");
const artifactBytes = Uint8Array.from(Buffer.from(encoded, "base64"));

// Local verification is account-free and precedes every transport projection.
const receiz = createReceizClient();
const verification = await receiz.verification.verifyArtifact(artifactBytes);
if (verification.status !== "verified-artifact") {
  throw new Error(`Artifact verification status: ${verification.status}`);
}
console.log(verification.status);