- Six declarative agents generated from the v1.1 stories (scaffold_from_stories.py, ADR 0001),
and a 9-step workflow export (build_workflow.py).
- Code-only intake (ADR 0008) verifies the one Discovery package in code before any agent.
- The rate card is the run input rate_card_document; no upload step (ADR 0009).
- Critic 0.1.6 after live runs on crucible-kab-dev:
- K-12 model independence checked at build time against each agent's deployed model
(ADR 0010); the critic reports it from its two inputs;
- receives in_cloud_estate for K-10; an unverified K-10 never fails the run alone;
- K-08 allows the scoring note to list findings as advisory, as ALZ-ASM-04 must;
- carries ALZ-ASM-03's and ALZ-ASM-04's rule sections, copied by the scaffold, so it can
recalculate risk, confidence and TCO.
- The scaffold refuses to regenerate unless every story file is present.
- Case azure-crucible-kab-dev-assessment with an illustrative rate card.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
0002. Discovery's outputs reach the agents as parsed text; run id and approval are run inputs
| Status | Proposed |
| Date | 2026-11-02 |
| Decided by | Built as a default; awaiting product owner confirmation |
| Requirements changed | Feature AC4 and ASM-01 US-001 (the approval and run-status preconditions) |
Context
A workflow can't run or chain another workflow (docs/platform-issues/workflow-composition/). The Artifacts step's only output is artifacts: per-file records with base64 content. Review decisions are written to the activity log, not onto artifacts.
Decision
- Front steps.
a1(Artifacts) selects the Discovery run's artifacts by exact id.p1(Parse Assessment Files) turnsa1.artifactsintoparsed_contentandfile_metadata. Every agent that reads Discovery takes both, asdiscovery_documentsanddiscovery_files. - No model copies Discovery's records between steps.
- Run inputs:
artifact_ids(unless the export fixes them),discovery_execution_id, anddiscovery_approval_ref, the decision record approving the Discovery run. discovery_completedis read as "the critic and report documents are both present". A failed run registers only the outputs it reached.- References to Discovery records are written
discovery:{execution_id}/{agent_id}/{record_key}, because Discovery's records carry no record-level reference of their own.
Consequences
- The approval can't be verified by the agents; they trust the reference they're given. The fix is platform-side: record the run outcome on its artifacts (workflow-composition question 3).
- An output too large to inline (over 8 MiB live) arrives with no content and is skipped by the parser. The agents report it as a missing document.
- The person starting the run has to find the right artifact ids.