Framework integrations

Solved outcome

What this enables

Adopt Receiz mechanics in an application while preserving developer-owned extension files and sealed artifact authority.

Installed identity

@receiz/sdk

Version

124.1.0

Package SHA-256

479d52f4c2215b05377ac557a62427abae9c16347e5341201b72699311afd7ac

Record source

packages/receiz-sdk/src/frameworkAdapters.ts

Exact form

Signature or request

generateReceizFrameworkFiles(contract: ReceizAppContract) => readonly ReceizGeneratedFile[]

Stable recovery

Failures

Permanent anchor · #frameworks-application-contract

Application contract

Validate a ReceizAppContract at operation contract version 122.0.0 with the required application-operation matrix before generating files.

Permanent anchor · #frameworks-framework-neutral

Framework-neutral

Generate transport-neutral modules that expose the declared operations, environment requirements, authority boundaries, and developer extension points without framework session assumptions.

Permanent anchor · #frameworks-next-js-app-router

Next.js App Router

Generate server-only credential modules, route handlers, and declared client boundaries for Next.js App Router. Keep secrets out of browser modules and preserve deterministic proof first paint.

Permanent anchor · #frameworks-generated-ownership

Generated ownership

receiz-generated files are compiler-owned; receiz-extension files are developer-owned. Apply updates through the exact preview digest and never overwrite declared developer-editable files.

Permanent anchor · #frameworks-upgrade-path

Upgrade path

Run app inspect, plan, check, apply, and upgrade with the exact target version. Review the plan digest, confirm only that digest, then rerun SDK conformance.

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

End-to-end example

Generated adapters begin from the same held-artifact local Verify path. Any separately selected authenticated issuance, request, response, cache, or session mechanic remains beneath the verified artifact.

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