Community documentation desk: a notebook of numbered synthetic discussion exercises. Each case has a question followed by up to six distinct responses.
The source question bank is finite. Later passes revisit a question with a named review focus, using short excerpts to examine scope, method, limitations or a summary. A new case number marks a separate exercise, not a new real event or a claim of historical community activity.
Case 1 — Source-review index: unresolved, documented and corrected
How can a review index distinguish an open question from a supported conclusion?
Exercise PHARMACY-30288/1: address this question within its stated limits.
Case 1 — Source-review index: unresolved, documented and corrected
Use clear evidence-status labels and dates, and link to the underlying records. Avoid numerical trust scores or invented purchase histories; this example demonstrates organisation only.
Case 1 — Source-review index: unresolved, documented and corrected
Clarification for “Source-review index: unresolved, documented and corrected”: the point beginning “Use clear evidence-status labels and dates, and link…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Case 1 — Source-review index: unresolved, documented and corrected
Limit of the answer in “Source-review index: unresolved, documented and corrected”: “Use clear evidence-status labels and dates, and link…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
Case 1 — Source-review index: unresolved, documented and corrected
Method note for “Source-review index: unresolved, documented and corrected”: use “Use clear evidence-status labels and dates, and link…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
Case 1 — Source-review index: unresolved, documented and corrected
Correction note for “Source-review index: unresolved, documented and corrected”: retain the wording beginning “Use clear evidence-status labels and dates, and link…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
Case 1 — Source-review index: unresolved, documented and corrected
Summary draft for “Source-review index: unresolved, documented and corrected”: the answer addresses “Use clear evidence-status labels and dates, and link…”; the related point is “Avoid numerical trust scores or invented purchase histories;…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
A order log contains a dispatch email on Friday and the first physical acceptance scan on Tuesday. The proposed review currently calls all four days carrier transit. Which events should the timeline distinguish?
Exercise PHARMACY-30288/2: address this question within its stated limits.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
Keep three separate fields: dispatch statement, label creation if recorded, and the first physical acceptance event shown by the carrier. State the timezone of each record; the dispatch email alone does not establish carrier possession.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
Are the event timestamps in the same timezone? Keep the original timestamp and its timezone beside any converted value. Removing the timezone can change which calendar day an event appears to fall on.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
The acceptance scan is evidence of the recorded acceptance event, but missing earlier scans do not prove exactly when handover occurred. Describe that interval as uncertain rather than asserting a four-day seller delay.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
A clear row would read: Friday—dispatch stated in email; Tuesday—carrier acceptance recorded; handover time—not independently established. That gives readers a useful chronology without a claim the records cannot support.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
Update the summary if an earlier custody record becomes available. Preserve the old interpretation in a dated correction rather than rewriting the entire thread without notice.
Case 2 — Dispatch email versus carrier acceptance: how should the timeline read?
For a public copy, remove the tracking token, account identifiers and recipient details. Keep the original records privately so a support enquiry can refer to them.