Product readiness summary¶

This page is the single place where product readiness is rated. Every product page links here instead of keeping its own scale.

Documentation status

Last verified: 26 Sep 2026. Ratings use only the rubric below and the status vocabulary.

Rubric¶

Each product is rated against five gates. A gate is only MET when the evidence listed below exists in the repositories or in a recorded owner decision. Nothing is assumed.

Gate	Evidence required
Code	The product's routes (or entry points) are implemented and reachable on the main branch or the branch that is deployed
Integration Verified	Evidence of a real consumer exercising the contract, or a contract test that runs producer and consumer together
Ops Ready	Deployment configuration, and monitoring or alerting, and a runbook
Security Approved	Enforced authentication and authorisation on the product's routes, and no open security findings, and a recorded owner sign-off
GA	All four gates above are MET, and an owner has declared general availability

Value	Meaning
MET	All required evidence exists
PARTIAL	Some of the required evidence exists; the notes say what is missing
NOT MET	The evidence shows the gate is not satisfied
UNKNOWN	No evidence either way in the sources available to the documentation team

Separately, capabilities on product pages use the labels in the status vocabulary: IMPLEMENTED, PARTIAL, PLANNED, DEPRECATED, DEAD, and UNKNOWN.

Ratings¶

Product / slice	Code	Integration Verified	Ops Ready	Security Approved	GA
Fraud Detection (baselines, scoring, report)	PARTIAL	NOT MET	PARTIAL	NOT MET	NOT MET
Fraud case-rule evaluation	PARTIAL	UNKNOWN	PARTIAL	NOT MET	NOT MET
KYC / KYB	PARTIAL	UNKNOWN	PARTIAL	NOT MET	NOT MET
AML / Regulatory Reporting (goAML)	NOT MET	NOT MET	NOT MET	NOT MET	NOT MET
Banking Reconciliation	PARTIAL	UNKNOWN	PARTIAL	NOT MET	NOT MET
Reconciliation exception resolve	PARTIAL	UNKNOWN	PARTIAL	NOT MET	NOT MET
Durable transaction-monitoring case desk	UNKNOWN	UNKNOWN	UNKNOWN	UNKNOWN	NOT MET

Why each rating¶

Fraud Detection

Code: PARTIAL. The scoring, baseline and report routes exist on the main branches. The current report contract (validation, normalisation, policy) and the current ML tiering exist only on the development branches, and which revision is deployed is UNKNOWN.
Integration Verified: NOT MET. The ML scoring output and the report step's accepted tiers are incompatible (Fraud output contract). The report contract tests cover the consumer only.
Ops Ready: PARTIAL. Deployment configuration and troubleshooting guidance exist. There is no monitoring or alerting configuration in the repositories.
Security Approved: NOT MET. Open security findings exist and there is no sign-off record.
GA: NOT MET.
The automated decision policy fraud-decision-v1 is provisional.

Fraud case-rule evaluation

Code: PARTIAL. Implemented on the development branch only; not present on the main branch.
Integration Verified: UNKNOWN. No consumer or contract-test evidence.
Ops Ready: PARTIAL. Deployment configuration exists; no monitoring or alerting.
Security Approved: NOT MET. Token verification is enforced on the route, but platform-level findings remain open and there is no sign-off.
GA: NOT MET.

KYC / KYB

Code: PARTIAL. 19 routes on the development branch. The main branch has 15 of them, and the deployed revision is UNKNOWN.
Integration Verified: UNKNOWN. Unit tests exist; no consumer or contract-test evidence.
Ops Ready: PARTIAL. Deployment configuration exists; no monitoring or alerting; logs are written to files inside the container.
Security Approved: NOT MET. Open findings on route authentication.
GA: NOT MET.

AML / Regulatory Reporting (goAML)

Code: NOT MET. An XML helper library exists, but it has no route and no submission path.
Integration Verified, Ops Ready, Security Approved, GA: NOT MET.

Banking Reconciliation and exception resolve

Code: PARTIAL. The microservices exist only on the deployment branch (dev-deploy); the main branch holds an older layout. Whether every local settings dependency is present on the deployed revision is UNKNOWN.
Integration Verified: UNKNOWN. Service unit tests exist, including the resolve trigger; there is no evidence of the publishing backend exercising the contract.
Ops Ready: PARTIAL. Deployment configuration and dead-letter topics exist; no monitoring or alerting configuration.
Security Approved: NOT MET. No application-level authentication, and no sign-off.
GA: NOT MET.

Durable transaction-monitoring case desk

Not present in the product repositories, so every gate is UNKNOWN except GA, which is NOT MET because nothing has been declared.

Provisional items (do not treat as production policy)¶

Item	Status
Fraud automated approve / pend / block (`fraud-decision-v1`)	Provisional until compliance sign-off
Fraud escalation labels (`investigator_review`, `sar_review`)	Labels only, not filings
goAML helper Excel→XML chain	PARTIAL: often needs manual correction; no submission

What these ratings do not mean¶

A rating is not a statement about any particular customer environment.
UNKNOWN is not a soft "yes". It means the evidence was not available.
Ratings change only when new evidence (code on the deployed branch, tests, monitoring configuration, sign-off records) is added.