Older ArcBlock material still uses product names that appear next to ARC. Use this index to find the current developer entry and the hard non-promises. Status values:
| Status | Meaning |
|---|---|
current | Actively documented ARC surface or product dependency you can open today |
reference implementation | Example app or pattern used to prove a contract; not a full platform product |
external dependency | Capability consumed from another package or service, not re-documented here as a full ARC product board |
historical only | Name retained for archaeology; not a supported upgrade path |
unresolved | Evidence incomplete; do not invent a successor product |
Mapping table
| Old name / alias | Why readers still see it | Current ARC home | Developer entry | What is not promised | Status |
|---|---|---|---|---|---|
| Discuss Kit | Standalone discussion Blocklet; site product record superseded / mergedInto: arc | Replicated discussion data as a reference Blocklet (blocklets/discuss-kit); parts of comments/collections surfaces in Web Device / UI runtime | Blocklets · Discuss Kit lineage · Blocklets | Full former board/blog/wiki/bookmark/message platform feature set | reference implementation |
| DID Connect | Sign-in and credential presentation in older apps and docs | Runtime identity and membership integration (for example @arcblock/did-connect-service used by members provider); broader DID Connect docs remain for the protocol/SDK family | Identity · DID Connect · Identity overview · existing DID Connect docs boards | That the former admin or user-centre UI is a stable ARC product face | external dependency (service/SDK) + current (caller/session integration on Identity board) |
| DID Spaces / DID Space | Personal or app data space branding and docs | DID Space as current AFS provider (@aigne/afs-did-space) and user-facing space tooling (arc space, related Blocklets) | Identity · DID Space · Identity overview | That every remote lifecycle, trust, and multi-instance path is one finished public contract | current (local/provider contract as documented on Identity board) with experimental/gap for unproven remote lifecycle |
| Data Space | Marketing and conceptual language around “data belonging to a DID” | Documentation term for caller data context and session views—not a second backend product | Identity · Data Space term | A separate public SDK, provider package, or lifecycle API named “Data Space” | current as terminology only |
| Media Kit | Standalone media Blocklet; site product superseded / mergedInto: arc | Partial media publishing, rendering, delivery, and upload-related pieces around Web Device / DID Space / CDN helpers—not a single named successor product | Task-specific Web Device / Identity pages as they document media paths; do not assume a Media Kit board | Full former uploader, plugin suite, remote-source pipeline, asset-library UI, or migration contract | unresolved successor product · partial capabilities only |
| Image Bin | Older asset/image library naming tied to media workflows | No verified full ARC equivalent product board in this documentation set | None as a first-class ARC developer board | That Image Bin features are fully present under another name | historical only / unresolved |
| Blocklet Server (and related Server-era tooling) | Long-running packaging and hosting vocabulary | ARC Blocklet package/instance model and CLI (arc blocklet) | Blocklets · ARC CLI blocklet | That every Server-era behaviour, API, or admin screen remains | lineage → current Blocklet contract is narrower and re-specified |
| AFS UI (as if it were a product SKU) | Draft architecture documents use the phrase | Architecture lens on this board; authoring via AUP + Web Device | AFS UI · AUP · Web Device | A third public authoring product or guaranteed third-party device SDK | architecture (not a separate product board) |
How to use a row
- Read Why readers still see it so you do not delete the name from mental models that external material still uses.
- Open Developer entry for operational work.
- Read What is not promised before writing migration, sales, or “feature parity” language.
- If status is
unresolvedorhistorical only, do not invent a replacement name in public docs.
Evidence notes (not a contract)
| Name | Primary evidence used for this table |
|---|---|
| Discuss Kit | Site content/products/discuss-kit (superseded, mergedInto: arc); ARC blocklets/discuss-kit README as replicated collection reference; Web Device comments-surface code |
| DID Connect | @arcblock/did-connect-service dependency in providers/basic/members; Identity board structure |
| DID Space | @aigne/afs-did-space provider package; Identity board DID Space pages |
| Data Space | Identity board terminology pages; no separate provider package named data-space |
| Media Kit | Site product superseded; no complete Media Kit migration evidence in ARC tree for this board |
| Image Bin | Name appears in historical material; no verified full successor board |
Update a row only after re-checking current code. A merged PR that once added a path is not enough if the tree no longer contains it.
Related: Contracts and evidence · Reference