Contract acceptance
Required deliverables were mapped, validated, packaged, and accepted.
Reproducible checks for contract compilation, package integrity, receiver acceptance, private-output exclusion, and autonomous MCP tool flow.
A local qwen3:8b agent received the objective and available MCP tools without tool names in the user prompt. It selected the contract compiler, followed the handoff with integrity inspection, and returned the receiver's decision and next action.
Required deliverables were mapped, validated, packaged, and accepted.
An incomplete contract returned actionable unmet requirements without creating a package.
Deliverable SHA-256 hashes, expiry, and contract satisfaction were verified.
Private notes were excluded from the receiver package and absent from the ZIP.
report.md, evidence.csv, summary.json, manifest.json, and handoff.json were present.
The model selected compile_handoff and inspect_handoff in the correct order.
| Model | qwen3:8b via Ollama |
|---|---|
| Tool sequence | compile_handoff → inspect_handoff |
| Receiver decision | accepted |
| Next action | consume_deliverables |
| Package files | report.md, evidence.csv, summary.json, manifest.json, handoff.json |
| Private output | private-notes.txt excluded |