Article series

Some pieces are chapters, not standalone articles — a planned run with an order, a shared frame, and a payoff that only lands across the whole set. This is the list of them and where each one stands.

Each series gets its own tracker doc in this folder: a table of its posts up top, then whatever frame, exercises, or code repo the series is built on. Membership is also recorded on the articles themselves, via the series front-matter field (series.name matches the tracker's slug) — see the Series section of ARTICLES.md for the field shape and the fmc queries that read it.

The list

series	slug	tracker	posts	status
The Borrow Checker	borrow-checker	borrow-checker.md	0 / 9 live · 1 drafted	writing — post 1 drafted, exercises next
Solana Economics	solana-economics	folder README	see README	in progress — predates this convention, tracker not yet backfilled
Why Go for microservices	go-microservices	—	0 / ?	idea — not yet scaffolded

How a series moves through here

The portfolio-side lifecycle, which is all this list tracks:

1. Idea — a title and a rough arc. Lives as a row here, no tracker yet.
2. Scaffolded — a tracker doc exists with the full post list and the frame.
3. Running — doing the exercises, capturing real output/errors/benchmarks. The insight from actually doing the work is the point; posts get written from it, not from memory.
4. Written — the markdown exists, clean, draft: true.
5. Live — draft: false, series field set on each member article.

Social-content distribution is a separate pipeline (social-content/) and a later phase — it isn't tracked here. This list is about the articles themselves.

Backlog — series worth pulling off the pile

Not committed, just parked so they aren't re-derived from scratch later:

• Solana Economics already exists as a folder with a plan-style README that links every intended post. It's a series in everything but the metadata — backfill a tracker here and set series.name: solana-economics on its members when convenient.
• Why Go for microservices — the case for Go as the default microservice language. Idea only; scaffold when it's next up.