Client Handoff Packet
Agreed Requirements
R1: Every claim needs a nonblank ID, positive finite numeric amount (not a boolean), and status new/review/closed. R2: Invalid claims return all applicable validation errors. The input is not modified. R3: Acceptance needs recorded evidence for valid inputs, invalid inputs, and nonmutation.
Implementer’s Completion Note
All work is complete. The feature is accepted and ready for client handover.
Attached Validation Evidence
- One valid claim with amount 10 returned no errors.
- No recorded invalid-input or nonmutation checks.
Proposed Logic Extract
if not claim.get('amount'):
errors.append('amount_invalid')Client Follow-up
We may also need to reject claims above a policy-specific limit. The limits and authoritative source have not been supplied. Is that already included?
Learner Task
Decide whether the agreed requirements are supported by the supplied evidence. Identify a concrete counterexample, distinguish missing evidence from a demonstrated defect, and route each finding. Identify the scope decision for the follow-up request. Produce a handoff with status, evidence, unresolved items, and owners. Do not silently invent a policy limit.