Known now
Decision column 1: known now must remain explicit in the saved record.
FAQ · Row Revision Log
Lovegobuy Spreadsheet Row Revision Log FAQ
Keep each answer tied to the evidence needed for this row change log, not to a broad product or service claim.
Scope questions for this row change log
- What counts as a material row change?
- A change that affects identity, selection, evidence, or the next action belongs in the log.
- Should every visit create a revision?
- No. Record a no-change checkpoint only when it establishes a useful review date.
Evidence questions for this row change log
- Can a redirect be treated as the same item?
- Only after the final page, item context, and visible selection have been compared.
- What if the old page is gone?
- Keep the last saved value as historical context and mark the current comparison incomplete.
Decision questions for this row change log
- When should a row be replaced?
- Replace it only when the current source no longer supports the intended item or option.
- Why keep unchanged fields?
- They show that the review compared the whole identity rather than one isolated label.
Decision record
Separate known fields, missing evidence, and the next check
The record is useful when it shows both the current decision and the evidence boundary that could reopen it.
Not observable
Decision column 2: not observable must remain explicit in the saved record.
Conflict retained
Decision column 3: conflict retained must remain explicit in the saved record.
Next evidence
Decision column 4: next evidence must remain explicit in the saved record.
Carry unresolved details into the next live check
A static answer should never disguise a changing platform detail.
Check the Lovegobuy reference page when a live shipping or policy detail falls outside this static record.
Use the method