Runner: run a voyage remotely as the kab-automation identity #1

Open
demo-bot wants to merge 4 commits from runner-remote-voyages into main

4 Commits

Author SHA1 Message Date
fb65ef9515 Runner: the system decides review points in the Cymbal Bank project
The owner named the KAB project "Cymbal Bank" (5a2da83b-...; voyage
ENG-CYMBAL-001) as one of Shakedown's own. There, the runner continues a
review point only on a critic pass with no failed step (plan 5b). Every
other project still waits for a person.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 05:14:00 +00:00
099f9a87e8 Runner: run a voyage remotely as the kab-automation identity
- shakedown_lib: runs F01 -> F02 -> F03 for one engagement on KAB with no
  personal token. Signs in as the kab-automation client (client credentials,
  provisioned by Stellwerk from crucible-platform-deploy) and renews the token
  itself.
- Each stage checks its workflow id against the registered sub-agent name,
  builds inputs from the case and upstream stages, starts the run, follows it
  and judges it with cp1-agents evaluate_case.py.
- Gates (plan 5b): in config/runner.yaml gate_projects only, continue on a
  critic pass with no failed step and a note saying the system decided.
  Never on a fail. Elsewhere, wait for a person and record who decided.
  gate_projects is empty for now.
- Ledger per voyage run, with --resume; nothing secret is written.
- Cymbal voyage ENG-CYMBAL-001; workflow registry; Dockerfile and an
  unapplied Job template; 15 tests against a fake KAB.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 05:08:31 +00:00
07060dbb37 Plan §5b: end-to-end use cases that fix what fails (owner, 2026-11-15)
Name a customer: the system generates its use case and runs Discovery,
Assessment and Strategy remotely. It decides gates only in its own projects
and only on a critic pass, fixes failures on an agentic/<customer>-<date>
branch, builds and deploys over the shared agents (one branch at a time,
rolled back if the PR is closed), and raises one PR to main per repository.
AC8, §4, §5, §5a, §9 and §10 amended to match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 21:03:50 +00:00
0890bc5c31 Plan: one UI in the KAB Docs Portal, the nightly cycle, skills
Amended 2026-11-12 with the owner: Shakedown has no UI of its own; the KAB
Docs Portal is the one UI and Shakedown its visualisation layer for workflow
case outputs, so Shakedown serves an API that accepts the portal's realm-kab
tokens. Adds the nightly cycle (5a: harvest, generate, execute, qualify,
prove, raise pull requests automatically for next-morning review, within a
standing daily budget; never merge or deploy), skills Bosun's sub-agents work
through (5), phase 7, and the engagement-id rule from cp1-agents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 10:28:36 +00:00