admin
Ops Status
Ops dashboard status: build identity, embedding identity vs registry, and the fleet-wide vectorless-atom counters (FAILURE-SURFACE-2026-08-26 P0-1).
- embedding_identity is the SAME truth /health/ready reports — engine._resolve_global_embedding_stamp(), the actual producing service.
- embedding_registry_active is the embedding_versions active row, read on the request pool (the table carries no RLS; boot reads it the same way).
- The atom counters go through storage.admin_ops_atom_counts() — the BYPASSRLS maintenance route, guarded by row_security_active on the same connection — and are gated by the existing ADMIN_ATOMS_AGGREGATES_ENABLED switch, whose config validation already forces a distinct maintenance DSN under multi-tenant auth. Flag off → the counters are null with a reason, never zero.
Failures: a database error on any read answers 503 (MnemoError, retryable) — the dashboard must see "unknown", not a 500 and not a number. A refused maintenance route (SQLSTATE MN001) is a 503 that names MAINTENANCE_DATABASE_URL; a pool timeout propagates to the dedicated asyncio.TimeoutError handler exactly as in aggregate_accounts.
get/api/v1/admin/ops/status
Request
- Base URL: https://core.mnemoverse.com
- URL: https://core.mnemoverse.com/api/v1/admin/ops/status
- Auth: API key in header X-Admin-Key
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.