A month, in one letter.

// knowledge_base/newsletter/2026-09.brief.json (trimmed)
{
  "stats": ["21 km raced", "1 book", "10 posts written"],
  "sections": {
    "On the road": ["Satara Hill Half Marathon 2026"],
    "On the shelf": ["त्सुबाकी स्टेशनर्स — इतो ओगावा"],
    "Written": [
      "Breaking the barriers within: Hyderabad…",
      "The Second Brain: Decoding the complex…",
      … 8 more
    ]
  },
  "previousNotes": [ // the last two letters, for voice ],
  "lastPoll": null
}

Every letter was checked against its data before publishing. Across the twelve, that cut "the hilliest half marathon" and a date that was a guess — neither was in a brief.

/now already had a row per month whose sections blob was a frozen copy of that month. A separate issues table would have been a second copy of the same month. Migration 0032 added only what makes a month publishable:

• slug text unique — 2026-09, the URL
• headline — the card's title, ≤ 6 words
• note — the letter, in markdown
• poll jsonb — {q, options[]}
• published_at — null means draft
• card_url — the rendered share card

-- who may read a month
using (published_at is not null
       or is_current or public.is_owner())

Refs tie every item back to the archive

// one item in sections.running
{
  "event": "Tata Ultra Marathon",
  "distance": "50",
  "date": "2026-02-22",
  "ref": { "type": "sport", "id": 19 }
}

A snapshot, on purpose: editing a race next year does not rewrite last September's letter, and a deleted row leaves no hole in it.

No email, no account. A new vote replaces the old one; a repeated reaction is a no-op. The browser remembers what you did so the buttons show it — courtesy, not enforcement. Postgres cannot see a client's IP through PostgREST, which is why writes go through the edge.

// the issue page sends
focus: { type: "now", id, refs }

// functions/api/ask.js — read by key, beside the search
const { picked } = selectChunks(…);
const chunks = withFocus(focused, picked, match_count);

Each issue is indexed as a letter chunk plus one chunk per section, at its own /newsletter/<slug> URL. Any page can pin itself this way.

Known limits