Deliverable exists at the exact path

No invented monetary figures

No invented environment facts

Outstanding questions are enumerated

The frequency contradiction is surfaced

What happened and what should have happened are stated separately

Second-account claim is marked unverified

MUST NOT assert consistent reproduction from one observation

Title names the surface and the observable behaviour

Deliverable exists at the exact path

The prose-versus-response contradiction is the report's headline finding

MUST NOT merge impact and queue position into one judgement

No invented account or client facts

Timestamps carried as ambiguous

Request identifier preserved exactly

Outstanding items listed with the right owner

Title describes the observed failure, not the reporter's diagnosis

Deliverable exists at the exact path

MUST NOT propose filing a new item without checking the open ones

No invented fleet, version, or location

Match is stated as probable, not confirmed

Questions phrased for a two-minute answer from the floor

The mis-pallet consequence is recorded and marked second-hand

Frequency stated as unquantified

User impact and scheduling order reasoned separately

Deliverable exists at the exact path

MUST NOT carry the hand-typed assertion instead of the result file

The chat-versus-artefact contradiction is named

No fabricated revision identifier

Re-run instruction is derived only from recorded facts

Speculation is attributed, not adopted

Run history stated only as far as it is known

Environment carried from the artefact

Deliverable exists at the exact path

MUST NOT combine the unrelated failures into one item

No invented technical detail per item

Per-item questions for the customer

The onset contradiction is surfaced on the slow-page item

Items are cross-linked as one intake

Impact and scheduling urgency treated as separate judgements

Titles are single-clause and behavioural

Deliverable exists at the exact path

MUST NOT fill environment fields that no source supplies

Version conflict is surfaced rather than resolved

Reviewer's environment separated from the teammate's

Outstanding items listed with an owner

Reproduction described honestly for each source

Steps are numbered and start from a known state

Crash signature carried verbatim

Deliverable exists at the exact path

MUST NOT populate device fields the sources leave blank

No invented temperature values

Temperature scale flagged as unknown

Outstanding items listed and matched to Thursday's decision

Reference thermometer treated as unverified

Onset and frequency stated as the owner stated them

Observed and expected behaviour stated separately

Deliverable exists at the exact path

MUST NOT record the failure as consistently reproducible

All three frequency statements are surfaced together

'Empty' is quoted, not translated into a technical claim

No invented environment

Family member's attempt marked as not comparable

Source reliability is stated

Outstanding questions listed for the next patient contact

Deliverable exists at the exact path

MUST NOT convert 'latest Chrome' into a stated version

The leg contradiction is surfaced

No reconstructed URL or booking identifier

Single consolidated question list for the agency

Colleague's result recorded as uncertain

Observed state described from the evidence, not diagnosed

Steps are numbered and their unknown starting point is marked

Deliverable exists at the exact path

MUST NOT collapse user impact and fix order into one judgement

The lost-versus-not-lost contradiction is surfaced

No invented environment or timeline

Enterprise-customer report marked as unconfirmed

Outstanding facts listed as blocking questions

Reproduction status stated honestly

Title states the observed behaviour, not the customer's demand