Runs
Runs stay until you delete them
The life cycle
Phase → gate
{# Chips live in the summary so they stay up when this card is closed. #}
{%- for p in phases %}
-
{{ p.n }}
{% if p.n == 1 %}Identify{% else %}{{ p.name }}{% endif %}
{%- endfor %}
The life cycle
Phase → gate
Clarify freezes the condition and the evidence — that is the only validation. Orchestrate (always Jarvis) drives it. After tests, verify A and verify B — build or an external agent, never Jarvis — independently sign the same evidence. Deploy stays a click.
The seven phases
-
{%- for p in phases %}
-
{{ p.n }}
{{ p.name }} {%- if p.gates %}{{ p.gates | join(' · ') }} {%- else %}not implemented — out of scope{% endif %} {{ p.note }}
{%- endfor %}
Validate once, then verify
Validation happens once: clarify/contract freeze the right condition and the right evidence. Everything after that is verification — LSP, driving those evidence lines, and two independent models re-reading the same evidence. These are the pairs that exist here:
-
{%- for v in vee_pairs %}
- {{ v.defines }} {{ v.answered_by }} {{ v.how }} {%- endfor %}
Nothing in flight
-
-
This interview is the validation. Jarvis asks through the same chat question card. Dev only listens — it does not invent a second form.
Open chat -
Tests: isolated Docker · no network or host mounts
-
sdlc/plan -
sdlc/design -
sdlc/code -
sdlc/tests -
sdlc/deploy -
ship Independent verify A + verify B + LSP green → merge. Deploy stays a click.Merge automatic when green
Independent verify A + verify B + LSP green merges this PR. Archive lives with the run controls below — it does not wait for a PR.
Deploy restarts production