Define what the newsletter publishes: Insights, Projects, and engineering publication criteria

Priority: High

Problem

It is not currently clear whether the newsletter should send only new Insights, also send project publications/updates, or use another editorial rule. Without a written policy, publication can become inconsistent and the newsletter promise can drift from the website's engineering principles.

Goal

Define an explicit engineering-publication policy for what qualifies for newsletter distribution and what remains website-only.

Scope

• Review the current newsletter promise on the website and Buttondown.
• Decide whether new Insights are sent automatically/manual-by-default.
• Decide whether new Projects, major project updates, engineering notes, or other content belong in the newsletter.
• Derive publication criteria from the site's evidence-first engineering principles: useful engineering substance, verifiable claims, non-repetitive value, appropriate confidentiality, and durable relevance.
• Define what should explicitly not be emailed.
• Document the publishing workflow so future agents can apply the policy consistently.

Acceptance criteria

• The newsletter content scope is explicitly documented.
• Insights and Projects each have a clear send/do-not-send rule.
• Engineering publication criteria are written as an actionable checklist.
• The public newsletter description matches the actual policy.
• The publishing documentation identifies the source of truth future agents should follow.

Review the current newsletter promise on the website and in Buttondown, then compare it with the site's evidence-first engineering principles. Document actionable send and do-not-send rules for Insights, Projects, updates, and engineering notes, along with a publishing workflow and source of truth. Done means the policy and checklist are written and the public newsletter description matches them.