Status vocabulary

Four defined terms. Documentation and acceptance evidence are both written against them, so what each one does not mean matters as much as what it does.

Written from docs/documentation-index.md

A document describes a capability. It does not by itself prove that a regulator, a provider or a production operator has accepted it. Every production claim should cite an acceptance record, an environment, a test run and an approving person.

Implemented

Represented in the repository and covered by automated or compile-time checks.

It does not mean: That it is running in your environment, that a regulator has accepted its output, or that a provider contract exists behind it.

Externally dependent

The contract exists and the seam is exercised, but a licensed provider, a regulator artefact or a live environment is required before it does anything.

It does not mean: That the work is incomplete on our side. It means the dependency is not ours to supply — identity verification and watchlist content are both in this state today.

Pending acceptance

The implementation exists, but business, legal, security or operational evidence is outstanding.

It does not mean: That it is unfinished. It means nobody has yet signed the record that says it was reviewed and found adequate.

Future

Deliberately outside the current release boundary.

It does not mean: A commitment, a date, or a roadmap item you can rely on in a business case.