cartulary
The knowledge layer of your project — decisions, issues, docs, all in one place.
⚠️ Status: Alpha —
cartularyis under active development. The CLI surface andcartulary.tomlschema may change in incompatible ways before1.0. Pin a specific version (--version "0.1.0-alpha.1") and watchCHANGELOG.mdbefore upgrading.
cartulary is a CLI tool to manage everything that gives context to your project: Architecture Decision Records (ADR), Design Decision Records (DDR), issues, and project documentation. Everything lives as plain Markdown in your repository.
📚 Documentation
- Concepts — the domain vocabulary, one page per concept:
docs/pages/concepts/. Same content offline viacartu man <name>. - CLI reference — every subcommand and flag:
docs/pages/reference/cli/. - Configuration — the
cartulary.tomlschema:docs/pages/reference/config/. - Workflows — built-in status presets and the decision-record lifecycle:
docs/pages/reference/workflows/.
You can also find all the documentation pages online at this address: crazy-crafters.gitlab.io/cartulary
🚀 Installation
Pre-built binary (recommended)
Download the archive for your platform from the GitLab Releases page. One-liner for Linux x86_64:
VERSION="0.1.0-alpha.1"
TARGET="x86_64-unknown-linux-gnu"
|
Available targets: x86_64-unknown-linux-gnu, aarch64-unknown-linux-gnu, x86_64-pc-windows-gnu. macOS users compile from source via cargo install (next section). Verify the archive against the SHA256SUMS file attached to the same release.
For Windows: download cartu-{version}-x86_64-pc-windows-gnu.zip, unzip, place cartu.exe on your PATH.
Via cargo binstall (no compilation)
If you have cargo-binstall:
cartulary ships a [package.metadata.binstall] block pointing at the GitLab Release artefacts — binstall picks the right archive for your platform.
Via cargo install (compile from source)
Compiles from the published crate on crates.io. Requires Rust 1.88+ via rustup.rs.
Build from source (contributors)
Requires Rust 1.88+. Beyond rustc/cargo, the dev workflow expects just (recipe runner) and cargo-llvm-cov (coverage). Nix users get them automatically via the flake (nix develop); other contributors should install them manually:
⚡ 30-second tour
Pick the next thread from the documentation section above.
🔎 Similar tools
| Tool | Category | Decision records | Issue tracking | Flow metrics | Plain files | Single binary |
|---|---|---|---|---|---|---|
| adr-tools | ADR CLI | ✅ | ❌ | ❌ | ✅ | ❌ |
| log4brains | ADR + web UI | ✅ | ❌ | ❌ | ✅ | ❌ |
| git-bug | Issue tracker | ❌ | ✅ | ❌ | ❌ | ✅ |
| git-issue | Issue tracker | ❌ | ✅ | ❌ | ✅ | ❌ |
| cartulary | ADR + issues | ✅ | ✅ | ✅ | ✅ | ✅ |
The market is split: ADR tools have no issue tracking, issue trackers have no decision records. cartulary covers both, plus flow metrics, structural validation, and a ULID-based identifier scheme that survives parallel branches. See market-benchmark.md for the full analysis.
🤝 Contributing
Contributions welcome — open an issue or submit a merge request.
cartulary enforces Conventional Commits 1.0.0 (rationale in ADR-0019). Allowed types: feat, fix, docs, refactor, perf, test, build, ci, chore, style. Subject in imperative mood, lowercase, no trailing period, ≤72 chars. CI rejects non-conforming commits; to get the same check locally:
Releases are cut by maintainers with cargo release --execute X.Y.Z, which runs git-cliff to update CHANGELOG.md and triggers cargo publish + GitLab Release artefacts on tag push. Maintainers either enter the Nix dev shell (nix develop, which ships cargo-release and git-cliff) or install the two tools manually:
📄 License
CeCILL
🎨 Credits
Logo: Book cover by Lorc, from game-icons.net, licensed under CC BY 3.0.