Devlog

Public, dated entries from the aidokit maintainer(s). Cadence target: weekly. Tone: honest about what shipped, what didn't, and what's next.

Why a devlog #

A devlog is the OSS substitute for a sales engine. aidokit ships zero telemetry by design, so the only way for prospective users to know the project is alive — and to decide whether the maintainer's priorities match theirs — is to read what's actually happening week by week.

It's also a cheap accountability surface. Posts force the maintainer to state what's blocked, what slipped, and what the next 7 days look like. Drift becomes visible.

Entries #

• 2026-05-26 — All 25 pain points closed by v1.x
• 2026-05-25 (week 2) — Workstreams A–H all closed
• 2026-05-25 — Tier rename + first distribution surface

Subscribe (no telemetry) #

There is no RSS yet. Watch the GitHub repository, or check this page on whatever cadence you prefer. If you want a push notification on new entries, that's a feature you can add by PR — the maintainer won't build it speculatively.

Submit #

The devlog is single-maintainer (or maintainer-team) by convention. If you want to publish a guest post — release notes, an adoption story, a critique — open an issue first. We'd rather have a few honest guest posts than a manufactured chorus.