What is not built yet

Metergrade's architecture describes five capabilities — Observe, Analyze, Validate, Deploy, Govern — and a documentation structure covering all of them. Most of it is not built.

This page exists so that gap is stated in one place rather than discovered one dead link at a time. If a capability is not listed as available below, it does not exist yet, whatever a diagram elsewhere might suggest.

Nothing here carries a date. A date would be a commitment, and the honest position is a status.

Available today

Capability	State
Economic Control Check	Available. No account, nothing transferred. Documented in these pages.
Signed, verifiable kit distribution	Available. Sigstore keyless signing, published at metergrade.com.
Assisted Assessment (service)	Available. A US$5,000 fixed engagement — people, not software.

Not built

Saving a baseline · Metergrade Free

An account, an Organization, and analysis that persists across sessions. Requires you to upload an export you produce locally, after signing in.

State: not built. There is no console and no sign-in. /start says so rather than linking to a host that does not resolve. The export query exists and runs, but there is nowhere to send its output.

Connect — continuous ingestion

Event Hub, the forwarder, authentication, reconciliation.

State: not built. The check is a point-in-time query you run yourself. Nothing watches your estate continuously. The kit's agent instructions explicitly forbid installing continuous ingestion, because it is a later milestone and not part of setup.

Control — workloads, ownership, economic standards

Naming a workload, assigning an accountable owner, attaching business outcomes, and defining the economic standard a workload is expected to satisfy.

State: not built. The check reports attribution gaps — consumption with no accountable API or operation behind it — but there is nowhere to resolve one. Resolving it today means changing how your callers identify themselves at the gateway.

Prove — validation and verdicts

Testing a candidate change against your own quality, latency and reliability requirements, returning PASS / FAIL / INCONCLUSIVE with the evidence.

State: not built. This is the centre of the product architecture and the point at which Metergrade charges, and it does not exist yet. Query 05 ranks candidates worth testing; it applies no threshold and reaches no verdict, because there is no validation engine behind it.

Deploy — configuration artifacts

APIM policy, Bicep, Terraform, CI/CD integration, attestation, rollback.

State: not built. Metergrade emits nothing deployable today.

Maintain — drift, invalidation, revalidation

Continuous monitoring of whether a validated result still holds.

State: not built. Depends on continuous ingestion and on validation, neither of which exists.

Administer — organizations, roles, retention, audit, billing

State: not built. There is no multi-user surface, so there is nothing to administer. Team and Foundation plans cannot be bought; /pricing says so.

Reference — API, events, errors

State: not built. There is no public API and no event stream.

Documentation that follows from that

The ratified documentation structure names Get started, Assess, Connect, Control, Prove, Deploy, Maintain, Administer and Reference.

Get started, Assess and Reference are written, because the Economic Control Check is real and you can run it today.

The rest are absent rather than stubbed. A page reading "coming soon" tells a reader nothing they could not infer from its absence, and thirty of them make a product look unfinished while adding no information. When a capability ships, its documentation ships with it.

Where the boundary sits commercially

Discovering the economic state of an estate is free and always will be. The Economic Control Check is that surface, and it is complete.

Payment begins at Validate — which is the part that is not built. Metergrade is not currently able to charge for the thing it intends to charge for, and saying so plainly is cheaper than being found out.