Major system status
| System family | Status | Demonstrated boundary | Known limit |
|---|---|---|---|
| Workshop interface | Implemented | Qt/QML operational-interface components were implemented and tested at the recorded milestone. | Does not establish complete operating-environment orchestration. |
| Shard interaction family | Prototype | Lifecycle, focus/attention separation, keyboard access and reduced motion were reviewed in bounded prototypes. | Not a complete Shard Field or desktop. |
| Minimal runtime proof | Prototype | One interactive object, movement and restart restoration were tested. | Performance and tuning remain; no desktop replacement claim. |
| Command Centre and System Pulse | Implemented | Read-only state visibility, live/history distinction and unavailable-source labelling were implemented. | Some durable identity contracts remain incomplete. |
| Factory infrastructure | Partial | Session design, deterministic transitions, append-only logs and recovery checks were established. | Infrastructure is not training success or an authorised campaign. |
| Dataset Foundry | Qualification resumed | Dataset Foundry R0 candidates are conditionally ready but export remains unauthorised; a separate R1.1 corpus passed defined identity, regeneration, provenance and split checks. | No Dataset Foundry R0 target is ready; the R1.1 corpus is curated rather than exhaustive. |
| Nano-model research | Research only | A controlled R1.1 continuation reached its fixed ceiling and showed bounded development-set improvement. | Terminal verdict: revise candidate; frozen qualification thresholds were not met and sealed holdout evaluation remains unapproved. |
| Mobile runtime | Planned | Future relationship only. | No current mobile capability is claimed. |
| Security and R&D branches | Dormant | Research direction exists under controlled boundaries. | Implementation detail is intentionally not public. |
What has been validated
Recorded validation includes interface and interaction gates, prototype accessibility behaviour, restart restoration, truthful live-versus-historical state presentation, optional observability comparison, and factory/recovery machinery. These outcomes establish their stated bounded results only.
What has failed or remains unresolved
The prior R1.1 data-identity and split problem was corrected in a regenerated corpus, but the resulting research-only candidate remains below its frozen qualification thresholds. A relationship visualisation is deferred until stable identity data exists. Some planned systems have no public implementation evidence. These are retained as visible constraints rather than hidden behind roadmaps.
Evidence and provenance
Sources: KPCF-002 to KPCF-012, KPCF-014 to KPCF-020; Gate 9J, Gate 9K and Gate 9M canonical result records; Public Casefile Evidence Index; result records named in the private source manifest. Status labels are public summaries, not release certifications.