anchors deliver

Record the delivery of a stage — the review trigger.

Closes a stage of the cycle by recording what was delivered in `changes/`.

The record has three parts, and the last two are what makes it useful:

  --intent      what you say you did (the DECLARED half of the confrontation)
  --decision    what the ruler did NOT decide and you chose alone
  --uncovered   what you KNOW is not proved

The last two may look optional and are not: a silent decision is the origin of most
of the defects that cross the gates (everything exists, everything references
everything, and someone chose alone). Declaring them is what separates assumed debt
from forgetting.

Example:

  anchors deliver --stage code --unit src/business-logic/pricing.ts \
    --file src/business-logic/pricing.ts --file src/business-logic/pricing.feature \
    --intent "implements PRICX-B01..B04; the carry-forward uses lexicographic comparison" \
    --decision "month outside YYYY-MM: I assumed valid input (the spec does not decide)" \
    --uncovered "PRICX-B04 has no scenario — the edge case depends on phase 2"

After this, the watcher queues the review task.

Usage

anchors deliver [flags]

Flags

Flag	Default	What it does
--agent		who delivered (optional)
--card	0	github mode: the card to record on, instead of finding it by the unit’s code (a plan card with no [CODE] in its title, or a change to generated files only)
--date		YYYY-MM-DD (REQUIRED — Anchors does not read the clock)
--decision		choice the ruler did not decide (repeatable)
--file		file touched (repeatable)
--intent		REQUIRED — what you claim to have done
--root	.	project root
--stage		REQUIRED — stage delivered: spec|code|feature|test|plan
--uncovered		what you know is not proven (repeatable)
--unit		REQUIRED — the file that identifies the unit of purpose

The work queue — family

Commands of the same family — what tells each apart:

Command	What it does
anchors next	Pull and claim the next item from the queue (the worker calls this)
anchors queue	List live tasks (the work the watcher queued)
anchors work	Emit the work prompt of a stage (spec|code|feature|test|review) for a target
anchors done	Close claimed task(s) (moves to the .anchors/done/ history)
anchors drop	Discard a task from the queue without completing it (removes; does not archive)
anchors reclaim	Return to the queue the tasks stuck in claimed (dead worker)
anchors deliver	Record the delivery of a stage — the review trigger
anchors decided	Release the card escalate --for-user stopped, once the decision is made
anchors discard	Take off the board the card that no longer makes sense, without deleting it
anchors unblock	Open the work card that unblocks a card stuck in needs-user
anchors escalate	Open the issue for a change needed in the plan or the spec
anchors report-bug	Report a bug in Anchors itself at github.com/co2-lab/anchors
anchors synthesize	Two PRs conflicting in CONTENT become a synthesis card
anchors watch	The background watcher: sees changes and QUEUES work
anchors monitor	Watch the project’s long processes: one line when one starts, stalls, dies or ends
anchors flow	Operate the work flows (the puzzle of actions and results)
anchors board	The project board — published by the pipeline, or served live