HR-2 A person's bar, not the agent's margin

Where a bar that no measurement fixes decides acceptance, the agent SHOULD apply a bar a person set, stored where the check reads it, and not a margin of its own choosing.

Field	Value
Keyword	SHOULD
Level	2
Checked	by judgement
Findings	F105
Harness facts	none
Threat	external: one project, three days of history, and a single person setting every bar
Status	active

Rationale: in polyweave a bar the agent chose, recorded as "a margin nobody asked for", blocked a port for a day. In another task a search of 109 samples found no rig that passed all four checks; the task was deferred for a person's look, and shipped once a person looked at the result beside the shipped sprite at display size and accepted it, at which the bar moved to 0.41 (F105). The project then filed a block to make a bar a person sets once a value the checks read. This is one project's record, a dated incident with no contrary observation, which admits SHOULD. Whether a stored bar is then reused without asking again is not yet observed; see the open questions.

That an acceptance condition a gate can decide is decided by a gate before the task closes is rule VG-8 in VG.md; it is not repeated here.