Status and evidence
This page is the public entry point to the engineering status ledger. It exists so a capability claim can be checked instead of inferred from a diagram, a plan, or a changelog.
Claim rule
A claim becomes shipped-accepted only when the ledger records:
- A source entry point and commit.
- A test, benchmark, recovery drill, or hosted-acceptance artifact.
- The deployment profile and dependency assumptions.
- An owner and verification date.
- Known limitations and a review/expiry date.
If any of those are missing, the claim stays provisional, proposed, or unknown. A passing local test is not hosted evidence. A merged PR is not an acceptance record. An accepted contract shape is not a running implementation.
Status vocabulary
| Label | Ledger class | Meaning |
|---|---|---|
| IMPLEMENTED | shipped-local | Implemented and locally evidenced. Not hosted, HA, or production readiness. |
| PROVISIONAL | provisional | A seam or contract exists; evidence, review, or a gate remains open. |
| PROPOSED | design-intent | Specified or designed only. No runtime or acceptance evidence. |
| DEFERRED | deferred | Intentionally outside the current dependency set. |
| UNKNOWN | unknown | Evidence is missing or expired. Treat as unverified. |
The same vocabulary is used by page banners across the documentation.
Current baseline
| Area | Status | Must not be inferred |
|---|---|---|
| Auth and proxy foundations | IMPLEMENTED | Hosted HA or a measured proxy SLO. |
| Management API · tenant routes | IMPLEMENTED | Operator sessions, hosted readiness, generated-client completeness, or production integration. |
| Rate limiting | IMPLEMENTED | Hosted Redis HA or a measured latency SLO. |
| Provider routing, breakers, and fallback | IMPLEMENTED | A hosted provider-conformance matrix or streaming release soak. |
| Proxy p99 and benchmark gate (GAP-004) | PROVISIONAL | p99 ≤20 ms is a target, not a measured hosted SLO; the Go gate is mean-based. |
| Provider and tokenizer packages | IMPLEMENTED | A model name is a capability contract. |
| Memory substrate | IMPLEMENTED | Typed projections, deletion certification, or production isolation. |
| Embedding model identity | PROVISIONAL | A re-embed path, or a semantic-quality claim: the only embedding task is a no-op, there is no generation column or backfill task, licence and model-revision fields are still unrecorded in the inventory for every model, and the dev bundle runs deterministic stub geometry at an overridden dimension. Nor that the bare model id fences every generation — each embedded row records the model id plus @<revision> when IBEX_MEMORY_EMBEDDING_MODEL_REVISION is set, so two revisions of one id cannot share an identity; the fence is off by default and must be given that full string; nor does it make a fenced search generation-pure, since it bounds only the vector channel, the full-text channels are not fenced, and a keyword hit recorded under another generation can still return; BAAI/bge-m3 carries a weights revision only in the v1-single-node Compose file. |
| Context assembly | PROVISIONAL | Per-user caller authentication and the deadline boundary remain open; a shared caller token only closes unauthenticated direct access. |
| Ranking-quality benchmark (v1 gold set, v2 mode comparison) | PROVISIONAL | That the saturated twenty-query v1 gold set, or the v2 comparison where full_graph equals hybrid_rerank because the expected memory must outrank the twin suppression removes, is ranking quality or a graph-suppression win. |
| Extraction workers | PROVISIONAL | Queue durability, live model quality, or exactly-once projection effects. |
| MCP memory tools | PROVISIONAL | Logging-only audit is evidence-grade audit. |
| MCP operator gateway | IMPLEMENTED | PolicySnapshot resource evaluation, durable audit, hosted support, or operator readiness. |
| Budget, usage, and cost | PROVISIONAL | Complete extraction usage export, invoice reconciliation, or hosted enforcement evidence. |
| Evidence plane and relay | PROVISIONAL | A production sink, request authentication, tenant allowlist, or acknowledgement authority. |
| Operator Console · live reads | PROVISIONAL | Operator data mutations beyond the three session routes, org switching, hosted two-tenant evidence, or full accessibility certification. 8 of 10 core surfaces are live (ADR-0089). The Console session (login, refresh, and logout through the BFF) exists and a clean-browser journey proves it; every operator data route is still a read and no data route writes an operator record (P0-05), while a 401 read can still rotate the expired session server-side. Public runtime configuration exposed to the browser is limited to the non-secret NUXT_PUBLIC_IBEX_ENV label, and upstream origins stay in the server-only BFF; the browser itself holds the session cookies login sets — HttpOnly access and refresh, plus the readable CSRF cookie — and the personal access token it types at login, which the page clears after the exchange and never stores. |
| Operator Console · preview tiers | DEFERRED | 2 core surfaces and 8 platform-tier surfaces remain preview designs; labelled illustrative fixtures are permitted under ADR-0089 §4. |
| Streaming hardening | PROVISIONAL | Slow-client, bounded-buffer, leak, and provider-error soak evidence. |
v1-single-node deployment profile | IMPLEMENTED | Hosted/HA operation, multi-user auth, a measured p99 SLO, a two-tenant browser journey, a recovery drill, or a full cross-tenant acceptance suite. Three one-shot gates run in order — migrate, provision, then bootstrap — and every application service connects on its capability login (ibex_bootstrap, ibex_auth, ibex_runtime, ibex_worker), while every long-running service refuses to start on the owner or a superuser; only migrate and provision use the owner credential. Live-proven on 2026-11-15: all 13 health-checked containers healthy, no application connection is ibex, an unpinned cross-tenant read on ibex_runtime raises 42501, and a route-level cross-tenant request returns 403. The recorded start is one host and one tenant. |
| Production operations and recovery | PROPOSED | A production origin, passing RPO target, PITR proof, or E1–E4 release evidence. |
| DecisionService and GLiNER | PROPOSED | Any runtime, benchmark, registry, or acceptance evidence. |
| Graph, A2A, marketplace, sandbox | DEFERRED | Current dependencies or committed dates. |
Accepted contract shapes
Five G0 contract shapes were accepted on 2026-10-10 by Rick1330 acting across all owner roles. The accepted scope is contract text and safety semantics only; runtime seams remain provisional. No independent reviewer is named. Review or expiry is 2027-02-06 for all five: the four shapes re-verified on 2026-11-06, and idempotency-operation.v1, whose acceptance lapsed on 2026-11-10 and was renewed by the owner on 2026-11-11 on the 2026-11-09 evidence packet plus the additive 409 IDEMPOTENCY_KEY_ERASED term from PR #1152. The 2026-11-06 review re-verified four of the accepted shapes with new evidence and re-dated only those rows; the nine provisional runtime rows were re-verified on 2026-11-09 and are re-dated to 2027-02-06 with their status and limitations unchanged.
The acceptance does not cover a repo-wide principal migration, durable budget reservation, provider manifests, typed memory lifecycle, MCP governance, control-plane effects, production ClickHouse delivery, hosted recovery, or exactly-once effects.
The honest short version
- Local implementations exist for auth, the proxy path, the Management API, rate limiting, provider routing, and the memory substrate.
- Context, extraction, MCP memory, budgets, evidence, streaming hardening, and live Console reads remain provisional.
- Console preview tiers remain deferred. 2 core surfaces and 8 platform-tier surfaces are preview designs; labelled illustrative fixtures are permitted under ADR-0089 §4.
- No hosted p99 SLO exists. Do not repeat the 20 ms target as a measured result.
- Tenant isolation is defended in depth but not fully proven end-to-end.
- Typed memory lifecycle and a revision ledger are open (GAP-007).
- Production, HA, and restore claims are unsupported.
Evidence map
- Benchmarks — published local benchmark artifacts.
- Releases — changelog history.
- Security — fail-closed and isolation rules.
- Memory — what the substrate does and does not prove.
- Context assembly — provisional pipeline and limitations.
Engineering source: engineering/architecture-v2/00-status-and-evidence.md and engineering/architecture-v2/18-gap-register.md in the repository.

