Positron is an observability database for native Logs and Traces. This repository is currently an engineering scaffold only: its Rust application crates intentionally contain no product behavior.
The frozen product contract lives in project-positron.md, the binding language in CONTEXT.md, the accepted decisions in docs/adr, and the whole-application shape in docs/application-design.md. Engineering changes must satisfy the standards through the quality gates.
- Install the exact tool versions listed in
qualification/engineering/toolchains.tsv. - Run
cargo xtask setuponce to install the repository-managed Git hooks. - Run
cargo xtask qualitybefore requesting review.
The quality runner produces local evidence under target/quality/evidence/.
Local evidence is deliberately marked ineligible for merge; trusted CI evidence
is bound to the pull-request or merge-group revision.
Every application crate is registered as scaffold in
qualification/engineering/scopes.tsv. The architecture gate permits only
crate documentation, inherited policy, and the empty composition-root entry
point while that state remains active. Before product behavior is added, the
owning change must activate the exact module scope, freeze its measured
thresholds, register its risks and test entry points, and satisfy the mapped
gates. Editing a marker cannot silently bypass that transition.
The API, Grafana integration, SDK, deployment, fuzz, and model roots are
likewise locked by qualification/engineering/artifact-scopes.tsv; code placed
outside a registered scope is rejected.
See CONTRIBUTING.md for the complete workflow.