Home

SAIPEN

Continuation protocol for AI coding agents. Project memory in plain markdown. Cold agent with zero history runs /saipen continue, reads STATE->BOARD->LOG tail, executes next_action, resumes in under a minute. Any vendor, any day.

v7.98.0 | MIT | Spec | RFC

---

One command. Zero dependencies. Zero amnesia.

User  ->  /saipen continue
Agent ->  reads STATE.md (phase, task, next_action, mode, human_note)
Agent ->  reads BOARD.md (DOING / TODO / DONE / BLOCKED tickets)
Agent ->  reads active LOG.md tail (recent events)
Agent ->  executes next_action immediately
Agent ->  loads phase doc only when rules needed
Agent ->  Works.

12 commands, full surface

Command	Effect
saipen set / saipen init	Bootstrap .saipen/
saipen continue / bare saipen	Resume from STATE
saipen goal <text>	Pivot to objective, run to completion
saipen plan	Enter PLAN phase
saipen clean	Deep repo scrub
saipen translate	Isolated translation build
saipen markhunt	Dry exhaustive audit (record only)
saipen prepare	Package work for handoff
saipen ship	Version bump, tag, push
saipen validate	Run conformance checker
saipen status	Read-only board report
saipen stop	Checkpoint + halt

Two layers

Layer	Required	Purpose
Core	✅	Continue work safely
Maintenance	On top of Core	Evolve software with no tasking

Core state machine: INIT -> PLAN -> SCOUT -> BUILD -> VERIFY -> REVIEW -> SHIP -> DONE | BLOCKED

Autonomous evolution: Empty board at DONE -> auto HUNT -> ADD -> HUNT... until mature or capped (3 waves / 20 tickets).

Goal mode: saipen goal <objective> - autonomous run with safety valve. Auto-pivots, auto-ships, auto-hunts. Stops at maturity or caps.

Key features v7.98.0

• WAIT categories (v7.93.0): Closed 7-word vocabulary — manual-verify, destructive-op, first-publish, user brake, blocked, safety valve, init. Makes stopping mechanically distinguishable.
• Cross-document drift detector (v7.93.0): tools/validate.py parses 6 sets from RFC, FAILs on schema/validator/BOOT/CONFORMANCE disagreement.
• Portable floor (v7.94.0-97.0): validate.sh + validate.ps1 probe all 9 RFC §1.2 fields, frozen against new checks.
• SubSaipen protocol (v7.91.0): OUTBOX validated (status/summary/critical), patch-with-evidence format, read-only workers.
• Determinism invariants (v7.86.0-92.0): fixed action priority, RECOVER/FINISH/START hierarchy, one-ticket-at-a-time.
• Real CI gate is pre-commit hook (v7.97.0): CI triggers on pull_request (zero PRs ever). Actual enforcer is .git/hooks/pre-commit running tools/validate.py. Portable validate.sh/validate.ps1 cover Python-less hosts.
• Drift hunt validation (v7.98.0): validate.py expanded to subSaipen next_action (prefix/category enforcement), self-transition enum checks, and adapter saipen/ path existence — no surface left unchecked.
• SubSaipen production ready (v7.98.0): extensions/subs/README.md updated from "Not yet field-tested" to "Running in production since v7.84.0, 4 live instances".

Quick Start

git clone https://github.com/vacterro/saipen
cd saipen
powershell -ExecutionPolicy Bypass -File .ootstrap\inject.ps1     # Windows
bash bootstrap/inject.sh                                            # macOS / Linux

Paste to any agent: Read <clone>/saipen/BOOT.md first (cold-start kernel), then <clone>/saipen/RFC.md + <clone>/saipen/STYLE.md

ДED Voice

"Без SAIPEN: открываешь проект через неделю — 'кто тут? что за код? где я остановился?' С SAIPEN: 'привет, продолжай, T-42 в DOING, verify не было, чини.' Один чтение — и работаешь. Никакого 'расскажи что ты делал'. Никакого 'дай контекст'. Просто STATE.md открыл — и всё понял."

---

GitHub | 32 locale guides | Changelog