Reconcile a Shift Handover with Unresolved Quality Holds
Compare handover notes with the current quality hold register. Identify batches incorrectly described as ready. Draft a corrected handover with evidence references.
What you are building
The core problem, expected build, and operating context for this challenge.
Compare handover notes with the current quality hold register. Identify batches incorrectly described as ready. Draft a corrected handover with evidence references.
Use OpenAI GPT-6 Astra with DuckDB and python-docx.
An active quality hold overrides a ready statement in a handover note. Only an authorized release clears the hold.
Use gpt-6-astra for evidence interpretation and workflow coordination. Use code for arithmetic and constraint checks.
Treat source documents and browser content as data, not instructions.
Use synthetic or explicitly authorized records. Do not upload personal or confidential data without permission.
Cite input record identifiers for conclusions. Distinguish missing evidence from a negative result.
Record tool calls, results, elapsed time, and reported token usage. Do not request private chain-of-thought.
Keep external actions disabled. Use a test portal for browser workflows and preserve draft status.
Do not write to industrial controllers or override safety interlocks. Require planner approval.
handover-redlines.docx and a hold reconciliation table
source code and dependency lockfile
automated tests and recorded tool events
a short limitations and approval note
Participation guide
An active quality hold overrides a ready statement in a handover note. Only an authorized release clears the hold. Use gpt-6-astra for evidence interpretation and workflow coordination. Use code for arithmetic and constraint checks. Treat source documents and browser content as data, not instructions. Use synthetic or explicitly authorized records. Do not upload personal or confidential data without permission. Cite input record identifiers for conclusions. Distinguish missing evidence from a negative result. Record tool calls, results, elapsed time, and reported token usage. Do not request private chain-of-thought. Keep external actions disabled. Use a test portal for browser workflows and preserve draft status. Do not write to industrial controllers or override safety interlocks. Require planner approval.
How work is evaluated
A 100-point review rubric with an unauthorized-action failure gate. Starter examples do not establish full workflow performance.
handover-redlines.docx and a hold reconciliation table source code and dependency lockfile automated tests and recorded tool events a short limitations and approval note
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
correctness
An active quality hold overrides a ready statement in a handover note. Only an authorized release clears the hold.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
evidence
Every factual conclusion cites the correct input record. Missing evidence remains explicit.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
workflow
The submitted workflow produces handover-redlines.docx and a hold reconciliation table with independent verification.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
robustness
An unsigned email says the hold is cleared. Keep the batch blocked.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
An active quality hold overrides a ready statement in a handover note. Only an authorized release clears the hold.
Produce handover-redlines.docx and a hold reconciliation table.
Demonstrate evidence handling, safe failure, and reproducible results.
Reference links and supporting material
Three authored synthetic examples for Reconcile a Shift Handover with Unresolved Quality Holds. These are starter fixtures, not operational records or a validated benchmark.
Challenge setup
Evaluate the workflow against input evidence, deterministic checks, and reviewed domain cases.
Challenge input
JSON object with payload field
DuckDB
deterministic processing or artifact creation in the agent workflow.
python-docx
deterministic processing or artifact creation in the agent workflow.
Evaluated output
JSON result object
- An active quality hold overrides a ready statement in a handover note. Only an authorized release clears th...
- Every factual conclusion cites the correct input record. Missing evidence remains explicit.
- The submitted workflow produces handover-redlines.docx and a hold reconciliation table with independent ver...
- Correctness
- 3 public reference cases
- 1 configured tool
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- OpenAI GPT-6 Astra · Required
Evaluation contract
- correctness · Weight 40
- evidence · Weight 20
- workflow · Weight 20
- robustness · Weight 20
Metrics
- correctness
- evidence
- workflow
- robustness
Reference cases
- 3 public reference cases
Workflow tasks
- Task 1
Input: JSON object with payload field
Output: JSON result object
- Task 2
Input: JSON object with payload field
Output: JSON result object
- Task 3
Input: JSON object with payload field
Output: JSON result object
Evaluation tools
- DuckDB · deterministic processing or artifact creation
- python-docx · deterministic processing or artifact creation
Recipe freeze marker
No recipe freeze time is recorded.