Sopify is a protocol layer for AI-assisted development. It stops when facts are missing, waits when a decision needs your sign-off, and resumes from the last checkpoint — even across different AI hosts.
No new editor, no new CLI. Install into the host you already use — Codex, Claude, or Copilot.
Design principles:
- Stop when unsure — score every requirement; ask before assuming
- Resume from anywhere — checkpoint-based; switch hosts, machines, or teammates without re-explaining
- Trace every decision — plans, choices, and reviews persist in
.sopify-skills/
curl -fsSL https://github.com/evidentloop/sopify/releases/latest/download/install.sh | bash -s -- --target codex:en-USAfter install, use ~go to start a managed workflow. See Installation for other hosts, audit-first install, and Windows.
Already in a Sopify-managed repo? Open any AI host and continue — it picks up from where you left off.
When requirements are unclear, it stops to plan first.
You say "add a caching layer." Sopify doesn't start coding — it plans first: analyze, design, split into tasks, then save to .sopify-skills/plan/. Only after you confirm the plan does it write code. Every line changed traces back to a decision.
Your teammate picks up where you left off.
You start a feature in Codex, finish the design, and implement two of four tasks. Next week your teammate opens the same repo in Claude, types ~go. Sopify reads the checkpoint and continues from task 3 — no handoff doc, no re-explaining context.
Every decision leaves a trace.
A month later, someone asks why the cache key includes the user ID. The answer is in .sopify-skills/plan/ — the requirement that prompted the decision, the design that resolved it, the review that approved it.
The LLM is only a proposal source. The Validator is the sole authorizer — every action is proposed, validated, and receipted before it touches your code. Knowledge persists in .sopify-skills/, accessible across sessions, hosts, and teammates.
Audit-first install:
curl -fsSL -o sopify-install.sh https://github.com/evidentloop/sopify/releases/latest/download/install.sh
less sopify-install.sh # review before running
bash sopify-install.sh --target codex:en-USWindows PowerShell:
iwr https://github.com/evidentloop/sopify/releases/latest/download/install.ps1 -OutFile sopify-install.ps1
Get-Content sopify-install.ps1 | more
.\sopify-install.ps1 --target codex:en-USInstall targets:
| Host | Target | Status |
|---|---|---|
| Codex | codex:en-US / codex:zh-CN |
Deep verified — suitable for daily use |
| Claude | claude:en-US / claude:zh-CN |
Deep verified — suitable for daily use |
| Copilot | copilot:en-US / copilot:zh-CN |
Baseline — feedback welcome |
Pass --workspace <path> to target another repo, --language <lang> to control output language.
For the full setup guide, see Getting Started. For a step-by-step demo, see External Repo Quickstart.
| Command | Description |
|---|---|
~go |
Automatically route and run the full workflow (auto-resumes if active plan exists) |
~go plan |
Plan only |
~go finalize |
Close out the active plan |
Most users only need ~go and ~go plan; maintainer validation commands live in CONTRIBUTING.md.
cp examples/sopify.config.yaml ./sopify.config.yamlbrand: auto
language: en-US
workflow:
mode: adaptive # strict | adaptive | minimal
require_score: 7
plan:
directory: .sopify-skillsplan.directory only affects newly created knowledge and plan directories.
sopify/
├── scripts/ # install, diagnostics, and maintainer scripts
├── examples/ # configuration examples
├── docs/ # workflow guides and developer references
├── runtime/ # built-in runtime / skill packages
├── skills/ # prompt-layer source of truth
├── .sopify-skills/ # project knowledge base
│ ├── blueprint/ # design baseline, reduction targets
│ ├── plan/ # active plans
│ └── history/ # archived plans
└── installer/ # host adapters and install orchestration
See How Sopify Works for the full workflow, checkpoints, and knowledge layout.
- See CHANGELOG.md for the detailed history
- Code and config: Apache 2.0, see LICENSE
- Documentation: CC BY 4.0, see LICENSE-docs
For user-visible behavior changes, update both README.md and README.zh-CN.md when needed, then follow CONTRIBUTING.md for validation.
