跳到主要內容

ARC 2.0.0-beta.28

Evidence and version boundaries

Re-verify identity and data-space claims against a named ARC release using source, tests, and isolated CLI runs.

This board states two kinds of facts:

  1. Implementation facts — true of the ArcBlock/arc tree and its tests at documentation time.
  2. Operational facts — true of a named arc CLI release after commands were actually run in an isolated directory.

Do not upgrade an implementation fact into an operational recipe without a re-run.

Baseline for this revision

AxisValue
Site boarddocs/identity-data-spaces
CLI verifiedarc 2.0.0-beta.28 (arc --version) for the implementation facts on this board; the operational recipe was re-captured on 2.0.0-beta.42, whose arc space command surface differs
Operational captureIsolated --root-path + fixture --user-did (see Inspect local spaces, re-run on 2.0.0-beta.42)
Source treeArcBlock/arc (read-only reference at documentation time)
Primary source areasproviders/basic/did-space/, providers/basic/members/, services/shared/src/caller.ts, runtimes/node/src/daemon/auth/, packages/aos/src/session/

Evidence hierarchy

RankSourceCan support
1Current source + target-version tests + real local run“Supported now”
2Package README for the same packageScope explanation; still re-run commands
3Merged PRThat a change landed; re-check for later drift
4Architecture draft / planning / historical product pageIntent and lineage only

Re-verify checklist

Run these steps when the CLI version, provider package, or session overlay behavior changes.

A. CLI identity

bash
arc --version
arc space --help
arc did --help

Record the version string on every operational page you refresh.

B. Isolated space recipe

Repeat the recipe on Inspect local spaces with a fresh empty --root-path:

  1. list on empty root
  2. sync into the system and user fragment directories (read the destination back with path first — the scope directory is derived from the user DID)
  3. tree and path for both scopes
  4. rm and re-tree
  5. Failure cases: missing app, invalid scope on tree, missing path argument

Replace pasted outputs with the new capture. Do not keep old timings or byte sizes if they changed.

C. Source anchors (read-only)

Confirm these still match the prose:

ClaimLook at
Caller mapping + membership flagsservices/shared/src/caller.ts
Node auth setupruntimes/node/src/daemon/auth/index.ts
Role fail-closedpackages/aos/src/session/role-level.ts
Session overlayspackages/aos/src/session/session-user-afs.ts
DID Space roles + local providerproviders/basic/did-space/src/local.ts
Transport op strippingproviders/basic/did-space/src/client.ts
Isolation testsruntimes/node/test/daemon/two-user-space-isolation.test.ts, scope-user-space-overlay.test.ts

D. What not to re-assert without new E2E

  • Complete instance DID provisioning lifecycle
  • VC trust gate as a default public contract
  • Remote sync (an https://<host> end) against a specific production server
  • Historical DID Connect admin UI as the ARC-stable surface
  • Anonymous public share as the default data plane

Drift handling

SymptomAction
CLI output differs only in timing/sizeUpdate the paste; keep the procedure
Subcommand flags changeUpdate local-inspection and link to arc-cli reference
Session overlay semantics changeUpdate session-views + isolation table; cite new tests
Package renameUpdate did-space page imports and evidence table
Architecture draft conflicts with codePrefer code; note the draft as archaeology only