James Maes
514f8eb15b
Sweep every README/doc for accuracy and remove fabricated or stale content: - README/CLAUDE: add the live roadmap-page link and a rule to keep the rendered page in sync with docs/ROADMAP.md; fix the stale cov alias and the already-moved-shells note. - .github/CONTRIBUTING+SECURITY: drop the fabricated nuncio.mx site link and the aspirational release/security claims; state honest pre-alpha status. - docs/RUNNING, DEVELOPING, ARCHITECTURE, BACKLOG, Home, NSQL spec, corruption notes, proto/README: correct crate count/list, service list, CLI flags, phase status, and remove claims of unshipped/removed things (IPC-as-current, hardcoded-keys, unwired engines); mark superseded api-surface-draft historical. - Remove the fabricated benchmark baked into nsql_pipeline.svg and delete the orphaned ipc_sequence.svg (depicted the removed IPC with a fake timing).
794 B
794 B
Database Corruption Detection & Self-Healing Engine
Status: the detection/backup/salvage machinery is real and tested. The two defects tracked in
BACKLOG.md(Phase 1.B) — transient errors (pool timeout /SQLITE_BUSY) being mis-classified as corruption and deleting a live DB, and rule salvage targeting the wrong schema so filter rules were never restored — are both fixed (crates/nuncio-store/src/recovery.rs).
Nuncio features a 4-Stage Database Corruption Recovery and Self-Healing Engine.
1. 4-Stage Self-Healing Recovery Flowchart
(No diagram is currently checked in for this pipeline — the image previously embedded here was the NSQL filter compiler pipeline, not the self-healing recovery flow, and has been removed as inaccurate.)