AI Analysis Layer — component status
Published under the Transparency and Public Disclosure Policy v1.1, art. 1 and §2.6. MCC-400 art. 95.1, which this page formerly cited, arrives with an Addendum whose entry into force is stayed (FD-2026-09-03 item D8) and has never applied; the disclosure is made anyway.
Read live from the registry database on each request. The platform watchdog last recorded these checks on 15 October 2026.
| Component | Status | Most recent output | Continuous coverage from |
|---|---|---|---|
Completeness Engine MCC-400 art. 95(a) | Operational last analysis 43 days ago; every submission presented has produced one | 2 September 2026 | 2 September 2026 |
Cross-Reference Engine MCC-400 art. 95(b) | Operational last analysis 43 days ago; every submission presented has produced one | 2 September 2026 | 2 September 2026 |
Risk Flag Engine MCC-400 art. 95(c) | Operational last analysis 43 days ago; every submission presented has produced one | 2 September 2026 | 2 September 2026 |
Per-section confidence scoring MCC-400 art. 95(e) | Operational last analysis 43 days ago; every submission presented has produced one | 2 September 2026 | 2 September 2026 |
Continuous Monitoring Engine MCC-400 art. 95(d) | Not operational no snapshot has ever been recorded — no registered project carries a monitoring boundary yet; the engine starts automatically when a project boundary is registered | — | — |
What is unavailable as a result
- MCC-400 art. 95.1 — no requirement, timeline, sampling reduction or fee expectation may rest on this component
- MCC-400 art. 114 — no indicative fee or effort reduction relying on this component may be published or communicated to any VVB
- MCC-400 art. 109 — the thirty-business-day subsequent verification timeline is unavailable; art. 108 (sixty days) applies
How to read this page
Operational means the component produced output for the inputs presented to it. Idle means no input was presented — the completeness engine produces nothing when no project has been submitted, which is not a fault. Not operational means expected output is absent, and the consequences under art. 95.1 apply.
The Continuous Monitoring Engine is schedule-driven and polls on a monthly cron. It has no external trigger, so it is never idle: an absence of output is a failure.
Art. 95.1 as adopted does not define idleness. The distinction applied here between a component that was asked and did not answer, and one that was never asked, is the Programme Administrator’s reading, and has been recommended for codification in the next amendment to MCC-400.