Files
cp1-agents/outcome-pattern/solution_architecture/cp1-solution-architecture-agent/schemas/input.json
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate
stream from the individual and sub-agent patterns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

15 lines
951 B
JSON

{
"type": "object",
"properties": {
"phase": {"type": "string", "enum": ["scoping", "requirements_discovery", "solution_architecture", "solution_implementation", "solution_validation", "packaging", "complete"], "description": "Set by a workflow step. A conversation leaves it out."},
"message": {"type": "string", "description": "One conversation turn, or the workflow request."},
"engagement": {"type": "string", "description": "The customer case's slug."},
"cloud_provider": {"type": "string", "enum": ["gcp", "azure", "aws"]},
"scope_spec": {"type": "string", "description": "A scope spec, as YAML."},
"conversation_id": {"type": "string", "description": "Ties a conversation's turns together when the A2A contextId isn't available."},
"allow_cloud_read": {"type": "boolean"},
"pre_approved": {"type": "boolean"},
"hitl_feedback": {"type": "string", "description": "A reviewer's comments on a rerun."}
}
}