The following boundaries are intentional. They keep this board from turning architecture intent or a historical product page into a present-tense product commitment.
Safe statements versus non-promises
| Topic | Current safe statement | Do not claim yet |
|---|---|---|
| Data Space | Explanatory name for data context and session-visible views. | Separate public DataSpace API, resource type, or provisioning lifecycle. |
| DID Space | AFS provider for DID-scoped storage; may appear through session views and local CLI. | One backend, one remote deployment path, or equal ops for all transports. |
| Session scope | Tests cover current-caller isolation, /tmp, optional /space, and network base write gates. | Universal application ACL for every Blocklet and every path. |
/space writes | Optional overlay; general writes may be readonly; collections write-guard is a fixed policy when wired. | Open write access to the whole DID Space root by default. |
| Caller and membership | Trusted credential resolution attaches caller identity and may overlay an instance role. | User account recovery, membership administration product, or complete instance DID lifecycle. |
| VC / trust | Not a public default gate documented here. | “VC trust is on by default” or full issuer-revocation operations. |
| Public sharing / CDN | Share and hosting mechanisms exist in provider code and plans; not packaged here as anonymous share-as-default. | DID Space is a public CDN or open anonymous data plane. |
| DID Connect | Runtime embeds connect-service for credential resolution and related host endpoints. | One-for-one migration of every former standalone UI or product surface. |
| Cloud sync CLI | arc space sync exists as a command and reaches a remote end when --from/--to is an https://<host> reference. | A re-verified remote E2E runbook on this board (not captured here). |
| Historical products | Names such as DID Spaces / DID Connect appear in lineage and runtime seams. | Every historical feature is already a stable ARC equivalent. |
Architecture drafts are not contracts
Internal materials such as docs/architecture/did-entities.md and docs/architecture/did-space.md explain intent and evolution. They mark incomplete areas (for example instance DID lifecycle) explicitly. Public pages on this board only absorb conclusions that current source, tests, or a named CLI run still support.
If you need something in the right column
- Narrow the requirement to a testable claim.
- Verify it against the target ARC release (source + tests + runtime).
- Add a versioned operational page only after that evidence exists.
- Until then, keep the gap explicit rather than papering it over with path-shaped language.
See Evidence and version boundaries for the re-verification checklist used by this board.