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>
This commit is contained in:
8
workflows/alz-f01-discovery.yaml
Normal file
8
workflows/alz-f01-discovery.yaml
Normal file
@@ -0,0 +1,8 @@
|
||||
# ALZ-F01 Discovery (ADO Feature 3214441). Registry entry: plan §3c.
|
||||
key: alz-f01-discovery
|
||||
pattern: sub-agents # the 2026-11-15 pivot: the individual-pattern agents were removed from `agents`
|
||||
feature: f01 # the feature name cp1-agents scripts/evaluate_case.py takes
|
||||
# Workflow names KAB may show for it. A run's workflow id is checked against these before it starts, because ids
|
||||
# change on every re-import (same names as the docs portal's registry/workflows.yaml).
|
||||
names: ["CP1 - Agentic Landing Zone - Discovery"]
|
||||
context: upload # the run context is uploaded to u1 (file); its workflow_inputs become run inputs
|
||||
Reference in New Issue
Block a user