Releases and release compatibility

Solved outcome

What this enables

Select an implementation baseline from exact release evidence without collapsing a repository release, Git tag, package publication, deployment, smoke result, or attestation into another status.

Exact form

Signature or request

GET /releases · GET /releases/v124.1.0 · GET /releases/compare

Stable recovery

Failures

Permanent anchor · #releases-current-release

Current release

The v124.1.0 record separates repository evidence, Git coordinates, package publication, migration, deployment, production smoke, scale, adoption, governance, and attestation into independent fields. Historical v124.0.3 public evidence is never promoted into v124.1.0 evidence.

Permanent anchor · #releases-v124-production-runtime

V124 production runtime

V124.1.0 is the source-carried convergence release. Exact replay, Receiz-ID conversation, proof-derived memory/Twin response, identity-carried account continuity, and arbitrary sealed file reconstruction now operate as one runtime. Browser-supported video, audio, images, EPUB, PDF, and text render without a database, CDN, third-party media host, or external proof authority; large mobile video begins from authenticated ranges while the rest settles. Canonical live Kai, authenticated heads, durable execution, replay, atomic domains, and every presentation mechanic remain beneath the sealed proof object and unchanged 124.0.0 ruleset.

Permanent anchor · #releases-archive

Archive

Each permanent release route is generated from a repository-bound structured record. Incomplete historical records disclose only established Git evidence; planned records remain planned.

Permanent anchor · #releases-comparison

Comparison

Compare primitives, capabilities, compatibility, migration, registry, and evidence status as structured fields without converting one evidence dimension into another.

Permanent anchor · #releases-compatibility

Compatibility

Choose a release whose coordinated package and operation identities match the implementation target, then preserve historical artifact verification separately.

Permanent anchor · #releases-migration

Migration

Follow the release's declared migration boundary and exact CLI plan/verify/apply mechanics. Never infer a migration from chronology alone.

Permanent anchor · #releases-evidence-dimensions

Evidence dimensions

Repository commit, Git tag, package publication, deployment, production smoke, signed attestation, and visual evidence each retain their own status and provenance.

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

End-to-end example

Run the example against the selected coordinated package declarations and retain its digest evidence with the release-specific conformance record.

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);