The Loopdown

loop + lowdown, field notes from an engineer who writes.

Short, sharp technical lessons pulled from real projects (Doori, kmp-toolkit, PaymentsLab-KMP, Gaddi, Dice), each written once and adapted to LinkedIn, dev.to, Hashnode, and Medium, plus an archive of everything I've written before.

Case study: The Loopdown (also at cv-siddharth.vercel.app)

This repo does three jobs at once:

1. 📚 Archive: my complete writing corpus, consolidated and versioned. Nothing lost.
2. 📡 Engine: a pipeline that turns a project war-story into a multi-channel post + branded graphic.
3. 🧱 Wall: public proof of consistency. The registry below is the track record.

The Loopdown isn't a content calendar, it's a world. An engineer stuck in a time loop (52 iterations of the same Wednesday), filing field notes on the same bugs and lying systems each pass. Because seniority is the loop: you don't know more code, you've just run the same failure enough times to name it on sight.

Posts share a recurring cast, The Concussed Witness (GPS that lies with total confidence), Doze the Jailer, The Messenger (CancellationException, forever mistaken for an assassin), grouped into series you can binge. Continuity is tracked automatically (see Cast Appearances below). The world is in lore/; the voice is in voice/.

Separate universe, same author. Four seasons, forty-eight entries, grown out of a single 2021 story in the archive that turned out to have a whole series folded inside it.

A field correspondent visits worlds that cannot yet leave them and writes down the story each one tells about its own weather. Every world independently reports fourteen gods and fourteen monsters. Nobody anywhere can name the fourteenth.

• Read it on the site → (also at cv-siddharth.vercel.app): all four seasons, every entry, the plates, the tellers and the starmap
• Canon: S1 bible · S2 bible · S3 bible · S4 bible
• Seasons One and Two were audited by multi-lens councils plus cross-family ensembles: S1 · S2 ownership audit. Season Three's ownership test is recorded inline in s3-bible.md.
• Sibling series, same universe, no shared cast: The Dark Directory (entry count in the registry table below)

node scripts/morkinstar-plates.mjs   # 49 field plates, all four seasons + cover
node scripts/morkinstar-site.mjs     # → site.html

This is not The Loopdown's cosmology and does not cross over with the cast above. They rhyme. The rhyme is the reward.

idea  →  new-lesson.mjs  →  lesson.md (source of truth, written ONCE)
                                 │
                 ┌───────────────┼───────────────┐
                 ▼               ▼               ▼
           linkedin.md      article.md      assets/card.yaml
        (≤1300, punchy)   (long-form)      → render.mjs → card.png
                 │               │               │
                 └──────── you review ───────────┘
                                 │
                    export → Buffer (LinkedIn) · dev.to/Hashnode API · Medium (manual)
                                 │
                          meta.yaml logs urls + metrics
                                 │
                    build-registry.mjs → this README updates

Every draft is checked against voice/voice-profile.md the style contract distilled from the archive so new posts sound like me, not generic LinkedIn.

cd scripts && npm install          # once (pulls @resvg/resvg-js for SVG→PNG)

node new-lesson.mjs "dead reckoning" --pillar location --project Doori --date 2026-07-19
node render.mjs lessons/2026-07-19-dead-reckoning      # card.yaml → card.png
node build-registry.mjs                                 # regenerate registry + this README
node check-setup.mjs                                    # pipeline readiness dashboard
node export.mjs lessons/<dir>                           # dry-run: plan + paste files (safe)
node export.mjs lessons/<dir> --draft                   # dev.to drafts, reviewable on-platform

Accounts, tokens, and the publish flow: SETUP.md.

Hook you with a scene, teach you something real, land a payload you didn't see coming, while clearly having fun. See voice/voice-profile.md.

Each lesson goes out as a coordinated cross-platform drop (SETUP.md):

• dev.to + Hashnode + Medium → native APIs (draft-first, per-post approval). Medium uses the legacy token if your account has one, else a one-click import from the canonical URL.
• LinkedIn → paste-ready file with the full-write-up link auto-embedded (optional Buffer queue). No tool touches the account directly.
• One canonical home so cross-posts don't compete in search, the rest declare canonical → it.
• Consistent branded footer on every article: series, featured cast, "previously in this series," follow links, all generated from profile.yaml. Edit once, threads everywhere.
• Series hubs (series/), a bingeable index page per arc, linked from every post in it.

• Repo + archive + voice profile + visual engine + first lesson
• Lore layer, universe bible, cast, series, continuity index
• export.mjs, dev.to/Hashnode/Buffer + paste files; check-setup.mjs dashboard
• Tokens filled, repo pushed: six lessons live across dev.to, LinkedIn, Medium and Hashnode
• .github/workflows/pipeline.yml: lints voice, smoke-tests renders, fails the build on registry drift, on every push to main
• Cadence: 2 to 3 posts/week from the backlog

Two licenses, because this repo holds two different kinds of work.

The engine is MIT. scripts/, templates/, voice/, launchd/ and the dashboard are yours to take, fork and adapt. That is what they are for.

The writing is not. lessons/, fiction/, lore/, series/, archive/, notes/ and docs/ are all rights reserved. Read them, quote them with attribution and a link, but republishing or adapting them needs a yes from me first. The pipeline is a tool. The field notes are the work.

See LICENSE for the exact terms.