Give agents identity across environments

Three separate coordinates

Cross-platform continuity does not mean universal private application access. A compatible environment must admit the source and expose the supported tools. An agent can keep its identity/history while acquiring only the permissions explicitly granted for that environment.

Device-held modern subjects

The installed MCP device runtime opens actual host-held identity custody. The receiz_device_ai_subject_create workflow previews creation, then requires its exact single-use confirmation digest. It creates a distinct private modern V122/V125 subject proof object, saves and verifies its enclosing source and full KaiSigil temporal artifact, and makes no public append. Public disclosure is separate.

import { openReceizMcpDeviceRuntime } from '@receiz/mcp-server';

// Trusted-host inputs: existing private identity and protected local paths.
const runtime = await openReceizMcpDeviceRuntime({
  identityArtifactPath,
  identityPassphrase,
  workspace,
  sealDirectory,
  subjectDirectory,
});

Keep personal context opt-in

Personal identity context sharing is off by default in the device runtime. Enabling all-carried-state sharing requires explicit disclosure consent. A private subject can retain its own continuity without automatically publishing the owner’s other private sources. Keep paths, phrases, keys and identity admission in the trusted host; do not send them as ordinary model text.

Do not mix subject generations

The maintained openReceizV127SubjectRuntimeFromFiles adapter is a historical V120 local-subject host despite the V127 function name. It has its own registry/reducer commitments, sealed-source admission and durable private compare-and-swap storage. It is separate from modern V122/V125 subject creation. Bare mind/snapshot JSON does not gain authority, and snapshot transport must preserve the enclosing sealed source before import.

• Version and protocol compatibility ↗

Connect tools with their real permissions

1. Choose one task and host

   Identify the source, subject generation, receiving application and custody path.

2. Admit the enclosing source

   Verify identity, subject and history under the supported primitive.

3. Inspect tool schemas

   Use the installed operation inventory and actual required grants.

4. Retain results

   Preserve carried history and exact consequential-operation references.

A model answer or proposal cannot authorize a transfer, publication or employee payment by itself. Those capabilities use their exact configured operation and consent. If a required host/tool is unavailable, name that boundary instead of inventing a second agent identity or authority layer.