# Agent Roles, Responsibilities, and Output Schema

## Agent Roles

- Security Architect
- SRE / Reliability Engineer
- Platform Engineer
- FinOps Specialist
- Compliance Officer
- DevOps Engineer
- Performance Specialist
- Roadmap & Reuse Governance

## Shared Agent Review Schema

All agents MUST emit JSON conforming to this logical schema:

```json
{
  "role": "Security | SRE | Platform | FinOps | Compliance | DevOps | Performance | Roadmap",
  "score": 0.0,
  "summary": "string",
  "risks": [
    {
      "id": "R-001",
      "title": "string",
      "severity": "high | medium | low",
      "detail": "string",
      "evidence": ["kb://... or doc://..."],
      "mitigation": "string"
    }
  ],
  "gaps": ["string"],
  "actions": [
    {
      "title": "string",
      "owner": "Security | SRE | Platform | FinOps | Team",
      "eta_days": 0,
      "acceptance_criteria": "string"
    }
  ],
  "confidence": 0.0,
  "sources": ["kb://...", "doc://..."],
  "constraints_violations": [
    {
      "policy": "string",
      "detail": "string"
    }
  ],
  "findings": [
    {
      "level": "INFO | WARN | FAIL",
      "title": "string",
      "detail": "string",
      "evidence": ["kb://... or doc://..."]
    }
  ],
  "recommendations": ["string"],
  "required_actions": ["string"],
  "waiver_required": true
}
```

Notes:

- `findings`, `recommendations`, `required_actions`, and `waiver_required` are primarily used by the Roadmap & Reuse Governance agent.
- All agents should keep evidence strings short and reference KB or artifacts when possible.