The composition cites the collection and waits for a person. It does not negotiate or write to a CRM.
Deal review
Review one fictional clause and record a human decision. Hands-on time is about 30 minutes. No message is sent to a customer.
Purpose
You can show a reviewer the citation, a conflict, or a gap. Level: editor plus a named reviewer. Mode: stored. Scope: one workspace, the example collection only.
Prerequisites
harbor-note.txt is indexed. You also upload a second fictional file, harbor-conflict.txt, containing only: Harbor Sample delivery window is 30 days. Extract both. Do not use a live contract.
Sample
Question: What delivery window should Harbor Sample use? Known-answer case uses only the 14-day note and expects a citation. Conflict case confirms refs from both notes and expects the reviewer to refuse a single number. Silence case asks who pays, and expects no decision.
Steps
- Search the collection for the window. Confirm only the refs you will show the reviewer.
- Write the answer request. If status is
grounded, the citation is the packet. If two windows appear, do not average them. - On the workflow canvas, keep a manual approval step in front of any result you would store as the decision. Publish and run only if your workspace already has that approved node. If it does not, stop after the packet and record the decision outside the product.
- The reviewer chooses
accept 14 days,conflict, orinsufficient. There is no send button in this recipe.
Fields
| Decision | When |
|---|---|
accept 14 days | One citation, excerpt says 14 days, no second window in the confirmed set. |
conflict | Confirmed excerpts disagree. |
insufficient | No excerpt states a window, or the question was about a payer. |
Example
{"deal":"HS-104","question":"What delivery window should Harbor Sample use?","decision":"conflict","citations":["14 days","30 days"]}That JSON is your review note. It is not a Bundata CRM write.
Recovery
If evidence goes stale before the reviewer finishes, search again. Do not approve a packet whose refs return source_changed. A model preference for 14 or 30 is not a resolution.
Limits
No autonomous negotiation, no CRM update, no cross-workspace search, and no template named Deal Desk unless that template is installed and you have run it. This cookbook does not assume it is installed.
Check
Success: the 14-day-only packet has one citation and the reviewer accepts it. Failure: both files are confirmed and the recorded decision is conflict, not a blended 22-day window.