Skip to content

DOSIAI Development Protocol

Documentation-first protocol for solo developers working with AI. Work produces documents, documents feed the vector DB, the vector DB remembers everything.

How It Works

Supervisor (human)                    Orchestrator (AI)
    │                                      │
    ├── sets objectives ──────────────→    boot: read state, history, protocol
    ├── injects ideas  ───────────────→    capture: log immediately, triage later
    ├── approves/steers ──────────────→    execute: dispatch agents, update OCD
    └── reads status   ←──────────────    close: finalize docs, embed, snapshot

DOSI sits between you and your AI coding partner. It gives the AI operational memory — where you are, what happened before, and how to work.

Without this, every session starts cold. With it, session 47 knows what session 1 decided.

The Stack

ComponentWhat It IsAnalogy
DOSIThe system — protocol + embedding pipelineGit workflow docs
OCDContext unit — directory of everything from one sessionA git commit
STATE.mdLive snapshot — where are we nowWorking tree status
CLAUDE.mdProject config — what are we buildingREADME for the AI
Knowledge NetworkVector memory — recall anythingSearchable brain

Built By

Bepely — Created by Bepely. Battle-tested across 60+ sessions building production software with Claude.

Created by Bepely