Local-Only Mode

None of the core loop needs a remote to function. No GitHub, no hosting provider, no network service beyond pulling down packages in the first place.

What runs with nothing pushed anywhere

The entirety of the build loop and the QA loop — specs, implementation, checks, audits, findings, test cases, test cycles, archives, and local merges, all of it.

/complete makes a local commit and merges locally once you approve. A remote existing was never a requirement.

What actually does need one

Feature	Needs
Automatic GitHub checks	A repository that’s been pushed
Branch protection acting as a lock	A GitHub ruleset
Deployment	The hosting provider, plus its own separate approval

Even /ci works with no remote in place — it defines the Verify command and writes the workflow file locally regardless. That file just sits there doing nothing until the repository actually gets pushed.

What stays true no matter what

No command pushes, deploys, publishes, or sends anything without your explicit yes in that exact session. /continuous goes further and never does any of that at all, by design, regardless of what’s configured elsewhere.

Local-only isn’t a mode you switch on — it’s just the default posture everything already starts from.

The dashboard never leaves your machine

npx create-syntaxis@latest dashboard

Bound to 127.0.0.1, read-only, no internet required, and it stops the moment you hit Ctrl+C. Local Dashboard has the rest.

Local state isn’t Git’s problem

syntaxis/.state/ holds the install manifest and dashboard activity. It’s Git-ignored and never becomes part of a feature commit.

Going remote whenever you’re ready

There’s no migration to run. Add the remote, push, and optionally run /ci to line GitHub up with the Verify command you already have. Your plans, history, findings, and QA records are just files — they travel with the repository the moment it does.