Repository navigation
Wave 0 "VeriSimDB reachable": auth default-on off-localhost, persistent image, mount groove_router, PatternQuery reads the store #346
Description
From the standards ultraplan (docs/ULTRAPLAN-KAUTZ-LADDER-2026-10-19.adoc, Wave 0, "VeriSimDB reachable"). I re-checked each item against main at 137045a on 2026-11-04.
| Item | State on main | Proposed change | Why it needs an owner decision |
|---|---|---|---|
| Auth off by default | rust-core/verisim-api/src/auth.rs:43 has enabled: false |
Default to enabled = true when the bind address isn't loopback; keep it off on 127.0.0.1/::1; allow an explicit override |
Changes behaviour for every non-local deployment |
Image built without persistent |
container/Containerfile takes FEATURES="" by default, and no workflow passes FEATURES=persistent |
Build the published image with FEATURES=persistent (redb graph, file-backed Tantivy, WAL), or publish both tags |
Image size, and on-disk state the deployment must own |
groove_router() not mounted |
Defined at rust-core/verisim-api/src/groove.rs:738; only pub mod groove; refers to it |
.route(groove_router()) in lib.rs, the receiver for feedback-o-tron at /.well-known/groove/feedback |
It's a write endpoint, so mount it only after auth defaults on, or gate it behind auth |
PatternQuery misses ingested scans |
Reads the :hypatia_scans ETS that ScanIngester writes only in its failure branch |
Read from the store | None; this is a plain bug |
Suggested order: auth first, then groove_router (its safety depends on auth), then the image, then the standalone PatternQuery fix.
The deployment target is settled: a stapeln verified bundle on owned hardware, ruled 2026-10-19.
Activity