biagiolibe/cardine

> Meridian 1.4.0 and still installs and runs as meridian. Until Cardine 0.9,
> use Meridian 1.4.0.
> The scope of Cardine 1.0 is docs/ADRCARDINE10.md.
Meridian
Explicit tasks, isolated worktrees, verified integration. A delivery workflow for AI coding agents.
Meridian turns a project plan into bounded tasks that AI coding agents can implement, validate, and integrate with a durable record of the result. It supplies workflow instructions, templates, and a CLI; it is not an agent. It prescribes no application stack: each project owns its architecture, invariants, and validation commands. It runs from a local Git checkout, without a service or background process.
## Meridian in 30 seconds
A task makes the change and its proof explicit:
markdown
# Task 001 — Explain the configuration defaults
## Objective
Document the defaults used when no configuration file exists.
## Acceptance criteria
README lists each default and the command that overrides it.
## Validation
python3 scripts/checkdocs.py
In an initialized project, assign it to your agent:
text
Proceed with 001
For a Lean Delivery task, that directive authorizes the whole lifecycle: prepare an isolated task branch and worktree, implement the task, run its validation, record completion, validate the integration candidate, integrate, push main, and clean up the merged worktree. Each step proceeds only when its gates pass. A failed gate returns a concrete BLOCKED and a resume command.
Follow the quick start to initialize a project and close your first task.
## Features
Explicit tasks: objectives, acceptance criteria, context, and validation stay with the code.
Per-task worktrees: one branch, one checkout, and one writer per task isolate concurrent work.
Command-backed stops: lifecycle gates explain why work stopped and how to resume.
Denied destructive actions: task authorization excludes force pushes, history rewriting, tags, releases, and textual conflict resolution.
Migration-based upgrades: versioned baselines and three-way merges preserve project-owned changes.
Project console: inspect tasks, dependencies, worktrees, and the next permitted action with meridian console (experimental).
Host hooks: bounded reads, queue briefings, and stop audits reinforce the project workflow.
## Choose a workflow
Lean Delivery is the default starting point for small projects, prototypes, demos, and reversible changes. Tasks use [ ] → [/] → [x] and carry enough context to implement and verify one bounded change.
Governed SDD adds architectural authority, dependencies, execution evidence, and independent review for higher-risk work involving public APIs, security, persistence, state, or unresolved design decisions. SDD means spec-driven development: the task is the durable specification. Its lifecycle is QUEUED → INPROGRESS → READYFORREVIEW → ACCEPTED, with a direct acceptance path for eligible low-risk work.
Each project's PROJECTWORKFLOW.md locks its mode and takes precedence over global or remembered instructions. See the Lean guide and governed workflow.
## Install
Requires macOS or Linux, Python 3.12+, Git, and an installed, authenticated agent host. See platform support for the CI-tested matrix and best-effort integrations.