When to use it
During design, pilot preparation and changes to system boundaries.
Fields to complete
| Field | Your notes |
|---|---|
| User task and trigger | Add known information, your judgment or an open question. |
| Identity, accessible data and valid versions | Add known information, your judgment or an open question. |
| Steps handled by rules, retrieval and models | Add known information, your judgment or an open question. |
| Tool actions and who authorizes them | Add known information, your judgment or an open question. |
| Reviewer information, time and right to reject | Add known information, your judgment or an open question. |
| Handling for success, failure and unknown outcomes | Add known information, your judgment or an open question. |
| Correction, takeover, appeal and exit | Add known information, your judgment or an open question. |
| Authoritative record and recovery owner | Add known information, your judgment or an open question. |
Example entry
Proposed workflow: the model prepares a parts recommendation, an engineer confirms, then a tool submits. Submission needs testing and authorization first; it is excluded from the initial Beichen pilot. After a timeout, show “Awaiting confirmation” and check request records before retrying.
From the fictional Beichen case. This shows one way to write an entry; your analysis may lead to a different choice.Check your work
Rejection stops the action, unknown outcomes are not shown as complete, and overnight takeover has available staff.