Build a GDPR-compliant legal contract review system with clause extraction, risk scoring, compliance reports, and human approval for high-risk decisions
| System Type | pipeline |
| Pattern | pipeline |
| Framework | crewai |
| Scale | medium |
| Autonomy Level | L3 |
| Infrastructure | Vector DB: pinecone | Graph DB: neo4j | Queue: redis | Observability: langfuse |
80/84 checks passed
| Status | Category | Agent | Check | Detail |
|---|---|---|---|---|
| ✗ | ATK-1 | doc_analyzer | system_prompt_isolation | Agent 'doc_analyzer' missing input injection detection |
| ✗ | ATK-1 | doc_analyzer | input_sanitization | Agent 'doc_analyzer' missing input injection detection |
| ⚠ | ATK-1 | doc_analyzer | instruction_hierarchy | Consider HITL for sensitive operations |
| ✗ | ATK-1 | risk_evaluator | system_prompt_isolation | Agent 'risk_evaluator' missing input injection detection |
| ✗ | ATK-1 | risk_evaluator | input_sanitization | Agent 'risk_evaluator' missing input injection detection |
| ⚠ | ATK-1 | guardian | instruction_hierarchy | Consider HITL for sensitive operations |
| ⚠ | ATK-2 | doc_analyzer | role_boundary_enforcement | Consider HITL for sensitive operations |
| ⚠ | ATK-2 | doc_analyzer | multi_turn_tracking | Consider HITL for sensitive operations |
| ⚠ | ATK-2 | guardian | role_boundary_enforcement | Consider HITL for sensitive operations |
| ⚠ | ATK-2 | guardian | multi_turn_tracking | Consider HITL for sensitive operations |
| ⚠ | ATK-3 | orchestrator | system_prompt_protection | Ensure system prompts are not exposed in tool outputs |
| ⚠ | ATK-3 | doc_analyzer | system_prompt_protection | Ensure system prompts are not exposed in tool outputs |
| ⚠ | ATK-3 | doc_analyzer | rag_access_control | RAG enabled — ensure access control on retrieval |
| ⚠ | ATK-3 | risk_evaluator | system_prompt_protection | Ensure system prompts are not exposed in tool outputs |
| ⚠ | ATK-3 | risk_evaluator | rag_access_control | RAG enabled — ensure access control on retrieval |
| ⚠ | ATK-3 | guardian | system_prompt_protection | Ensure system prompts are not exposed in tool outputs |
| ⚠ | ATK-4 | doc_analyzer | inter_agent_auth | Verify agent-to-agent auth at framework level |
| ⚠ | ATK-4 | doc_analyzer | message_validation | Add input validation for inter-agent messages |
| ⚠ | ATK-4 | doc_analyzer | privilege_boundaries | Add input validation for inter-agent messages |
| ⚠ | ATK-4 | risk_evaluator | inter_agent_auth | Verify agent-to-agent auth at framework level |
| ⚠ | ATK-4 | risk_evaluator | message_validation | Add input validation for inter-agent messages |
| ⚠ | ATK-4 | risk_evaluator | privilege_boundaries | Add input validation for inter-agent messages |
| ⚠ | ATK-4 | guardian | inter_agent_auth | Verify agent-to-agent auth at framework level |
| ⚠ | ATK-6 | orchestrator | recursion_depth_limits | Recursion limits should be configured at framework level |
| ⚠ | ATK-6 | doc_analyzer | recursion_depth_limits | Recursion limits should be configured at framework level |
| ⚠ | ATK-6 | risk_evaluator | recursion_depth_limits | Recursion limits should be configured at framework level |
| ⚠ | ATK-6 | guardian | recursion_depth_limits | Recursion limits should be configured at framework level |
| ⚠ | ATK-7 | orchestrator | pii_detection | Agent 'orchestrator' has no PII detection on input |
| ⚠ | ATK-7 | orchestrator | context_isolation | Verify context isolation between users at runtime |
| ⚠ | ATK-7 | doc_analyzer | pii_detection | Agent 'doc_analyzer' has no PII detection on input |
| ⚠ | ATK-7 | doc_analyzer | context_isolation | Verify context isolation between users at runtime |
| ⚠ | ATK-7 | risk_evaluator | pii_detection | Agent 'risk_evaluator' has no PII detection on input |
| ⚠ | ATK-7 | risk_evaluator | context_isolation | Verify context isolation between users at runtime |
| ⚠ | ATK-7 | guardian | context_isolation | Verify context isolation between users at runtime |
| LLM Cost | $1940.00 |
| Infrastructure | $200 |
| Total | $2140.00/mo |
Based on 2 detected responsibilities and deterministic nature.
2-3 sequential responsibilities with clear data handoffs. Pipeline is simplest.
| Requirement | Component | Status |
|---|---|---|
| Art. 13-14 Transparency | guardrails.output → explainability | Review |
| Art. 15 Right of access | audit_trail → logging | Configured |
| Art. 17 Right to erasure | memory → deletion endpoint | Review |
| Art. 25 Data protection by design | guardrails.input → pii_detection | Configured |
| Art. 35 DPIA | blueprint.decisions | Review |