PG-3 A false premise is recorded, not rewritten

When a task's premise or design is found false, the finding SHOULD be recorded, by retiring the task with its reason or in its ledger entry, rather than rewritten in place.

Field	Value
Keyword	SHOULD
Level	1
Checked	by judgement
Findings	F102, F103, F106
Harness facts	none
Threat	internal: the silent losses are recorded by one tool of repositories it does not name
Status	active

Rationale: false premises are common enough to recur in four projects, and where they were recorded the record is a retirement that names the error, such as freewilly's tasks filed "against the wrong writer" or with a heading naming an unrelated task (F102). Designs found wrong on implementation were, in one tool, deleted at shipping "with no trace that its reasoning had" been wrong, and the remedy was a ledger sentence stating what the design was wrong about (F106, F103). The silent case is observed only in that one tool's sources, so the rule carries SHOULD. Where a task line survives because the symptom held, amending its reason in the open is the same record in a different place.