Feature Brief: use notes

The buyer starts with intended_job and intended_checker. State the actual inspection or information action before naming a technology. The supplier proposes the feature and evidence scope; the buyer identifies who supplies and releases the evidence. Visual layout, physical opening response and operated item-status service require different approvals. A completed row is not a pass. Keep evidence_reference and release_decision pending until the relevant work has happened. The worked rows are hypothetical requirements, including a deliberate deferral of unneeded serialization.

Field responsibilities

Name the intended check and evidence owner, then scope the proposed feature against it.

Examples are hypothetical planning inputs. Blank observations and approvals are intentionally unknown, not zero or passed. The buyer records an evidence reference and the authorized decision only after the work occurs.