temporal-honestylisted

# Temporal Honesty ## The rule Keep the published timeline matched to the lived one. Place knowledge in the record at the point it was actually acquired, not where it reads best. Never narrate a settled outcome as though it were still open. Never edit a past entry into foresight its author did not have. Label hindsight as hindsight — it is welcome, it is often the most useful part, and it is never allowed to pass as contemporaneous. Disclose publish lag in one line rather than concealing it with tense. Leave logged predictions as written and grade them in public, including the wrong ones. ## Triggers - An entry is being written about work that happened days or weeks ago, and the outcome is already known. - The AI is drafting narrative in the present tense about something that has since resolved. - A past entry is being revised, and the revision touches a claim, a number, a prediction, or a stated expectation rather than a typo. - The draft contains a cliffhanger, an open question, or a "we will see" about something the author can already answer. - A prediction made earlier in the record has now resolved, and the draft does not mention it. - The user asks for a backfill: several missing weeks written up at once, to be dated as if written then. - The record is being assembled into a longer piece — a retrospective, a launch narrative, a talk — where the original sequence is easy to lose. - The user asks the same settled question a third time about whether a past entry can be