anchors freeze

Freeze the project: nobody works until anchors thaw.

Stops the work on the entire project, in three layers.

  1. writes 'enabled: false' and the reason into anchors.yaml, and PUSHES
  2. creates a ruleset on the remote that blocks push and merge on every branch
  3. opens an issue with the reason, so whoever hits the brake knows what happened

The --reason is MANDATORY. A freeze with no written reason is indistinguishable from
broken configuration, and whoever hits it tries to work around it instead of reading.

The commit and the push are made with --no-verify, on purpose: the hooks that this
command has just activated would refuse the freeze itself.

WHOEVER FIXES IT PASSES. The admin bypasses the ruleset, and '--no-verify' bypasses the
hooks — the brake exists to stop work by INERTIA, not the fix that
releases it.

Usage

anchors freeze [flags]

Flags

Flag	Default	What it does
`--no-push`		do not commit or push anchors.yaml
`--no-ruleset`		do not create the ruleset on the remote (only the local brake)
`--reason`		why the project is being frozen (required)
`--root`	`.`	project root

Freezing the project — family

Commands of the same family — what tells each apart:

Command	What it does
`anchors freeze`	Freeze the project: nobody works until `anchors thaw`
`anchors thaw`	Thaw the project: work resumes

When a project reaches a release candidate or production milestone, you must prevent accidental code modifications while allowing inspection and audit commands to run.

1. Freezing the Project (`anchors freeze`)

# Freeze the project with an audit rationale
anchors freeze --reason="v2.0.0 Release Candidate verification"

When frozen:

All mutating commands (new, work, deliver, map build) are strictly blocked.
Read-only diagnostics (status, doctor, guide, coverage, version) continue to function.

2. Unfreezing (`anchors thaw`)

anchors thaw

Resumes normal development activities and unlocks the task queue.