ARC 2.0.0-beta.28

Reference and boundaries

Check which identity and data-space statements are current contracts, which are architecture terms, and which still require release-specific evidence.

Use this section when a design decision depends on an exact boundary rather than a high-level explanation. The pages here separate three classes of statements:

Class	How to use it
Current contract	Current source, tests, and (for CLI) a named release run show the behavior. Start here, then verify your target ARC version.
Architecture term	The term helps explain how parts fit together, but does not create an importable API or operational workflow.
Unverified or evolving area	Keep it outside production assumptions until a versioned contract and runnable evidence exist.

Child pages

Current contract boundaries — safe statements versus non-promises.
Evidence and version boundaries — how to re-verify this board against a named arc release.

Quick index

Topic	Current contract page	Notes
Caller resolution	Caller context	Trusted credentials only
DID Space provider	DID-scoped storage	Transport ops unequal
Data Space name	What “Data Space” means here	Explanatory only
Session overlays	Session views	Isolation as tested
Local CLI	Inspect local spaces	`2.0.0-beta.28` capture
DID Connect seam	DID Connect in ARC	Runtime handoff, not full product UI