From wicked-garden
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"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
A layered architecture model for agentic systems that separates concerns and enables scalable, maintainable, production-ready systems.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
A layered architecture model for agentic systems that separates concerns and enables scalable, maintainable, production-ready systems.
┌─────────────────────────────────────┐
│ 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
└─────────────────────────────────────┘
Core intelligence - reasoning, planning, and decision-making.
Memory, state, and knowledge management.
Tools, APIs, and communication channels.
Execution environment, monitoring, and scaling.
Safety, compliance, and audit.
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.
| 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 |
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