Feature · Settings
Decision record
One decision a worker made, with its inputs and result.
How it works
What a typed decision is
A typed decision is a small, repeated choice with a fixed set of answers, for example what kind of message just arrived. A rule, a small typed model (an "arm") or a large model can answer it.
Modes
- off: a rule, then the large model. No typed arm is asked.
- shadow: the large model decides. A typed arm answers beside it and Crewshal measures how often they agree.
- primary: confident typed answers are used. The rest go to the large model.
- auto: shadow until the measured agreement is high enough, then primary. It goes back when agreement drops.
The page
Decisions shows, for each purpose over 24 hours, 7 days or 30 days: calls, rule hits, typed answers, agreement, overrides, speed, cost and escalations. Only owners and admins change the mode and the threshold.
From the help article Typed decisions, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewergetDeliverySubjectRecordGets the delivery subject record.
Types:
GetDeliverySubjectRecordRequestreturnsDeliverySubjectRecordDto
ViewerlistDeliverySourceReceiptsLists delivery source receipts.
Types:
ListDeliverySourceReceiptsRequestreturnsListDeliverySourceReceiptsResponse
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
Screens
/decisions/decisions/:id