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

published coordinated packages 128.0.0 · ruleset 127.0.0 · supported current range >=128.0.0 <129.0.0 · 335 MCP tools · 43 AI skills

Stable recovery

Failures

Permanent anchor · #compatibility-current-identity

Current identity

The application, Academy, SDK, compiler, MCP and AI release identity is 128.0.0, inheriting the exact admitted v127 ruleset. The published packages contain 425 SDK client methods, 680 callable exports and 335 explicit MCP tools. Installed-package tables bind exact 128.0.0 package digests. Package publication and application deployment remain separate evidence boundaries.

Permanent anchor · #compatibility-version-matrix

Version matrix

The v128 release binds coordinated 128.0.0 packages, ruleset 127.0.0 and supported current range >=128.0.0 <129.0.0. Upgrade the three public packages together. Stable historical wire schemas and method suffixes remain protocol identities; historical sealed proof bytes remain immutable.

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 current 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 installed 128.0.0 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);