anchors settings

This agent’s LOCAL configuration — what is its own, not the project’s.

The `anchors.yaml` is the Structure: versioned, reviewed, the same for everyone.
What lives in `.anchors/settings.yaml` is the opposite — it holds for ONE agent on one machine,
and it does not go to git.

Today there is one decision here: whether this agent acts on ESCALATED cards
(`needs-user`), which await a decision from whoever knows the product.

Usage

anchors settings

Subcommands

anchors settings role

Declare the PROFILE of whoever operates this agent.

The profile says which work is yours, and the capabilities derive from it.

It is not hierarchy: the architect does not command the dev, he answers another question. And it
is not repository permission — git takes care of that. It is about WHAT WORK the agent pulls
from the board and HOW it behaves in the face of what it does not know.

The difference that shows up most: only `product-owner` and `architect` act on
ESCALATED cards (`needs-user`), which await a decision from whoever knows the product. The
other profiles escalate and move on to the next card.

Usage

anchors settings role [perfil] [flags]

Flags

Flag	Default	What it does
--date		REQUIRED — YYYY-MM-DD, the date of the declaration
--root	.	project root

anchors settings show

Show this agent’s local configuration.

Usage

anchors settings show [flags]

Flags

Flag	Default	What it does
--root	.	project root

anchors settings user-issues

Declare whether this agent acts on escalated cards (needs-user).

ESCALATED cards await a decision from whoever knows the product: the agent found
something that changes the direction and escalated instead of deciding alone.

In a project with several devs, each one can run their own agent — and not all of them can
decide for the product. An agent that picks up one of these cards and asks whoever is
running it gets an answer, and that answer may not be the project owner's.

The default is NOT to act. Whoever can decide declares that they can.

Usage

anchors settings user-issues [sim|nao] [flags]

Flags

Flag	Default	What it does
--date		REQUIRED — YYYY-MM-DD, the date of the decision
--root	.	project root

Setup and artifacts — family

Commands of the same family — what tells each apart:

Command	What it does
anchors init	Configure the project (anchors.yaml) through questions and answers
anchors new	Emit the skeleton of an artifact (spec, feature, test, plan…) per the ruler
anchors code	Generate a unique identity code for a new unit
anchors guide	Print the Anchors guides for AI agents
anchors docs	Compile the documentation from the templates in doct/
anchors install-hooks	Install the git pre-commit that runs the gates over staged files
anchors migrate	Bring the Anchors files up to the current format
anchors settings	This agent’s LOCAL configuration — what is its own, not the project’s
anchors touch	Bump updated_at in the @anchors header of the files that changed