Roadmap
Detent is a work in progress with a complete architecture and a careful, staged implementation. This page states plainly what works today, what’s in progress, and what’s still missing. Items marked as unimplemented elsewhere in these docs are collected here.
Status at a Glance
Section titled “Status at a Glance”| Area | Status |
|---|---|
| Client library: reads, evaluation and file sources | Done, covered by golden vectors, precedence tests and concurrency stress |
Host-local agent and detent get | Done |
| Python and Rust bindings | Basic: file source only |
| Durable authority | Component accepted; fleet-scale qualification open |
| Managed delivery and SDK source | Component accepted |
| Resumable subscriptions, relays, incremental publication | Component accepted (Stage 5) |
| Sustained system, fleet and failure qualification | Active (Stage 6); sustained capacity remains unqualified |
| Updated libraries and remaining reusable-library extraction | In progress; required before the initial release |
Implementation Stages
Section titled “Implementation Stages”| Stage | Deliverable | State |
|---|---|---|
| 0 | Architecture, contracts and failure assumptions | Accepted |
| 1 | Legacy Raft safety corrections | Accepted; Xapiand compatibility retained |
| 2 | Durable storage and strict consensus | Accepted |
| 3 | Bounded transaction API and authority runtime | Accepted |
| 4 | Portable distribution and immutable local views | Accepted, including managed agent and SDK |
| 5 | Resumable delivery, subscriptions, relays, incremental publication | 5A, 5B and 5C components accepted |
| 6 | Sustained system, fleet and failure qualification | Active; short 10k-session functional evidence, sustained qualification open |
The planning workload for stages 5 and 6 is 500,000 knobs, 300 concurrent publishers, 1,000 transactions per second and 50,000 agents. Those are test targets, not demonstrated capacity.
Build and Release
Section titled “Build and Release”The release execution plan tracks the remaining gates. It includes updated-library qualification and extraction of shared HTTP clients, bounded MessagePack, the persistent map and resource primitives. Final system qualification uses the resulting pinned library closure.
- Qualify dependency updates against the existing immutable pins before adopting them. The M1 move to every library’s head is done and recorded in the changelog.
- Tagged releases with a changelog, and a version reported by the binaries.
- Continuous integration on Linux, macOS and FreeBSD, including the sanitizer runs.
- Packages: Homebrew bottles (the tap builds from source today), Debian/RPM, FreeBSD ports, container images, a Python wheel and a Rust crate.
Knob Model
Section titled “Knob Model”- String, float and structured (JSON) knob types.
- Group overrides for int knobs.
- Knob metadata: owner, description, creation date and expiry, with stale-flag reporting.
- Rule-based targeting beyond exact group names, such as attribute matching or segments.
Client and Bindings
Section titled “Client and Bindings”- A shipped command-line flag parser for CLI overrides
(
--knob name=value) and a config-path flag. - An opt-in environment switch that freezes baked defaults for tests.
- Filesystem notifications for the file source instead of metadata polling.
- Python:
read_view(),check(), category-specific exceptions, type stubs. - Rust: views, structured errors, test guards.
- Go and Java bindings, and a documented stable reader ABI for the shared snapshot.
- A change-notification API for applications that want to react to updates.
Distribution
Section titled “Distribution”- Resumable subscriptions with snapshot/history handoff and durable publication feedback have Stage 5A component acceptance. Native, sanitizer and focused supported-platform checks establish component behavior; sustained fleet capacity remains a Stage 6 qualification target.
- Regional relays for fan-out have Stage 5B component acceptance; sustained fleet qualification remains in Stage 6.
- Incremental page publication, warm recovery, shared-segment reclamation, migration and bounded maintenance have private-component source GO and affected native/platform/sanitizer qualification. Opt-in agent/relay format configuration is under assembled-process qualification; sustained pressure and fleet capacity remain in Stage 6.
Operations and Observability
Section titled “Operations and Observability”- A metrics endpoint (Prometheus/OpenMetrics) for the daemons, and an exporter for client counters.
- A versioned, documented schema for the authority’s health document.
- Audit history: who changed which knob when, with the ability to list and revert past versions.
- A publishing CLI (
detent set,detent publish) so operators don’t need hand-writtencurl. - A web UI for browsing and editing knobs.
- Dry-run validation of a snapshot or transaction without publishing it.
Qualification
Section titled “Qualification”- Real network conditions, not only loopback.
- Multi-hour and multi-day soak tests.
- Fleet-scale fan-out at 1,000, 10,000 and 50,000 agents on enough hosts.
- Power-loss and filesystem-level durability on target hardware.
- Combined pressure/churn and whole-service telemetry overhead for the authority.
The shared-segment collector, warm recovery, mapped admission and paged delivery have component acceptance, including affected Linux, FreeBSD, ASan/UBSan and TSan checks. Controlled contention attributes the native 500k feedback failure to a fixture observer deadline; production deadlines remain unchanged. Earlier Linux shared-host pressure failures retain a separate attribution gap. Short 10k-session transport checks do not establish 10k durable-agent capacity. Sustained workload, fresh-group restore, combined resource conservation and clean deployment qualification remain open.