docs(adr): 0009-build-path#97
Merged
Merged
Conversation
…perimental Closes #61. Four parallel build-environment definitions (`flake.nix`, `.guix-channel` / `guix.scm`, `Containerfile`, `.devcontainer/`) plus the implicit `cargo build` lived side-by-side. None was documented as canonical, so new contributors had to guess. ADR-0009 picks **two canonical paths**: - **`cargo build` for development.** Direct Rust toolchain, fastest iteration, MSRV-pinned via V-L3-K1 (#57). - **`Containerfile` for ops.** OCI image suitable for deployment, CI, reproducible release builds. Complementary to the V-L3-L1 (#58) release workflow that produces native binaries. Everything else (`flake.nix`, `guix.scm`, `.guix-channel`, `.devcontainer/`) is **experimental**: kept in the tree, not maintained, not CI-tested. Re-promotable via a future ADR if a maintainer emerges. Alternatives considered: - Pick exactly one path: rejected; dev vs ops have legitimately different cost-benefit profiles. - Delete the experimental files: rejected; no CI cost to keeping them, someone put work in. Follow-up: small README "Install" rewrite (separate PR). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per V-L3-P1: four build-environment files (
flake.nix,guix.scm/.guix-channel,Containerfile,.devcontainer/) plus implicitcargo buildcoexisted, none documented as canonical.ADR-0009 picks two canonical paths:
cargo buildfor dev. Direct toolchain, fastest iteration, MSRV-pinned (V-L3-K1, V-L3-K1: add rust-version (MSRV) to Cargo.toml; CI matrix #57).Containerfilefor ops. OCI image for deployment, CI, reproducible release builds. Complements the V-L3-L1 (V-L3-L1: add release workflow building binaries for 4 targets #58) native-binary release workflow.Everything else is experimental — kept in the tree, not maintained, not CI-tested. Re-promotable later if a maintainer emerges.
Alternatives considered: "pick exactly one" (rejected — dev and ops are legitimately different) and "delete experimental files" (rejected — no CI cost to keeping them).
Follow-up: small README "Install" rewrite as a separate PR.
Closes
Test plan
docs/decisions/0009-build-path.adocrecords the decision + alternatives + consequencesDoc-only.