writ issue

Issue a writ and supervise the run.

writ issue <file>

The command validates the file, engages the holder model, and runs the loop. The registrar examines each action against the terms. The command shows the record while the run continues.

Flags

Flag	Purpose
--set <name>=<value>	Give a placeholder a value. Use the flag more than one time for more than one placeholder.
--config <path>	Use the engagement configuration at this path.

Before you issue

You must configure the engagement first. The registrar cannot engage a model without a holder, a price, and an API key.

Writ reads the API key from the environment variable that key_env names.

Give a value to each placeholder

writ issue bug-fixer.yaml \
  --set failing_test=tests/test_sync.py::test_retry \
  --set failing_test_file=tests/test_sync.py

The command stops with an error when a placeholder has no value. Read more about placeholders.

What stops a run

Cause	Exit code
The satisfaction clauses pass.	0
A bound stops the run, or a remedy stops the run.	1
The file is not valid.	2
The configuration is wrong.	3

Writs that this command refuses

The command stops with an error in these two cases:

• The writ contains an mcp grant. An mcp grant works only in sidecar mode.
• The writ contains a reserved field: issued_by, requires, yields, or holder_must. Delegation ships in version 2.

The command also stops when a term needs something that the configuration does not have:

• A judgment clause needs a judge.
• A clause or a grant that needs assent needs an assent transport.

After the run

Read the record:

writ record bug-fixer

The record shows each action and each check, including the actions that the registrar denied. Read more about the record.