AI Analysis Layer — component status
Published under MCC-400 art. 95.1 (decision D-2026-08-11, in force 17 September 2026).
Read live from the registry database on each request. The platform watchdog last recorded these checks on 30 August 2026.
| Component | Status | Most recent output | Continuous coverage from |
|---|---|---|---|
Completeness Engine MCC-400 art. 95(a) | Operational last analysis 92 days ago; every submission presented has produced one | 30 May 2026 | 30 May 2026 |
Cross-Reference Engine MCC-400 art. 95(b) | Operational last analysis 92 days ago; every submission presented has produced one | 30 May 2026 | 30 May 2026 |
Risk Flag Engine MCC-400 art. 95(c) | Operational last analysis 92 days ago; every submission presented has produced one | 30 May 2026 | 30 May 2026 |
Per-section confidence scoring MCC-400 art. 95(e) | Operational last analysis 92 days ago; every submission presented has produced one | 30 May 2026 | 30 May 2026 |
Continuous Monitoring Engine MCC-400 art. 95(d) | Operational last snapshot 11 days ago | 19 August 2026 | 18 August 2026 |
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.