Add CP1 Discovery agents in both patterns
All checks were successful
check agents / check (push) Successful in 10s
All checks were successful
check agents / check (push) Successful in 10s
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,17 @@
|
||||
# 0010. Step outputs travel through the workflow; there is no shared store
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| Status | Proposed |
|
||||
| Date | 2026-10-29 |
|
||||
| Decided by | Built as a default; awaiting platform team confirmation |
|
||||
| Requirements changed | Platform rails PR-11 (evidence chain): each agent's outputs were to be recorded on a hash-linked chain |
|
||||
|
||||
## Decision
|
||||
|
||||
A step's output exists only as that step's reply. The executor carries it to later steps (externalising large payloads to execution storage) and registers it as an `execution_output` artifact.
|
||||
|
||||
## Consequences
|
||||
|
||||
- **No hash chain across steps:** evidence integrity rests on each fact's `evidence_ref` and the critic's call-log check.
|
||||
- **No memory between runs.** That is the cost of having no orchestrator; `../cp1-agents` keeps a workspace instead.
|
||||
Reference in New Issue
Block a user