mikeparcewski/five-layer-architecture
skills/agentic/five-layer-architecture/SKILL.md
Five-layer architectural model for building production-grade agentic systems with clear separation of concerns. Use when: "agent architecture layers", "five layer", "agent system design", "separation of concerns agents"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden five-layer-architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:58 AM6.8s6 files scanned
SKILL.md
- name:
- five-layer-architecture
- description:
- |
- Use when:
- agent architecture layers", "five layer", "agent system design", "separation of concerns agents
- portability:
- portable
Five-Layer Architecture
A layered architecture model for agentic systems that separates concerns and enables scalable, maintainable, production-ready systems.
The Five Layers
┌─────────────────────────────────────┐
│ Layer 5: Governance │ Safety, compliance, audit
├─────────────────────────────────────┤
│ Layer 4: Runtime │ Execution, monitoring, scaling
├─────────────────────────────────────┤
│ Layer 3: Interaction │ Tools, APIs, communication
├─────────────────────────────────────┤
│ Layer 2: Context │ Memory, state, knowledge
├─────────────────────────────────────┤
│ Layer 1: Cognition │ Reasoning, planning, decisions
└─────────────────────────────────────┘
Layer 1: Cognition
Core intelligence - reasoning, planning, and decision-making.
- Task understanding and decomposition
- Planning and strategy formulation
- Reasoning patterns (ReAct, Chain-of-Thought)
- Meta-cognition and self-reflection
- Anti-pattern: Mixing business logic into prompts, no separation between reasoning and action
Layer 2: Context
Memory, state, and knowledge management.
- Short-term working memory (conversation history)
- Long-term memory (persistent knowledge, vector search)
- State management and checkpointing
- Context window optimization and compression
- Anti-pattern: Passing entire history to every agent (context bloat)
Layer 3: Interaction
Tools, APIs, and communication channels.
- Tool/function registry and execution
- External API integration with error handling
- Multi-agent communication protocols
- Rate limiting, retry logic, serialization
- Anti-pattern: Tight coupling, no retry/timeout, missing input validation
Layer 4: Runtime
Execution environment, monitoring, and scaling.
- Agent lifecycle management (start, stop, restart)
- Concurrent execution and orchestration
- Observability (logging, tracing, metrics)
- Resource quotas, health checks, circuit breakers
- Anti-pattern: No observability, no resource limits, synchronous bottlenecks
Layer 5: Governance
Safety, compliance, and audit.
- Safety guardrails and action constraints
- Human-in-the-loop approval gates
- Audit logging, traceability, compliance
- PII detection, access control, rollback
- Anti-pattern: No approval gates, missing audit trails, no rollback
Layer Interaction Patterns
Bottom-Up Flow: Cognition decides → Context provides info → Interaction executes → Runtime monitors → Governance validates
Top-Down Constraints: Governance sets policies → Runtime enforces limits → Interaction restricts tools → Context filters sensitive data → Cognition operates within constraints
Cross-Layer: Observability, security, error handling, and performance optimization span all layers.
Designing a New System
- Start with Cognition: What reasoning/planning capability do you need?
- Add Context: What information must agents remember?
- Define Interaction: What tools/APIs do agents need?
- Build Runtime: How will you execute, monitor, scale?
- Implement Governance: What safety/compliance is required?
Quick Reference
| Layer | Focus | Key Question | Example Component | |-------|-------|--------------|-------------------| | 1. Cognition | Intelligence | "What should I do?" | LLM reasoning | | 2. Context | Memory | "What do I know?" | Vector database | | 3. Interaction | Tools | "How do I act?" | API clients | | 4. Runtime | Execution | "Is it working?" | Monitoring | | 5. Governance | Safety | "Is it safe?" | Approval gates |
When to Use
- "How should I architect my agentic system?"
- "Where does [component] belong in the architecture?"
- "My system is getting messy and hard to maintain"
- "How do I separate concerns in my agent system?"
References
refs/layers-cognition-context.md- Layer 1 (Cognition) and Layer 2 (Context) with implementation patternsrefs/layers-interaction-runtime.md- Layer 3 (Interaction) and Layer 4 (Runtime) with implementation patternsrefs/layers-governance-integration.md- Layer 5 (Governance) and cross-layer integration examplerefs/implementation-guide-layers-1-3.md- Building Layers 1-3 (Cognition, Context, Interaction)refs/implementation-guide-layers-4-5.md- Building Layers 4-5 (Runtime, Governance) and complete system
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026