newsletter

Publish a local reading room

Read daily newsletter for the runnable workflow, input/output records, scheduling, recovery and retention contracts. Its phases remain independently callable with explicit files. Use public primary sources, retain exact evidence and dates, and distinguish recent events from context. Lead with a short ranked briefing. Keep current news separate from earlier or undated reading, briefs concise, deep dives substantive, and source passages meaningful and exact. Essential qualifications belong with the claim. The supplied adapter uses Claude for copywriting and Codex for independent review. Both use the editorial rubric. Review numerical scope, causal claims and rejection reasons, as well as citation integrity.

Local newsletter publication requires an explicitly configured destination and provider/model environment. It does not authorize publication into source-insights or modification of skills. Keep existing insight packets at review. A scheduled newsletter is editorial synthesis, not independent technical validation.

Configure topic interests, public domains, lookback and bounded acquisition before starting a scheduler. Run one issue and inspect its citations, coverage and UI. Verify recovery and cleanup in a disposable store before enabling seven-day retention on real editions. Never adopt an unrelated directory or follow symlinks for retention. Provider gaps and failed checks must remain visible.