diff --git a/README.md b/README.md
index 914ee3f..2a74eb8 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ The reset has two evidence cadences:
 - CRA civil links and death status, MoSD enrolment, SIPF pension and survivor
   cases, and NAgDI agriculture requirements use named Relay V2 exact lookups.
 
-Six Evidence cells have distinct providers, issuers, signing keys, JWKS, audit
+Six Evidence gateways have distinct providers, issuers, signing keys, JWKS, audit
 sinks, subject-binding secrets, and endpoints. Five Relays expose only the
 named non-enumerating operations needed by the lab. NIA's Relay is reserved for
 the optional eSignet UserInfo profile; NIA Evidence reads its own extract.
@@ -60,11 +60,12 @@ Local entry points after startup are:
 
 - Visitor Center: `http://127.0.0.1:4301`
 - Programme portal: `http://127.0.0.1:4300`
-- Authority Evidence gateway: `https://localhost:4341/evidence/{authority}`
+- Local TLS front door: `https://localhost:4341/evidence/{authority}`
 - Static metadata: `http://127.0.0.1:4331`
 
-The gateway strips `/evidence/{authority}` before forwarding. Application code
-uses six authority base URLs and never assumes a national Evidence host.
+The front door strips `/evidence/{authority}` before forwarding, so one local
+port reaches all six gateways. Application code uses six authority base URLs and
+never assumes a national Evidence host.
 
 ## Architecture
 
@@ -103,7 +104,7 @@ uv run python -m solmara_lab.publisher --root .. publish-extract \
 
 The live MoSD mutation is visible on the next Relay-backed Evidence request
 without a restart. A newly named SRO extract is not visible until only the SRO
-Evidence cell is rebound and restarted. Invalid, stale, or overwritten extracts
+Evidence gateway is rebound and restarted. Invalid, stale, or overwritten extracts
 fail closed. Run lifecycle smoke in isolated volumes or restore the deterministic
 fixture state afterward.
 
@@ -131,9 +132,9 @@ Relay/Evidence authoring inputs are tracked.
 
 - `relays/` contains five authority-governed Relay V2 projects.
 - `evidence/cells/` contains six authority Evidence bundle templates and
-  runtime bindings.
+  runtime bindings, one per gateway.
 - `generator/solmara_lab/publisher.py` publishes deterministic SQLite sources.
-- `scenarios/` and `scenario-runner/` route requirements to authority cells,
+- `scenarios/` and `scenario-runner/` route requirements to authority gateways,
   verify multiple JWKS, and compose application outcomes.
 - `portal/` and `home/` display safe authority, issuer, and source-type labels.
 - `metadata/` and `requests/registry-lab/` publish discovery and request
diff --git a/docs/changelog.md b/docs/changelog.md
index 12869ef..59e2a58 100644
--- a/docs/changelog.md
+++ b/docs/changelog.md
@@ -3,6 +3,16 @@
 A small dated log of what changed in the visitor center and the lab topology.
 Newest entry first.
 
+## 2026-08-20 Evidence gateways replace "cells"
+
+Every visitor-facing surface now calls an authority's Evidence deployment an
+Evidence gateway. "Cell" was a private coinage of the reset and was never
+defined for a reader; "gateway" is the noun Registry Stack itself uses for the
+service that answers a requirement over an authority's own source. Nothing in
+the topology changed. Directory names, hostnames, volume paths, and the
+`solmara-authority-cells` catalogue identifier keep their existing spelling
+because they are identities rather than descriptions.
+
 ## 2026-08-20 Registry Stack v0.23.0
 
 Solmara pins Registry Stack v0.23.0 across `versions.env`, the release-pin
@@ -13,10 +23,10 @@ topology is unchanged. The reason to move is security: v0.23.0 upgrades `h2`
 to 0.4.17, past RUSTSEC-2026-0258, where a peer could queue unlimited empty
 DATA frames on the HTTP/2 path that Relay and Evidence both serve over.
 
-The Evidence deployment contract gained three required fields, so the six cell
+The Evidence deployment contract gained three required fields, so the six gateway
 bundles are authored rather than only re-pinned. `service.publicOrigin` names
-the one routed origin RFC 9728 discovery answers on, which is each cell's own
-`<cell>-evidence.solmara.registrystack.org`. Every requirement and every
+the one routed origin RFC 9728 discovery answers on, which is each gateway's own
+`<authority>-evidence.solmara.registrystack.org`. Every requirement and every
 concept now carries a `handle`, the stable key a client reads a result under;
 each is authored to the last segment of the identifier it names. v0.23.0 also
 adds Registry Discovery and published Discovery client packages, neither of
@@ -53,7 +63,7 @@ digest input.
 
 ## 2026-08-12 Authority-owned Relay and Evidence reset
 
-Solmara now authors six independent Evidence cells and five Relay V2 projects.
+Solmara now authors six independent Evidence gateways and five Relay V2 projects.
 CRA, NIA, and SRO publish immutable SQLite extracts for direct Evidence use;
 CRA, MoSD, SIPF, and NAgDI expose only named exact Relay lookups, with NIA's
 Relay reserved for the optional eSignet UserInfo profile. The programme code
diff --git a/docs/hosted-deployment.md b/docs/hosted-deployment.md
index 8123506..ace3fd9 100644
--- a/docs/hosted-deployment.md
+++ b/docs/hosted-deployment.md
@@ -1,6 +1,6 @@
 # Hosted deployment
 
-Deploy the authority-cell reset only from the exact Registry Stack release
+Deploy the authority-owned reset only from the exact Registry Stack release
 recorded in `versions.env`. Relay, Evidence, and Mint must use their official
 Registry Stack OCI images pinned by digest. Solmara-owned images are also
 digest-pinned, while the local Relayctl helper is assembled from its
@@ -41,7 +41,7 @@ Do not reuse an unrelated package or deploy a mutable tag.
 ## Authority topology
 
 The hosted topology contains five Relay V2 services, six independently signed
-Evidence cells, one shared lab Mint, and the programme application. The optional
+Evidence gateways, one shared lab Mint, and the programme application. The optional
 eSignet profile uses the NIA Relay lookup.
 
 Evidence hosts are:
@@ -53,8 +53,8 @@ Evidence hosts are:
 - `sipf-evidence.solmara.registrystack.org`
 - `nagdi-evidence.solmara.registrystack.org`
 
-Each host is also the cell's own identity. The signed bundle carries it as
-`service.publicOrigin`, and the cell answers with it as the `resource` and the
+Each host is also the gateway's own identity. The signed bundle carries it as
+`service.publicOrigin`, and the gateway answers with it as the `resource` and the
 `jwks_uri` prefix of its RFC 9728 protected-resource metadata and in the
 `WWW-Authenticate` challenge it returns. `SOLMARA_<CELL>_EVIDENCE_PUBLIC_HOST`
 moves the route without moving that identity, so a deployment that sets one
@@ -72,16 +72,16 @@ paths are:
 |---|---:|---|
 | Shared Mint | 3 | Runtime, secrets, and Transit socket |
 | Five Relays | 10 | One runtime and one mutable source path per authority |
-| Six Evidence cells | 21 | Runtime, secrets, and Transit socket per cell, plus the CRA, NIA, and SRO immutable-extract paths |
+| Six Evidence gateways | 21 | Runtime, secrets, and Transit socket per gateway, plus the CRA, NIA, and SRO immutable-extract paths |
 
 Each application also joins a Coolify-managed container network that carries the
 ingress proxy, alongside the private runtime network its services address. A
 listener bound only to its private runtime address refuses that proxy and never
-answers its public route, so Mint and every Evidence cell bind every interface.
+answers its public route, so Mint and every Evidence gateway bind every interface.
 Evidence records this as `networkExposure: container-private`, the exposure its
 runtime requires before it accepts a wildcard bind. Isolation rests on network
 membership rather than on the bind address: an application's networks carry only
-its own containers and the proxy, so no authority reaches another's cells.
+its own containers and the proxy, so no authority reaches another's gateways.
 
 Joining two networks makes a container's routable address ambiguous. Traefik
 reads the address from the first network it iterates when no network is named,
@@ -111,7 +111,7 @@ to two different empty directories. Co-locating the provision, signer, core, and
 four authority applications is a deployment precondition.
 
 Each ministry runs its own signer application, which creates and owns the
-Transit socket paths of its cells and runs one isolated signer per cell:
+Transit socket paths of its gateways and runs one isolated signer per gateway:
 
 | Application | File | Signers |
 |---|---|---|
@@ -156,7 +156,7 @@ least-authority source clients, each limited to its named operation:
 - `nia-esignet`
 
 The ninth client, `solmara-demo`, belongs to the programme application and is
-used to request assertions from the authority Evidence cells. The shared Mint
+used to request assertions from the authority Evidence gateways. The shared Mint
 is a lab convenience, not production tenancy guidance.
 
 ## Secret boundary
@@ -170,7 +170,7 @@ Compose file, repository file, build log, or delivery record:
 - authority-specific Relay audit HMAC keys, plus cursor HMAC keys for the Relay
   contracts that require cursors;
 - Mint and Evidence audit HMAC keys;
-- one subject-binding HMAC key for each Evidence cell;
+- one subject-binding HMAC key for each Evidence gateway;
 - the programme federator token;
 - when eSignet is enabled, its database credential, KYC-token and PSUT HMAC
   secrets, KYC keystore credentials, and portal OIDC client key.
@@ -195,14 +195,14 @@ hosted provisioner creates the initial checked publication and reuses the exact
 active filename on a restart. It never overwrites an active extract in place.
 
 Reuse does not re-apply the extract's serving age. `maximumExtractAgeSeconds` is
-a policy each Evidence cell applies to live requests, so re-checking it while
+a policy each Evidence gateway applies to live requests, so re-checking it while
 re-adopting an already published extract would only make the provision
 application refuse to redeploy a day after it last ran. Every other binding,
 metadata, schema, and integrity check still applies, and an extract published in
 the future is still refused. Publishing a newer checkpoint remains the deliberate
 `publish-extract` operation below.
 
-To publish a later checkpoint, override the matching direct-cell provisioner
+To publish a later checkpoint, override the matching direct-gateway provisioner
 service command with:
 
 ```text
@@ -211,8 +211,9 @@ publish-extract --target <cra|nia|sro>-evidence --assets /opt/solmara-hosted-ass
 
 The operation validates the current binding, appends the checked publication
 under a fresh immutable filename, preserves the old file, and atomically
-rebinds only that cell's runtime configuration. Restart only the matching
-Evidence cell after the operation succeeds. The running cell continues to read
+rebinds only that gateway's runtime configuration. Restart only the matching
+Evidence gateway after the operation succeeds. The running gateway continues to
+read
 the old mounted extract until that restart. A malformed, metadata-mismatched,
 or non-newer publication fails closed.
 
@@ -248,7 +249,7 @@ Deploy the reset alongside the existing deployment in this order:
    `compose.coolify.social-development.yaml`,
    `compose.coolify.labour-pensions.yaml`, and
    `compose.coolify.agriculture.yaml`. Confirm all five Relays and all six
-   Evidence cells are ready on the private routes.
+   Evidence gateways are ready on the private routes.
 6. Run the hosted programme, denial, JWKS, source-label, redaction, and UI smoke
    against the new routes before changing public routing.
 7. If required for this deployment, add `compose.coolify.esignet.yaml` and run
@@ -274,7 +275,7 @@ requires:
 - wrong-purpose and unauthorized calls to fail generically;
 - the portal to prove authority URL selection, per-authority JWKS verification,
   source-type labels, and redaction;
-- the Visitor Center to show the publisher, six Evidence cells, five Relays,
+- the Visitor Center to show the publisher, six Evidence gateways, five Relays,
   shared Mint, and programme application;
 - when the optional profile is deployed, eSignet login to complete through the
   NIA Relay V2 lookup.
diff --git a/docs/purposes.md b/docs/purposes.md
index 2935d6b..57c2ce4 100644
--- a/docs/purposes.md
+++ b/docs/purposes.md
@@ -3,7 +3,7 @@
 Status: normative for the authority-owned Evidence reset.
 
 Evidence requests carry one closed purpose code in the signed request body.
-For Relay-backed requirements, the Evidence cell authenticates to Registry Mint
+For Relay-backed requirements, the Evidence gateway authenticates to Registry Mint
 with a dedicated private-key JWT client. Mint issues a token whose registration
 fixes the full purpose IRI, exact Relay scope, and `solmara-runtime` audience.
 The caller cannot select or override downstream Relay authority.
@@ -30,4 +30,4 @@ Responses and logs never include selectors, tokens, source rows, secrets,
 private keys, audit material, or sensitive dependency details.
 
 The programme application verifies every authority JWS and owns the final
-cross-authority outcome. No Evidence cell returns an application decision.
+cross-authority outcome. No Evidence gateway returns an application decision.
diff --git a/docs/solmara.md b/docs/solmara.md
index 2ce0691..127b860 100644
--- a/docs/solmara.md
+++ b/docs/solmara.md
@@ -1,9 +1,9 @@
 # Solmara lab architecture
 
-Solmara is a fictional institutional lab. Its core boundary is an authority
-cell: an authority publishes a governed source, operates its Evidence service,
-signs its assertions, and owns its audit trail. A programme consumes assertions
-from several cells and owns the programme decision.
+Solmara is a fictional institutional lab. Its core boundary is the authority:
+each one publishes a governed source, operates its own Evidence gateway, signs
+its assertions, and owns its audit trail. A programme consumes assertions from
+several authorities and owns the programme decision.
 
 ## Runtime topology
 
@@ -16,9 +16,9 @@ from several cells and owns the programme decision.
 | SIPF | live read-only SQLite | pension payment and survivor exact lookups |
 | NAgDI | live read-only SQLite | voucher and livestock exact lookups |
 
-There are six Evidence cells and five Relays. A Relay exists only for governed
-live consultation. It is not a façade over an Evidence cell's immutable local
-extract.
+There are six Evidence gateways and five Relays. A Relay exists only for
+governed live consultation. It is not a façade over an Evidence gateway's
+immutable local extract.
 
 Every Relay operation has one dedicated Mint client registration, exact scope,
 fixed purpose claim, access profile, and disclosure profile. Relays do not
@@ -27,10 +27,11 @@ offer list, search, cursor, or generic record routes. The shared
 
 ## Evidence authority
 
-Each cell has a unique provider IRI, authority DID issuer, ES256 signing key and
-JWKS, audit destination, subject-binding secret, runtime binding, and hostname.
-The application chooses the cell from a closed requirement directory, fetches
-only that cell's JWKS, verifies the exact requirement, evidence type, concepts,
+Each gateway has a unique provider IRI, authority DID issuer, ES256 signing key
+and JWKS, audit destination, subject-binding secret, runtime binding, and
+hostname. The application chooses the gateway from a closed requirement
+directory, fetches only that gateway's JWKS, verifies the exact requirement,
+evidence type, concepts,
 purpose, nonce, issuer, provider, audience, and validity window, then retains a
 safe presentation projection.
 
@@ -57,7 +58,7 @@ profile.
 Wrong scope, wrong purpose, malformed selectors, invalid source rows,
 unavailable source, and unavailable audit fail closed. No-match, ambiguous
 match, and policy-hidden matches use the same data-free unresolved class. An
-Evidence cell does not infer a negative assertion from an unresolved Relay
+Evidence gateway does not infer a negative assertion from an unresolved Relay
 consultation.
 
 ## Programme stories
diff --git a/docs/stories/birth-to-child-benefit.md b/docs/stories/birth-to-child-benefit.md
index 91e62dd..9a52027 100644
--- a/docs/stories/birth-to-child-benefit.md
+++ b/docs/stories/birth-to-child-benefit.md
@@ -21,7 +21,7 @@ unregistered birth, duplicate enrolment, and wrong purpose. An unregistered
 birth is a valid CRA record with no BRN and produces signed false, not an
 unresolved consultation. The mutable MoSD source changes on the next request;
 the three immutable sources change only after a reviewed replacement is bound
-and the owning cell is restarted.
+and the owning gateway is restarted.
 
 The response surface contains safe authority, issuer, provider, source type,
 and verified concept values. It does not contain selectors, tokens, source
diff --git a/docs/stories/death-to-pension-survivor.md b/docs/stories/death-to-pension-survivor.md
index 73228ff..7d9ae4f 100644
--- a/docs/stories/death-to-pension-survivor.md
+++ b/docs/stories/death-to-pension-survivor.md
@@ -2,7 +2,7 @@
 
 The pension application combines a CRA death assertion and a SIPF active
 payment assertion under `pension-payment-review`. The application, not either
-Evidence cell, derives whether payment should stop.
+Evidence gateway, derives whether payment should stop.
 
 CRA calls only `civil-person/death-by-uin` and discloses the governed death
 status. SIPF calls only `pension-payment/by-pensioner-uin` and discloses active
diff --git a/home/e2e/home.test.ts b/home/e2e/home.test.ts
index 78261c3..9278868 100644
--- a/home/e2e/home.test.ts
+++ b/home/e2e/home.test.ts
@@ -164,7 +164,7 @@ test('problem-codes anchors resolve, including current Evidence authorization de
   await expect(page.locator('[id="malformed_request"]')).toBeVisible();
 });
 
-test('anatomy lists five Relay V2 projects and six authority Evidence cells with config links', async ({ page }) => {
+test('anatomy lists five Relay V2 projects and six authority Evidence gateways with config links', async ({ page }) => {
   await page.goto('/anatomy');
   await expect(page.locator('#relays .entity')).toHaveCount(5);
   for (const id of ['cra-evidence', 'nia-evidence', 'sro-evidence', 'mosd-programme-evidence', 'sipf-evidence', 'nagdi-evidence']) {
@@ -241,10 +241,10 @@ test('purpose lens: the live review reveals evidence and the wrong-purpose chall
   await page.goto('/');
 
   await expect(
-    page.locator('#proof .proof-grid > div').filter({ hasText: 'authority Evidence cells' }).locator('strong')
+    page.locator('#proof .proof-grid > div').filter({ hasText: 'authority Evidence gateways' }).locator('strong')
   ).toHaveText('6');
   await expect(
-    page.locator('#solmara-preview .country-facts > div').filter({ hasText: 'Evidence cells' }).locator('dd')
+    page.locator('#solmara-preview .country-facts > div').filter({ hasText: 'Evidence gateways' }).locator('dd')
   ).toHaveText('6');
 
   // The boundary challenge appears only after a successful live evidence run.
diff --git a/home/src/lib/components/ProofStrip.svelte b/home/src/lib/components/ProofStrip.svelte
index 9a73230..6620907 100644
--- a/home/src/lib/components/ProofStrip.svelte
+++ b/home/src/lib/components/ProofStrip.svelte
@@ -17,7 +17,7 @@
   <div class="content proof-grid">
     <div><strong>1</strong><span>synthetic country</span></div>
     <div><strong>{authorities ?? 'Unavailable'}</strong><span>live authorities</span></div>
-    <div><strong>{evidenceCells ?? 'Unavailable'}</strong><span>authority Evidence cells</span></div>
+    <div><strong>{evidenceCells ?? 'Unavailable'}</strong><span>authority Evidence gateways</span></div>
     <div><strong>{journeys ?? 'Unavailable'}</strong><span>guided policy journeys</span></div>
     <div><strong>0</strong><span>real resident records</span></div>
   </div>
diff --git a/home/src/lib/components/SolmaraPreview.svelte b/home/src/lib/components/SolmaraPreview.svelte
index 22e0c16..d2168f8 100644
--- a/home/src/lib/components/SolmaraPreview.svelte
+++ b/home/src/lib/components/SolmaraPreview.svelte
@@ -27,7 +27,7 @@
       </p>
       <dl class="country-facts">
         <div><dt>Live authorities</dt><dd>{authorities ?? 'Unavailable'}</dd></div>
-        <div><dt>Evidence cells</dt><dd>{evidenceCells ?? 'Unavailable'}</dd></div>
+        <div><dt>Evidence gateways</dt><dd>{evidenceCells ?? 'Unavailable'}</dd></div>
         <div><dt>Real records</dt><dd>0</dd></div>
       </dl>
       <a class="button-link secondary-link" href="/country">Explore Solmara and its full synthetic cast</a>
diff --git a/home/src/lib/server/purposes.test.ts b/home/src/lib/server/purposes.test.ts
index a93717d..54103d9 100644
--- a/home/src/lib/server/purposes.test.ts
+++ b/home/src/lib/server/purposes.test.ts
@@ -8,8 +8,8 @@ const SAMPLE = `# Solmara Purpose Catalogue
 
 | Purpose IRI | Advertised by | Enforced by | Story | Denial problem codes |
 |---|---|---|---|---|
-| \`child-benefit-review\` | CRA, NIA | Authority Evidence cells | Birth to child benefit | \`not_authorized\` |
-| \`voucher-eligibility-review\` | NAgDI | Authority Evidence cells | Farmer climate-smart voucher | \`not_authorized\` |
+| \`child-benefit-review\` | CRA, NIA | Authority Evidence gateways | Birth to child benefit | \`not_authorized\` |
+| \`voucher-eligibility-review\` | NAgDI | Authority Evidence gateways | Farmer climate-smart voucher | \`not_authorized\` |
 
 ## Purpose Rules
 
@@ -55,7 +55,7 @@ describe('purposes parser', () => {
     expect(child.iri).toBe('child-benefit-review');
     expect(child.slug).toBe('child-benefit-review');
     expect(child.advertisedBy).toBe('CRA, NIA');
-    expect(child.enforcedBy).toBe('Authority Evidence cells');
+    expect(child.enforcedBy).toBe('Authority Evidence gateways');
     expect(child.story).toBe('Birth to child benefit');
     expect(child.denialCodes).toEqual(['not_authorized']);
     expect(child.plainLanguage).toContain('permits evidence needed to determine whether a child');
@@ -64,6 +64,16 @@ describe('purposes parser', () => {
     expect(child.plainLanguage).not.toContain('`');
   });
 
+  it('names the enforcing service for a three-column row', () => {
+    // Every row in the published catalogue is three columns, so this is the
+    // shape the site actually renders and the one that supplies the enforcing
+    // service from code rather than from the table.
+    const purposes = parsePurposes(`| \`citizen-self-service\` | CRA link, NIA status | one Relay lookup |`);
+    expect(purposes).toHaveLength(1);
+    expect(purposes[0].enforcedBy).toBe('Authority Evidence gateways');
+    expect(purposes[0].plainLanguage).toContain('CRA link, NIA status may answer this purpose');
+  });
+
   it('does not treat the credential section as a rule paragraph', () => {
     const purposes = parsePurposes(SAMPLE);
     expect(purposes.every((purpose) => !purpose.plainLanguage.includes('Ignore this section'))).toBe(true);
diff --git a/home/src/lib/server/purposes.ts b/home/src/lib/server/purposes.ts
index f58dba7..7ca41f0 100644
--- a/home/src/lib/server/purposes.ts
+++ b/home/src/lib/server/purposes.ts
@@ -26,7 +26,7 @@ export function parsePurposes(raw: string): Purpose[] {
           iri,
           slug,
           advertisedBy: cells[1],
-          enforcedBy: 'Authority Evidence cells',
+          enforcedBy: 'Authority Evidence gateways',
           story: slug.replace(/-/g, ' '),
           denialCodes: ['not_authorized'],
           plainLanguage: `${cells[1]} may answer this purpose through ${cells[2]}. Wrong-purpose and unauthorized requests disclose nothing.`
diff --git a/home/src/lib/server/services.test.ts b/home/src/lib/server/services.test.ts
index 0eeca14..9ba4b54 100644
--- a/home/src/lib/server/services.test.ts
+++ b/home/src/lib/server/services.test.ts
@@ -2,7 +2,7 @@ import { describe, expect, it } from 'vitest';
 import { statusProbes, topologyGroups } from './services';
 
 describe('authority-cell topology', () => {
-  it('has exactly five Relays, six Evidence cells, and one shared Mint', () => {
+  it('has exactly five Relays, six Evidence gateways, and one shared Mint', () => {
     const probes = statusProbes('http://portal.example');
     expect(probes.filter((probe) => probe.role === 'relay')).toHaveLength(5);
     expect(probes.filter((probe) => probe.role === 'evidence')).toHaveLength(6);
diff --git a/home/src/lib/server/services.ts b/home/src/lib/server/services.ts
index c63f4fc..514e55b 100644
--- a/home/src/lib/server/services.ts
+++ b/home/src/lib/server/services.ts
@@ -109,7 +109,7 @@ export const SERVICES: ServiceDef[] = [
     probeEnv: 'SOLMARA_CRA_EVIDENCE_URL',
     probeDefault: 'https://cra-evidence.solmara.registrystack.org',
     probePath: '/health',
-    configPaths: [{ label: 'Authority Evidence cell', path: 'evidence/cells/cra' }]
+    configPaths: [{ label: 'Authority Evidence gateway', path: 'evidence/cells/cra' }]
   }),
   evidence({
     id: 'nia-evidence',
@@ -119,7 +119,7 @@ export const SERVICES: ServiceDef[] = [
     probeEnv: 'SOLMARA_NIA_EVIDENCE_URL',
     probeDefault: 'https://nia-evidence.solmara.registrystack.org',
     probePath: '/health',
-    configPaths: [{ label: 'Authority Evidence cell', path: 'evidence/cells/nia' }]
+    configPaths: [{ label: 'Authority Evidence gateway', path: 'evidence/cells/nia' }]
   }),
   evidence({
     id: 'sro-evidence',
@@ -129,7 +129,7 @@ export const SERVICES: ServiceDef[] = [
     probeEnv: 'SOLMARA_SRO_EVIDENCE_URL',
     probeDefault: 'https://sro-evidence.solmara.registrystack.org',
     probePath: '/health',
-    configPaths: [{ label: 'Authority Evidence cell', path: 'evidence/cells/sro' }]
+    configPaths: [{ label: 'Authority Evidence gateway', path: 'evidence/cells/sro' }]
   }),
   evidence({
     id: 'mosd-programme-evidence',
@@ -139,7 +139,7 @@ export const SERVICES: ServiceDef[] = [
     probeEnv: 'SOLMARA_MOSD_PROGRAMME_EVIDENCE_URL',
     probeDefault: 'https://mosd-programme-evidence.solmara.registrystack.org',
     probePath: '/health',
-    configPaths: [{ label: 'Authority Evidence cell', path: 'evidence/cells/mosd-programme' }]
+    configPaths: [{ label: 'Authority Evidence gateway', path: 'evidence/cells/mosd-programme' }]
   }),
   evidence({
     id: 'sipf-evidence',
@@ -149,7 +149,7 @@ export const SERVICES: ServiceDef[] = [
     probeEnv: 'SOLMARA_SIPF_EVIDENCE_URL',
     probeDefault: 'https://sipf-evidence.solmara.registrystack.org',
     probePath: '/health',
-    configPaths: [{ label: 'Authority Evidence cell', path: 'evidence/cells/sipf' }]
+    configPaths: [{ label: 'Authority Evidence gateway', path: 'evidence/cells/sipf' }]
   }),
   evidence({
     id: 'nagdi-evidence',
@@ -159,12 +159,12 @@ export const SERVICES: ServiceDef[] = [
     probeEnv: 'SOLMARA_NAGDI_EVIDENCE_URL',
     probeDefault: 'https://nagdi-evidence.solmara.registrystack.org',
     probePath: '/health',
-    configPaths: [{ label: 'Authority Evidence cell', path: 'evidence/cells/nagdi' }]
+    configPaths: [{ label: 'Authority Evidence gateway', path: 'evidence/cells/nagdi' }]
   }),
   shared({
     id: 'lab-mint',
     label: 'Shared lab Mint',
-    blurb: 'Issues short-lived, audience-bound machine tokens for the six authority Evidence cells and five Relays.',
+    blurb: 'Issues short-lived, audience-bound machine tokens for the six authority Evidence gateways and five Relays.',
     probeEnv: 'MINT_URL',
     probeDefault: 'https://localhost:4341',
     probePath: '/health',
@@ -270,7 +270,7 @@ export function topologyGroups(repoUrl: string): TopologyGroup[] {
     },
     {
       key: 'evidence',
-      title: 'Six authority Evidence cells',
+      title: 'Six authority Evidence gateways',
       blurb: 'Each authority has its own Evidence service identity, issuer, reviewed requirements, and origin. The lab Mint is shared infrastructure, never the evidence issuer.',
       services: byId(['cra-evidence', 'nia-evidence', 'sro-evidence', 'mosd-programme-evidence', 'sipf-evidence', 'nagdi-evidence', 'lab-mint'])
     },
diff --git a/home/src/routes/anatomy/+page.svelte b/home/src/routes/anatomy/+page.svelte
index 48239b5..50f50bf 100644
--- a/home/src/routes/anatomy/+page.svelte
+++ b/home/src/routes/anatomy/+page.svelte
@@ -14,14 +14,14 @@
 
 <svelte:head>
   <title>Anatomy · Solmara Lab</title>
-  <meta name="description" content="What an institution actually runs: source-owned Records APIs, authority Evidence cells and Mint, application evidence collection, and the config linked in the repo." />
+  <meta name="description" content="What an institution actually runs: source-owned Records APIs, authority Evidence gateways and Mint, application evidence collection, and the config linked in the repo." />
 </svelte:head>
 
 <main class="reference-surface reference-page">
   <ReferenceHero
     eyebrow="System anatomy"
     title="See where every trust boundary runs"
-    description="Trace the deployed topology from source-owned registries and Records APIs through six authority Evidence cells to the applications that collect bounded signed values. Every card links back to the configuration that creates it."
+    description="Trace the deployed topology from source-owned registries and Records APIs through six authority Evidence gateways to the applications that collect bounded signed values. Every card links back to the configuration that creates it."
     active="anatomy"
     {facts}
   />
diff --git a/metadata/public/metadata/catalog.json b/metadata/public/metadata/catalog.json
index ad05ede..a8d6085 100644
--- a/metadata/public/metadata/catalog.json
+++ b/metadata/public/metadata/catalog.json
@@ -57,7 +57,7 @@
       "id": "cra-evidence-api",
       "iri": "https://cra-evidence.solmara.registrystack.org/v1/evidence",
       "title": {
-        "en": "CRA Evidence cell"
+        "en": "CRA Evidence gateway"
       }
     },
     {
@@ -67,7 +67,7 @@
       "id": "nia-evidence-api",
       "iri": "https://nia-evidence.solmara.registrystack.org/v1/evidence",
       "title": {
-        "en": "NIA Evidence cell"
+        "en": "NIA Evidence gateway"
       }
     },
     {
@@ -77,7 +77,7 @@
       "id": "sro-evidence-api",
       "iri": "https://sro-evidence.solmara.registrystack.org/v1/evidence",
       "title": {
-        "en": "SRO Evidence cell"
+        "en": "SRO Evidence gateway"
       }
     },
     {
@@ -87,7 +87,7 @@
       "id": "mosd-programme-evidence-api",
       "iri": "https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence",
       "title": {
-        "en": "MoSD Programme Evidence cell"
+        "en": "MoSD Programme Evidence gateway"
       }
     },
     {
@@ -97,7 +97,7 @@
       "id": "sipf-evidence-api",
       "iri": "https://sipf-evidence.solmara.registrystack.org/v1/evidence",
       "title": {
-        "en": "SIPF Evidence cell"
+        "en": "SIPF Evidence gateway"
       }
     },
     {
@@ -107,7 +107,7 @@
       "id": "nagdi-evidence-api",
       "iri": "https://nagdi-evidence.solmara.registrystack.org/v1/evidence",
       "title": {
-        "en": "NAgDI Evidence cell"
+        "en": "NAgDI Evidence gateway"
       }
     }
   ],
@@ -491,7 +491,7 @@
       "title": "NAgDI agriculture publication"
     }
   ],
-  "description": "Six authority-owned Evidence cells, five governed Relay V2 services, and the programme applications that compose signed assertions.",
+  "description": "Six authority-owned Evidence gateways, five governed Relay V2 services, and the programme applications that compose signed assertions.",
   "evidence_types": [
     {
       "id": "cra-child-benefit-v1",
diff --git a/metadata/public/metadata/dcat.jsonld b/metadata/public/metadata/dcat.jsonld
index 2001947..7f5f905 100644
--- a/metadata/public/metadata/dcat.jsonld
+++ b/metadata/public/metadata/dcat.jsonld
@@ -31,6 +31,6 @@
       "dct:title": "NAgDI agriculture publication"
     }
   ],
-  "dct:description": "Six authority-owned Evidence cells, five governed Relay V2 services, and the programme applications that compose signed assertions.",
+  "dct:description": "Six authority-owned Evidence gateways, five governed Relay V2 services, and the programme applications that compose signed assertions.",
   "dct:title": "Solmara authority-owned Evidence catalogue"
 }
diff --git a/metadata/public/metadata/index.json b/metadata/public/metadata/index.json
index 7efa2ef..9a6d07d 100644
--- a/metadata/public/metadata/index.json
+++ b/metadata/public/metadata/index.json
@@ -9,7 +9,7 @@
     {
       "media_type": "application/json",
       "path": "metadata/catalog.json",
-      "sha256": "sha256:49604351742db066f104f1e648e383228bd786c0b264c1a4370331f8dc9f3e6e"
+      "sha256": "sha256:c9c540a49ef5945b62a035b285fc992987227b5bf371f1a8d3908f9608ddc8ef"
     },
     {
       "media_type": "application/json",
@@ -24,7 +24,7 @@
     {
       "media_type": "application/ld+json",
       "path": "metadata/dcat.jsonld",
-      "sha256": "sha256:3747beabd9d30201a2065963cdeefeb45a1b26c9ae380d787f1da7d511e81d32"
+      "sha256": "sha256:0c1dbff692facf94d31ccf304f4b727766090611bc3d1af9a01bfb348fea586b"
     },
     {
       "media_type": "application/json",
@@ -89,7 +89,7 @@
     {
       "media_type": "application/yaml",
       "path": "metadata/metadata.yaml",
-      "sha256": "sha256:4c765f6526a95a84d59485b94e1fd57f677df824b91ecd5a3b00651cf006d191"
+      "sha256": "sha256:f3842a3527c81a513a23587591f21d767edd7147f01ddcc9f1332152ce7cb783"
     },
     {
       "media_type": "application/json",
diff --git a/metadata/public/metadata/metadata.yaml b/metadata/public/metadata/metadata.yaml
index 219ad77..aa0d0cb 100644
--- a/metadata/public/metadata/metadata.yaml
+++ b/metadata/public/metadata/metadata.yaml
@@ -5,7 +5,7 @@ catalog:
   title:
     en: Solmara authority-owned Evidence catalogue
   description:
-    en: Six authority-owned Evidence cells, five governed Relay V2 services, and the programme applications that compose signed assertions.
+    en: Six authority-owned Evidence gateways, five governed Relay V2 services, and the programme applications that compose signed assertions.
   publisher:
     name: Solmara Interoperability Metadata Publisher
     iri: did:web:id.registrystack.org:solmara:authority:metadata
@@ -238,37 +238,37 @@ public_services:
 data_services:
   - id: cra-evidence-api
     iri: https://cra-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: CRA Evidence cell}
+    title: {en: CRA Evidence gateway}
     endpoint_url: https://cra-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://cra-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: nia-evidence-api
     iri: https://nia-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: NIA Evidence cell}
+    title: {en: NIA Evidence gateway}
     endpoint_url: https://nia-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://nia-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: sro-evidence-api
     iri: https://sro-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: SRO Evidence cell}
+    title: {en: SRO Evidence gateway}
     endpoint_url: https://sro-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://sro-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: mosd-programme-evidence-api
     iri: https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: MoSD Programme Evidence cell}
+    title: {en: MoSD Programme Evidence gateway}
     endpoint_url: https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: sipf-evidence-api
     iri: https://sipf-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: SIPF Evidence cell}
+    title: {en: SIPF Evidence gateway}
     endpoint_url: https://sipf-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://sipf-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: nagdi-evidence-api
     iri: https://nagdi-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: NAgDI Evidence cell}
+    title: {en: NAgDI Evidence gateway}
     endpoint_url: https://nagdi-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://nagdi-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
diff --git a/metadata/solmara-wave1.metadata.yaml b/metadata/solmara-wave1.metadata.yaml
index 219ad77..aa0d0cb 100644
--- a/metadata/solmara-wave1.metadata.yaml
+++ b/metadata/solmara-wave1.metadata.yaml
@@ -5,7 +5,7 @@ catalog:
   title:
     en: Solmara authority-owned Evidence catalogue
   description:
-    en: Six authority-owned Evidence cells, five governed Relay V2 services, and the programme applications that compose signed assertions.
+    en: Six authority-owned Evidence gateways, five governed Relay V2 services, and the programme applications that compose signed assertions.
   publisher:
     name: Solmara Interoperability Metadata Publisher
     iri: did:web:id.registrystack.org:solmara:authority:metadata
@@ -238,37 +238,37 @@ public_services:
 data_services:
   - id: cra-evidence-api
     iri: https://cra-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: CRA Evidence cell}
+    title: {en: CRA Evidence gateway}
     endpoint_url: https://cra-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://cra-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: nia-evidence-api
     iri: https://nia-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: NIA Evidence cell}
+    title: {en: NIA Evidence gateway}
     endpoint_url: https://nia-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://nia-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: sro-evidence-api
     iri: https://sro-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: SRO Evidence cell}
+    title: {en: SRO Evidence gateway}
     endpoint_url: https://sro-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://sro-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: mosd-programme-evidence-api
     iri: https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: MoSD Programme Evidence cell}
+    title: {en: MoSD Programme Evidence gateway}
     endpoint_url: https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://mosd-programme-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: sipf-evidence-api
     iri: https://sipf-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: SIPF Evidence cell}
+    title: {en: SIPF Evidence gateway}
     endpoint_url: https://sipf-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://sipf-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1
   - id: nagdi-evidence-api
     iri: https://nagdi-evidence.solmara.registrystack.org/v1/evidence
-    title: {en: NAgDI Evidence cell}
+    title: {en: NAgDI Evidence gateway}
     endpoint_url: https://nagdi-evidence.solmara.registrystack.org/v1/evidence
     endpoint_description: https://nagdi-evidence.solmara.registrystack.org/v1/evidence-definitions
     conforms_to: https://id.registrystack.org/spec/registry-evidence/v1