AI work needs a record.

Open Scaffold records AI-assisted work in your repo: plans, run packets, evidence, handoffs, review gates, and close records that survive the session.

Kill the session mid-task. A fresh reader, compatible agent, or operator can resume bounded work straight from the repo after total chat-context loss — no archaeology through vanished chat. See the resume demo fixture and the resume walkthrough.

First command

Guided start in a new or existing repository.

npx open-scaffold@latest first-run

Three questions produce the minimum work record and the exact next commands.

ProblemAI work disappears into chat, retries loop blind, and nobody can review what happened.

AudienceDevelopers and teams using agents for work that must survive the session.

Methodhandoff, review, and gate over a repo-native work record.

BoundaryExternal agents do the work. Humans own merge and release.

Solo developer

Resume work after a week away. The mission, active plan, verification commands, and latest evidence are in the repository instead of an old chat.

Team PR review

Attach intent, constraints, acceptance criteria, tests, and review state to the branch so reviewers see why the change exists.

Client or audit-sensitive delivery

Keep a lightweight trail of what was requested, what was produced, what passed, and what humans approved.

What you can rely on today

The work loop and its record are stable: MISSION.md, plan folders with acceptance criteria, amendments, no-spawn run packets, evidence notes, osc handoff, osc review, osc gate, and osc verify. Runtime launch stays outside Open Scaffold core.

Current package truth: the public line is still pre-1.0 and the evidence is pilot-grade. Treat Open Scaffold as a repo record and review layer, not as a hosted orchestrator, compliance program, or production-readiness certificate.

One page holds the full maturity contract — stable, experimental, future, and the honest limits: the stability page.

What it creates

MISSION.md                         why this repo exists
.osc/plans/                        scoped work with acceptance criteria
.osc/runs/<run_id>/run.json         handoff package for a worker or reviewer
.osc/releases/                     evidence notes and release records
.osc/evolution/<loop_id>/           repeated attempts and frontier history