Service Inventory and Dependency Map

Generated from the live Cloud Run control plane by scripts/regen_service_inventory.py. Every field below is read with gcloud run services list --format=json and rendered mechanically — no value is transcribed by hand. Do not hand-edit this file; regenerate it.

Claim label: verified result for what is deployed, its region, runtime service account, ingress setting, and referenced secret NAMES.

NOT verified here, and deliberately not asserted: per-service IAM bindings (whether any carries an allUsers invoker), request-path behaviour, inter-service call graphs, or health. Ingress is the Cloud Run ingress annotation, which is not the auth gate — see docs/lii/RUNBOOK.md §0.a for the three gates a caller actually clears.

1. Fleet shape

• 111 services deployed.
• us-central1: 109
• us-east1: 2

2. Runtime service accounts

82 of 111 services run as 698171499447-compute@developer…. The project default compute account is broadly privileged, so this is a standing least-privilege gap across most of the fleet. Recorded as an observation; changing runtime identities is an owner decision with a real blast radius.

3. Retired Neo4j wiring still present on live services

Owner decision 2026-08-09: Neo4j is not being re-provisioned; Firestore is the knowledge-graph backend. The services below still carry a NEO4J_URI. As of 2026-08-10 every such host was NXDOMAIN while the parent databases.neo4j.io resolved — dead hosts, not a DNS fault.

This list is DERIVED from each service's deployed env, not maintained by hand. A service that acquires a NEO4J_URI tomorrow appears here on the next regeneration without anyone editing the script.

None. No deployed service carries a NEO4J_URI. The retirement is complete at the fleet level; this section can stay as the guard that would notice a regression.

intent-graph (Cell 35) does not appear above, and that is correct. It carries INTENT_NEO4J_MODE — a backend selector, not a dial — and no NEO4J_URI, which resolves the cell to its in-process memory graph. See docs/lii/RUNBOOK.md §1 for the readiness contract that follows.

Live retirement is complete. Keep this generated section and its derived NEO4J_URI scan as the regression guard.

4. Deployed services

⚠ = carries retired Neo4j wiring (§3).

5. Regenerating

python3 scripts/regen_service_inventory.py > docs/service_inventory.md

If a row here disagrees with the fleet, the fleet is right and this document is stale — regenerate rather than hand-patch, which is how the previous version drifted past the point of being checkable.