Rename decision 2026-05-23

This is a maintenance record. If you’re an integrator using the current project names (Registry Relay, Registry Notary, and the rest of the stack), you can ignore the legacy column.

Five registry projects were renamed on 2026-05-23 from a mix of snake_case, kebab-case, and three competing root metaphors (registry, evidence, dataspace) to a single Docker-style registry- naming convention. This record documents the decision, the mapping, and the per-repo rename state as of the review date.

Decision

Adopt the following legacy-to-current mapping across all five repos. The rename is a clean break: no aliases, no fallback strings, no legacy v1 identifiers retained (rename plan, Decisions baked in, item 1).

Legacy name	Current name	Role
registry_relay	registry-relay	Protected, read-only registry consultation gateway
registry-metadata	registry-manifest	Portable manifest contracts, validation, and renderers
evidence-server	registry-notary	Standalone claim evaluation, credential issuance, and attestation
dataspace-atlas	registry-atlas	Standards-first workbench for inspecting registry discovery artifacts
decentralized-evidence-demo	registry-lab	Compose-based runnable demo of the registry stack

Human-readable brand strings flip in lock-step: “Registry Relay” stays; the other four adopt new display names as listed (rename plan, “Final state”).

Context

The rename plan (2026-05-23) documents the rationale: nothing is in production, so the cost of half-renaming (legacy machine strings forever) exceeds the cost of a single complete sweep. The plan defines five sequential phases, one PR per repo, in dependency order: Phase 1 (registry-manifest), Phase 2 (registry-atlas), Phase 3 (registry-notary), Phase 4 (registry-relay), Phase 5 (registry-lab).

Machine contracts that rename alongside project labels include:

• Schema version: registry-metadata/v1 to registry-manifest/v1
• JSON-LD CURIE prefix: registry_metadata: to registry_manifest:
• Canonical IRI: updated to https://jeremi.github.io/registry-manifest/ns#
• Access kind enum value: evidence-server to registry-notary
• Media type: application/vnd.evidence-server.claim-result+json to application/vnd.registry-notary.claim-result+json
• JWT audience default: updated to match the new service name
• Cargo feature names: updated in each crate
• Project-labeled env vars: updated across all repos

API route prefixes (/evidence/..., /metadata/...) and domain-flow env vars (CIVIL_EVIDENCE_*, SOCIAL_PROTECTION_EVIDENCE_*) are intentionally preserved because they name domain flows, not the project (rename plan, Decision 1 keep list).

Sibling worktree directories at the apps/ root (registry_relay-claim-verification, registry_relay-ogc, registry_relay_history_backups) are out of scope and remain as-is (rename plan, Decision 5).

Per-repo rename state

Registry Manifest

Source: registry-manifest evidence packet, “Naming and rename status” section.

The rename is fully landed locally. Crate names are registry-manifest-core and registry-manifest-cli. Schema versions read registry-manifest/v1, registry-manifest-profile/v1, and registry-manifest-index/v1. No legacy labels (registry_metadata:, registry-metadata.dev, registry-metadata/v1) found in source. projects.yaml rename_status: “Already using the target repo name locally.”

Registry Relay

Source: registry-relay evidence packet, “Naming and rename status” section; projects.yaml rename_status.

The local checkout is renamed to registry-relay. The Cargo crate name and binary are already registry-relay. Old underscore-form references do not appear in the API or config surface. Old worktree directories (registry_relay-*) remain at the apps/ root as historical artifacts; renaming them is out of scope per Decision 5 of the rename plan. projects.yaml rename_status: “Local checkout renamed to registry-relay; old worktrees under registry_relay-* remain for historical evidence.”

Partial rename note: The rename plan identifies that Phase 4 absorbs cross-repo work: updating the Cargo dependency on registry-manifest-core, swapping notary contract strings (evidence-server to registry-notary in access.kind, conforms_to, and OpenAPI enum), and regenerating snapshot files. The evidence packet confirms the current binary and Cargo package name are correct but does not confirm Phase 4 cross-repo absorption is complete.

Registry Notary

Source: registry-notary evidence packet, “Naming and rename status” section.

The rename is fully landed locally. Crate names are registry-notary-core, registry-notary-server, and registry-notary-bin. The media type constant reads application/vnd.registry-notary.claim-result+json (model.rs:9). The default service_id is registry-notary (config.rs:249). The env var is REGISTRY_NOTARY_ISSUER_JWK (config.rs:561). No legacy labels (evidence-server, evidence-server-cel, vnd.evidence-server) found in source. projects.yaml rename_status: “Already using the target repo name locally.”

Registry Atlas

Source: registry-atlas evidence packet, “Naming and rename status” section.

The rename is fully landed locally. Nomenclature is stable across specification and implementation layers. No renaming campaigns detected in commit history. projects.yaml rename_status: “Already using the target repo name locally.”

Registry Lab

Source: registry-lab evidence packet, “Naming and rename status” section.

The directory has been renamed from decentralized-evidence-demo/ to registry-lab/. The git submodules point to vendor/registry-relay and vendor/registry-notary (.gitmodules, registry-lab evidence packet “Vendored or third-party content”). Compose service names use registry-relay:demo and registry-notary:demo images.

Remaining references to the legacy name are present in scripts and fixtures:

• scripts/generate-fixtures.py (docstring and creator metadata string "registry-relay-decentralized-demo-generator")
• scripts/generate-demo-secrets.py (docstring)
• scripts/demo-flow.py (docstring, PURPOSE URI, CORRELATION_ID default value "decentralized-demo-correlation-001")
• scripts/smoke.sh (correlation ID default, temp file paths, Data-Purpose header values)
• config/static-metadata/metadata.yaml (id: decentralized-demo-static-publication)
• README.md (narrative reference to decentralized-demo-correlation-001)
• .env.example (credential comments)

The registry-lab evidence packet notes that functional identifiers baked into credentials, log correlation, and spec URLs (decentralized-demo-correlation-001, decentralized-demo-static-publication) are intentionally stable and do not require change when the directory is renamed. Docstrings and comments are residual and could be updated to say “Registry Lab demo” without affecting machine contracts. projects.yaml rename_status: “Local checkout renamed to registry-lab; some scripts and fixtures may still reference the old decentralized-evidence-demo name.”

Consequences

v0 prose in this site uses the current names in the “Decision” table for all five projects. Legacy names appear only in this decision record, in rename_status fields in projects.yaml, and in historical pages where they explain the pre-rename shape.

When the GitHub repos finish their per-phase renames, update src/data/projects.yaml and any affected source links in src/data/repo-map.yaml. Do not rewrite historical evidence docs unless the owning repo migrates them.

Superseded by

None. This record stands until all five GitHub repo renames complete and a follow-up record documents the final state.