chronicle

Chronicle

Chronicle is a daily AI signal filter for builders. It clusters duplicate AI/ML links, classifies each item, scores novelty against a 30-day rolling history, and ranks by a composite signal score.

Static site, no backend. The Chronicle workflow runs the pipeline once a day, commits two JSON files, uploads public/ as the GitHub Pages artifact, and deploys GitHub Pages.

public/feed.json and data/history.json are intentionally committed by the scheduled workflow. The feed gives GitHub Pages a static file to serve, and the history file gives novelty scoring durable state without adding a database or separate storage service.

Pipeline

sources → fetch → canonicalize → window-filter → cluster
                                                     ↓
                              novelty ← history ← classify (Haiku, one call)
                                                     ↓
                                                   score
                                                     ↓
                                                feed.json

• Canonicalize strips utm_*, fbclid, /amp, fragments, default ports, www., normalizes arXiv pdf ↔ abs.
• Cluster is two-stage: exact canonical URL match, then trigram Jaccard on titles (≥ 0.55). No embeddings in v1.
• Classify runs all clusters in a single Haiku call with forced tool-use output. Returns kind, quality, one_liner.
• Novelty is 1 − max trigram-Jaccard against 30 days of history.
• Score is a weighted sum of trust, novelty, quality, cluster-size, recency.

Local run

npm install
ANTHROPIC_API_KEY=sk-... npm run run:pipeline
npm run verify:feed
npx --yes serve public

Run without an API key to see the fallback path (uses kind_hint, marks everything mixed).

Deploy

1. Settings → Pages → Source: GitHub Actions.
2. Settings → Secrets and variables → Actions → add ANTHROPIC_API_KEY.
3. Push the pages branch.
4. Trigger Refresh Chronicle manually for the first run.

Scheduled workflows run from the repository default branch. Set the default branch to pages if you want the daily cron to run from this branch.

Tuning

All knobs live in source. Eyeball output for a week, then adjust:

• Trust weights: src/sources/registry.yaml
• Cluster threshold: TITLE_THRESHOLD in src/pipeline/cluster.ts
• Score weights: W in src/pipeline/score.ts
• Window: WINDOW_HOURS env (default 36)
• Output cap: MAX_OUTPUT env (default 60)

Cost

Chunked Haiku calls per run, ~150 clusters/day, JSON tool output. Roughly $0.20–0.50/month at current Haiku pricing. Free tier of GitHub Actions covers the compute.

v2 backlog (deferred on purpose)

• Claims as units. Cluster across stories that report the same fact, not just the same URL/title. Needs entity extraction + claim normalization.
• Embedding-based clustering for paraphrased coverage that trigrams miss.
• Per-source quality learning. Track how often a source produces signal vs hype over time, fold into trust.
• Personal weighting. Let the user upvote/downvote; persist to localStorage.
• RSS output of the curated feed.
• Email digest via a separate Action.
• Twitter/X ingestion (probably via Nitter mirrors, fragile).

This site is open source. Improve this page.