How CI/CD works on the Command tab

Chefe 2700 · you asked to build CI/CD · 23 Aug 2026 · still pictures before the tab itself

Ideia central

CI = tests that run the same way every time a program changes. If they fail (red), we do not ship.
CD = ship to our lab only after green, and only if that program’s toggle is ON. Public product is a later press by you — not automatic.

You drive it from the Command tab: ASK “run tests” or “ship”, TOGGLE keep-going or pause, SEE green / red / missing.

You ASK or toggle, then change, then CI tests. Green and toggle ON can ship to lab. Red stops. SEE shows status per program.

We copy the gate that already works on ParviClaw core. We do not install a new tool in every repo. We do not put Grafana in the middle.

O que foi entregue

  1. Picture of the flow (above).
  2. Honest list: who already has tests on GitHub, who does not.
  3. How the Command tab drives it (table).
On the tabWhat it does to CI/CD
SEE greenLast tests passed. Safe to talk about shipping to lab.
SEE redStop. Fix. Do not ship.
SEE missingThat program has no automatic tests yet — we copy the ParviClaw core gate.
TOGGLE ONEvery new change runs tests. Agents keep delivering.
TOGGLE OFFPause that program. No silent “keep shipping”.
ASK “run tests”Start the same tests now, even if you did not push.
ASK “ship”Only if green. Goes to our lab. Public product waits for you.

Who already has automatic tests

ProgramAutomatic tests today?
ParviClaw coreYes — tests + lint + security on every push (our machine)
ParviGovYes — unit tests on every push (GitHub)
ParviSight, ParviMax, Defenders, Range, licensing, lab, othersNot yet — this is the copy work

O que mudou no meio do caminho

Nothing installed today. You wrote CI/DC — I treat that as CI/CD (tests, then ship). I did not add Jenkins, GitLab, or Grafana. The Command tab from 2699 is still waiting your Yes / Change; this picture is how CI/CD hangs on that tab.

O que falta

Look at the picture. Then pick:

1 — Yes, this is how it works. First copy the ParviClaw test-gate onto the next program you name (I suggest ParviSight if it is on GitHub; several others are not even a GitHub repo yet).

2 — Yes to the flow, but Command tab first (2699 Yes), then the test-gate copies.

Change — tell me what is wrong (example: auto-ship public product, which I advise against).

I will not write the gates or the tab until you pick 1, 2, or Change.