Skip to content

Design Documents

Detent’s engineering record lives in the repository, next to the code. These documents are written for contributors: they record decisions, acceptance gates, measurements and audit findings in more depth than this site.


DocumentWhat it covers
knob-model.mdThe knob model: names, groups, overrides, rollout, evaluation and the JSON formats
DocumentWhat it covers
VALIDATED_ARCHITECTURE.mdThe reviewed large-state architecture and its stage gates
SCALING.mdCapacity model, the 100k/500k-knob baseline, and the scaling plan
AUTHORITY_ARCHITECTURE.mdThe bounded authority application and runtime
ASYNC_AUTHORITY_ARCHITECTURE.mdAuthenticated multi-node transport and completion-based I/O
AUTHORITY_TRANSPORT.mdPeer hello, framing, TLS and fixed-voter configuration
AUTHORITY_READINESS.mdCheckpoint ownership, admission, telemetry and qualification
AUTHORITY_EXPORT.mdScoped export, change history and the distribution endpoint
DISTRIBUTION_ARCHITECTURE.mdPortable distribution and immutable local publication
DISTRIBUTION_CODEC.mdThe codec comparison behind the MessagePack choice
DELIVERY_INTEGRATION_ARCHITECTURE.mdAuthenticated authority-to-local-view delivery
SUBSCRIPTIONS_ARCHITECTURE.mdStage 5A sessions, snapshot/history handoff and durable publication feedback; implementation in progress
LOCAL_IMAGE_FORMAT.mdThe generation image and descriptor formats
DISK_LIFECYCLE_ARCHITECTURE.mdDurable ownership, census and lease-protected GC
COMPLETION_ALLOCATION_ARCHITECTURE.mdPhysical admission through completion controls
DocumentWhat it covers
IMPLEMENTATION.mdStage-by-stage implementation status
AUDIT.mdThe ongoing source audit and every fix it produced
AUTHORITY_COMPONENT_REVIEW.mdThe consolidated authority review
LINUX_COMPLETION.mdio_uring storage qualification
benchmarks/*.jsonRaw measurement artifacts
DocumentWhat it covers
USAGE.mdDeployment scenarios, end to end
SERVICES.mdService accounts, directories and supervision
LOGGING.mdDaemon logging and its measured footprint