Turns forwarded newsletter emails into a daily, category-grouped “magazine issue” published as a webpage (Phase 1), later also sent to Kindle (Phase 2).
Newsletter: A recurring email subscription (e.g. a Substack) that the user has chosen to route into this system. The source, not any single email from it. Avoid: Subscription, feed
Article: One newsletter email, once it enters the pipeline. Carries three layers as it’s processed: raw (the original email), cleaned (extracted article text), and summary (AI-generated highlights). Has exactly one Category. Avoid: Email, post (email is fine for the raw inbound message itself, before it becomes an Article)
Issue: The daily compiled digest — one per day, containing every Article received since the previous Issue’s cutoff, grouped by Category. The unit the webpage and (later) Kindle delivery are built around. Avoid: Digest, edition (digest is fine informally, but Issue is canonical for anything schema/code-facing)
Category: A topical grouping assigned per-Article by the AI at compile time, not a fixed property of a Newsletter — the same source can land in different Categories on different days, and category names can drift day to day. Avoid: Section, tag
Intake address: The dedicated email address newsletters are forwarded to. Deliberately isolated from the user’s real inbox — an inbound-parse webhook (Mailgun/Postmark), not a polled Gmail account. Avoid: Forwarding inbox
aiste-io landing-page repo).newsletters@mail.reads.aiste.io). Nested one level under reads.aiste.io rather than the same hostname, since a CNAME (required for the site) can’t coexist with an MX record (required for intake) at the same DNS name.