Skip to content

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.


AreaStatus
Client library: reads, evaluation and file sourcesDone, covered by golden vectors, precedence tests and concurrency stress
Host-local agent and detent getDone
Python and Rust bindingsBasic: file source only
Durable authorityComponent accepted; fleet-scale qualification open
Managed delivery and SDK sourceComponent accepted
Resumable subscriptions, relays, incremental publicationComponent accepted (Stage 5)
Sustained system, fleet and failure qualificationActive (Stage 6); sustained capacity remains unqualified
Updated libraries and remaining reusable-library extractionIn progress; required before the initial release

StageDeliverableState
0Architecture, contracts and failure assumptionsAccepted
1Legacy Raft safety correctionsAccepted; Xapiand compatibility retained
2Durable storage and strict consensusAccepted
3Bounded transaction API and authority runtimeAccepted
4Portable distribution and immutable local viewsAccepted, including managed agent and SDK
5Resumable delivery, subscriptions, relays, incremental publication5A, 5B and 5C components accepted
6Sustained system, fleet and failure qualificationActive; 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.


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.

  1. 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.
  2. Tagged releases with a changelog, and a version reported by the binaries.
  3. Continuous integration on Linux, macOS and FreeBSD, including the sanitizer runs.
  4. Packages: Homebrew bottles (the tap builds from source today), Debian/RPM, FreeBSD ports, container images, a Python wheel and a Rust crate.
  1. String, float and structured (JSON) knob types.
  2. Group overrides for int knobs.
  3. Knob metadata: owner, description, creation date and expiry, with stale-flag reporting.
  4. Rule-based targeting beyond exact group names, such as attribute matching or segments.
  1. A shipped command-line flag parser for CLI overrides (--knob name=value) and a config-path flag.
  2. An opt-in environment switch that freezes baked defaults for tests.
  3. Filesystem notifications for the file source instead of metadata polling.
  4. Python: read_view(), check(), category-specific exceptions, type stubs.
  5. Rust: views, structured errors, test guards.
  6. Go and Java bindings, and a documented stable reader ABI for the shared snapshot.
  7. A change-notification API for applications that want to react to updates.
  1. 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.
  2. Regional relays for fan-out have Stage 5B component acceptance; sustained fleet qualification remains in Stage 6.
  3. 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.
  1. A metrics endpoint (Prometheus/OpenMetrics) for the daemons, and an exporter for client counters.
  2. A versioned, documented schema for the authority’s health document.
  3. Audit history: who changed which knob when, with the ability to list and revert past versions.
  4. A publishing CLI (detent set, detent publish) so operators don’t need hand-written curl.
  5. A web UI for browsing and editing knobs.
  6. Dry-run validation of a snapshot or transaction without publishing it.
  1. Real network conditions, not only loopback.
  2. Multi-hour and multi-day soak tests.
  3. Fleet-scale fan-out at 1,000, 10,000 and 50,000 agents on enough hosts.
  4. Power-loss and filesystem-level durability on target hardware.
  5. 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.