You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Pull request template**: opening a PR fills the body from [`.github/pull_request_template.md`](.github/pull_request_template.md), which ends with four type checkboxes - `Component`, `Requirement`, `Sampling Strategy`, `Tool`. If your PR adds or modifies one of those, check the matching box; the `PR Bot` workflow ([`.github/workflows/pr-update.yml`](.github/workflows/pr-update.yml)) then posts a comment with the type-specific review checklist from `.github/PULL_REQUEST_TEMPLATE/`:
This matters when a PR is opened outside the GitHub UI (`gh pr create --body`, from a fork, or by an agent): the template isn't applied automatically. When you open such a PR and it adds or modifies one of the four types, build the body from `.github/pull_request_template.md` with the matching box checked (if relevant) so the bot posts the checklist.
110
+
100
111
**Review states**: when reviewing a PR, see [CONTRIBUTING.md → Review States](CONTRIBUTING.md#review-states) for when to use `APPROVE` vs `REQUEST CHANGES` vs `COMMENT`.
101
112
102
113
For AI attribution trailers, see [Section 7 (AI Attribution)](#7-ai-attribution).
Copy file name to clipboardExpand all lines: docs/docs/concepts/requirements-system.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,6 +162,7 @@ last output.
162
162
|`score`|`float \| None`| Optional numeric score from your validator. |
163
163
|`thunk`|`ModelOutputThunk \| None`| The model output used, if your validator ran a backend call. |
164
164
|`context`|`Context \| None`| The context snapshot at validation time. |
165
+
|`error`|`Exception \| None`| The exception raised while parsing validator output, if any. When set, `bool(result)` is `False` (fails closed) and `reason` is `None`; lets callers tell an unparsable response apart from an ordinary "requirement not met". |
165
166
166
167
The `reason` field is the most useful in practice — a clear reason string helps the
167
168
model make a targeted repair rather than regenerating blindly.
0 commit comments