phpbotscout review clarify¶
review clarify walks the clarifying questions the bot asked instead of answering, oldest first,
and records whether asking back was right. Its verdicts are kept apart from review's, so none of
them counts towards the thirty reviewed answers that gate posting
(spec 0031 D11).
Usage¶
$ phpbotscout review clarify
Clarification 41 · shadow · recorded 2026-11-02 14:03
Question: how do I load config?
It asked: Do you mean `go/config` or `rust/config`, or config in general? Reply here and I'll answer for the one you mean.
Replied: yes
Passages by reading:
3 phpboyscout/go/config
3 phpboyscout/rust/config
Top shares: 0.375, 0.375 (split_share 0.375)
Bare words: config → phpboyscout/go/config, phpboyscout/rust/config (name_passages 2)
Decided on: name, offering phpboyscout/go/config, phpboyscout/rust/config
Then one choice:
| Choice | Records |
|---|---|
| Yes, asking back was right | right |
| No, one reading was plainly meant | wrong, reason one_meant |
| No, the offer missed the reading that was meant | wrong, reason offer_missed |
| Skip it for now | nothing, and it is offered again next run |
| Exclude it | taken out of the count, for a replayed benchmark or calibration question |
| Quit | nothing, and the walk ends |
A verdict is followed by an optional note, redacted as review's notes are. The walk ends with the
clarify line of review status.
Replied says whether a later record answers the same question, which is what the asker's reply
produces. That answer is an ordinary one, in review, and counts towards the thirty.
How long it is kept¶
A note is cleared when the clarifying question's own text expires, after 120 days. The verdict stays.
Flags¶
| Flag | Meaning |
|---|---|
--server <id> |
The server whose clarifications to review. Required when more than one server is configured, and implied when there is one. |
Like review, it needs an interactive terminal, or GTB_ACCESSIBLE=true to answer line by line
on a piped stdin.