---
file_id: TLRI-COMMUNITY-NEWSLETTER-STARTER
version: 0.1
timestamp: 2026-09-19
status: DRAFT_REVIEW_CANDIDATE
checksum_hint: sha256-body:fb53736b48ed338b08c78aa9a8de565d12d1b606e26ec720ec78ef9293d928bd
---

# [Community name] newsletter

**DRAFT — complete the placeholders and human review before sharing.**

Issue: [ID and version]  
Published: [date and time zone]  
Coverage: [date range, places, communities, subjects]  
Publisher: [name and accurate independent or authorized status]  
Next issue: [date you can maintain]  
Corrections: [named person and tested public contact route]

[Two or three sentences welcoming readers and naming what is useful in this issue.]

## Coming up

### [Plain title]

[What is happening and why these readers may care.]

- **Who:** [Who may attend, apply, or ask; do not infer eligibility.]
- **When:** [Date, time, time zone, deadline; distinguish event and application dates.]
- **Where:** [Location and access information relevant to the item.]
- **Next step:** [One useful action; responsible organizer/office; checked contact.]
- **Source:** [Title and public URL; checked date/time/time zone.]
- **Still to confirm:** [Unknown, conflict, or “none identified in this check”; remove any action that assumes an unknown is settled.]

[Repeat the item block only for relevant, checked items.]

## What has changed

[Updates to previously reported items; what changed, effective date, source, action if any.]

## Help and opportunities

[Checked items using the same block. Identify standing resources as standing resources, not new announcements.]

## Regional items

[Clearly identify the different community or area. Include only if useful to these readers.]

## Corrections and previous issues

- Correction owner and route: [name/contact]
- How corrections are handled: [real process and response limits]
- Issue archive: [public location]
- Correction to this issue: [date, prior statement, corrected statement, reason, new version]

[Closing and next issue date. Avoid soliciting private case details.]

---

# Working notes — prepare separately from the public issue

Do not publish private contact details, family information, protected cultural material, or uncertain-circulation records. Keep a lawful, minimal evidence record. Delete this working section from the reader-facing copy.

## Scope and upkeep

- Audience and community boundaries: [ ]
- Publisher and basis for any claimed authority: [ ]
- Editor / correction owner / backup: [ ]
- Sustainable cadence and next issue: [ ]
- Review trigger for changing information: [event or date, owner]
- All important current claims checked together through: [date, time, time zone, or explicitly not complete]
- File last edited: [separate date; editing is not verification]

## Source list and check record

For each planned source, record a check even if no item was found.

| Source ID | Source / URL | Check date, time, zone / checker | Result | Item supported | Uncertainty / next check |
| --- | --- | --- | --- | --- | --- |
| [S01] | [ ] | [ ] | [Item found / no change / conflict / replaced source / inaccessible / not relevant this issue, with reason] | [ ] | [ ] |

For each public item record its source type separately: official source, supplied public flyer, direct report, community post, conflicting sources, awaiting confirmation, or archived/passed. A found item is not automatically verified. A flyer supports what it actually says, not what it omits.

## Human review

- Reviewer and date: [ ]
- Exact issue version and channels checked: [ ]
- Could the reader identify the date, intended participants, uncertainty, next step, and correction route? [evidence and repairs]
- Were consequential dates, contacts, and participation conditions checked with the responsible source? [evidence]
- Phone, keyboard, links, and print checks: [observations; do not mark complete without doing them]
- Public circulation, privacy, cultural context, and permissions: [decisions and exclusions]
- Named human decision for this exact issue: [share / repair / hold, with reasons]
- Final issue, source record, lawful evidence, and prior versions saved at: [ ]

## Correction and handoff

| Date | What changed / why | Affected copies | Owner | Completed check |
| --- | --- | --- | --- | --- |
| [ ] | [ ] | [website, email, print, social, other] | [ ] | [ ] |

Next editor: [where to find the source list, unfinished checks, templates, issue archive, and correction contact]. Recheck recurring items; do not carry them forward solely because they appeared last time.

## About this starter

Draft general guide companion, prepared 19 September 2026. Basis: The Long Return Mandatory Weekly Source-Sweep Control Document v1.0 (6 August 2026), and Community Briefing Template and Protocol v1.1 candidate with its Language and Output Audit (11 September 2026). This is not the complete Pit River Weekly Check-In control packet. The briefing protocol remains a candidate pending its adoption exercises and owner decision. This new starter has not completed reader testing.