GitHub Repository

🧠 Local-first CLI that gives your repo durable, AI-ready memory — features, ADRs, modules, architecture, standards & tests — and a 🩺 deterministic doctor that validates health, evidence & drift. Git tracks what changed; Persist OS tracks why.

1 starsTypeScript

Persist OS – Durable decisions for AI code

Name: Persist OS – Durable decisions for AI code
Availability: InStock
Author: karthickrmchn

by karthickrmchn·Jun 23, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●●SolidBig BrainShip It

Doctor gate returns exit codes for CI when decisions contradict or tests are missing.

Strengths

•Writes decisions as plain files in repo, not vectors—survives session compaction and context loss.
•ADR supersede command maintains auditable trail when decisions change, flags stale references.
•Zero network calls, no telemetry—runs entirely local with deterministic validation.

Weaknesses

•ADR tools already exist (adr-tools, log4brains)—doctor gate is the only real differentiator.
•Only 1 GitHub star suggests very early adoption, unproven in real team workflows.

Post Description

In the past few months, I’ve been building and shipping things extremely fast. Some of the MVPs that I built for my friends were completely vibe-coded and shipped within a day to show a demo.

While it was a great experience working with AI tools, I wanted to make sure some basics were followed, decisions of what and why written down, obvious things not skipped and that it could scale.

That’s why I built persist-os. It’s a CLI that runs locally. No network required. It records the architecture decisions and standards in plain files in the repo and 'persist doctor' checks them - it flags if anything contradicts or is missing, or if the task is done with no tests. Because the rules live in your repo files, it doesn't matter if you start a new session or the session is compacted - the standards and rules survive.

MIT licensed. Here’s how you can try it: npx persist-os@latest init