Jarvis Control Plane

Deterministic workflow gates for AI-assisted software delivery.

Commands

• jarvis init - scaffold workflow files into the current project.
• jarvis status - show current stage and gate status.
• jarvis check [stage] - run gate checks for current or specified stage.
• jarvis promote <target-stage> - move to next stage if current stage passes.
• jarvis repo [owner repo-name --public|--private --template owner/repo] - create and clone a new repo (prompts interactively if args are omitted).
• npm run cp:codex-pr-check - validate workflow/artifacts/codex-review.json against gate policy.

Local usage

npm install
npm run cp:init
npm run cp:status
npm run cp:check

Stage model

discovery -> contract -> plan -> build -> harden -> release -> operate

Gate requirements are defined in workflow/gates.yaml. Workflow state is tracked in workflow/state.yaml. Transition history is tracked in workflow/history.yaml. Note: workflow/ is runtime state and is intentionally not committed in this template repo. Run jarvis init in each new repo to scaffold it.

How this controls AI-assisted work

1. AI can generate code and docs.
2. Promotion between stages is blocked until deterministic checks pass.
3. Stage transitions are chain-validated from history to block stage jumps.
4. CI runs the same checks to prevent bypass.

Codex PR Gate

harden stage includes a Codex review gate:

1. Required artifact: workflow/artifacts/codex-review.json
2. Required command: npm run cp:codex-pr-check

Policy:

1. status: "fail" blocks gate pass unless override file exists.
2. Unresolved high severity findings block gate pass unless override file exists.
3. Optional override file: workflow/artifacts/codex-override.md

Reuse Across New Repos

1. Mark this repo as a GitHub Template Repository.
2. Create a new repo from template:
   • jarvis repo <owner> <new-repo-name> --private
   • From any directory: jarvis repo <owner> <new-repo-name> --private --template <owner/repo>
   • Optional env default: export JARVIS_TEMPLATE_REPO=<owner/repo>
3. Apply branch and environment protections:
   • scripts/apply-github-protections.sh <owner> <repo> main
4. Follow the full checklist:
   • docs/REPO_BOOTSTRAP_CHECKLIST.md

Scripts

• scripts/create-repo-from-template.sh - create/clone repos from this template.
• scripts/apply-github-protections.sh - enforce branch/environment protection via GitHub API.
• scripts/guard-state-change.js - CI guard to block invalid state.yaml edits.

Next steps

1. Publish this package to npm.
2. Use npx jarvis-control@<version> init in any project.
3. Customize workflow/gates.yaml per project domain.