Output Contracts

Output Contracts

Machine-readable contracts allow downstream tools to distinguish a usable artifact from a draft or blocked run.

Core records

File	Role
estimate-package.json	Canonical estimate input and normalized line items
normalized-bom.json	Validated BOM view used by later stages
nest-result.json	Placement, stock, metrics, geometry status, and findings
rfq-nesting.json	RFQ-facing nesting projection
workbook-semantic.json	Deterministic semantic representation of the draft workbook
qa-report.json	Overall outcome, readiness label, warnings, and stage results
run-manifest.json	Artifact hashes, lineage, configuration, and publication state

JSON schemas live under skills/_shared/schemas/. Consumers should validate the contract version, inspect qa-report.json, and verify the manifest entry before opening a generated artifact.

Determinism

Inputs, configuration, and relevant upstream artifacts are hashed. A review acknowledgement is bound to its finding and input hash so a later input change cannot silently inherit an earlier decision.

No workbook on blocked runs

This is an invariant, not a UI convention. If a run is blocked, downstream automation must not search for or synthesize an RFQ workbook.