Skip to main content
An escalation is a question that stops a stage until the Factory has a decision. Unlike a plan or PR gate, it asks for input such as a behavior choice, a dependency or a recovery action.

Answer an escalation

1

Read the current question

Check Inbox → Waiting on you or list open escalations. Read the question and its options before answering. An answer to a previous question does not decide a replacement question.
2

Send your decision

Use the escalation ID, not the run ID. For an open-ended question, give the missing requirement:
For a stopped stage with fixed choices, use an offered number or the exact choice text:
If the question is on a bound issue or Factory PR, reply where it was asked. If it was posted to Slack, reply in that question’s thread. Use the CLI if delivery or identity is uncertain. The Factory ignores its own replies. Comment replies are not authenticated the same way as gate approvals; a stored GitHub reply can be held if its author’s write access cannot be verified.
3

Check what happened

The first accepted answer decides the question. Usually the stage continues with your answer; a dependency option can keep it waiting or defer planning instead. Check runs show before sending another answer. Your local agent can relay your words, but shouldn’t choose for you.

Wait for a PR to merge

A wait mark belongs to an option offered by the stage, not to an arbitrary reply you type. For example, a stage might offer this single-PR option or the list form:
Choose the corresponding option by number (recommended) or its unambiguous printed text:
Use owner/repo#number, not a URL. The list has space-separated references inside one mark with at most eight distinct PRs. Every PR in the selected list must merge before the same stage can resume. An open or unreadable PR doesn’t count. If a dependency closes unmerged, or the Factory confirms an open dependency’s owning run ended without landing, it replaces the wait with a question. Read the replacement and decide whether to continue or cancel as offered.

Wait for an issue to close

A board-bound plan can offer one issue dependency at the end of a labelled option:
This defers planning, rather than keeping the plan stage open. The Factory looks for the GitHub issue to close or the latest Factory run for that dependency issue to finish as DONE. Use one issue per option. The mark is not available to a boardless run.

Recognize a deferred outcome

A plan’s explicit Defer planning option with a single PR mark can defer the run instead of waiting in place. A list of PRs is for waiting in place, not for a deferred plan. Check the outcome and dependency with architech factory runs show "$RUN_ID" --json.