anchors compliance

The state of each regulatory duty: how many nodes subject, how many comply.

Shows, per DUTY, how many nodes are subject to it and how many comply.

The duties come from the adopted packs (`packs:` in anchors.yaml) and from the
obligations declared inline. Each line cites the norm that originates the duty — that is what
makes the report presentable to whoever audits, and not only to whoever programs.

A duty with subject nodes and none complying is usually a disconnection (the target changed
path and the pack points at the old place), not 100% violation — and the report
signals that instead of letting you conclude wrongly.

Uso

anchors compliance [flags]

Flags

Flag	Padrão	O que faz
--root	.	project root
--verbose		lists the nodes missing in each duty

Saúde do projeto — família

Comandos da mesma família — o que distingue cada um:

Comando	O que faz
anchors doctor	X-ray of the ecosystem: systemic loose ends, health and maturity
anchors audit	Dossier of one file’s pending items (gates + doctor), for batch fixing
anchors status	Where the project stands in the cycle, and what the next step is
anchors task-status	The round’s report: what is delivered, what remains, and what comes next
anchors compliance	The state of each regulatory duty: how many nodes subject, how many comply
anchors governs	Show who each guide governs (and how many) — sizes the audit per guide