Layered System Architecture Stack

Five-layer abstraction stack with single responsibility per layer and downward dependencies only.

Prompt

A five-layer abstraction stack diagram, drawn as a vertical stack of horizontal slabs.

Top to bottom (each slab is a labeled rectangle with rounded corners):

Layer 5 — Federation
- KGRAG-style orchestrator coordinating multiple sub-systems

Layer 4 — Application
- Domain-specific business logic and workflows

Layer 3 — Service
- API gateways, authentication, rate limiting

Layer 2 — Data
- Persistence stores (relational, vector, object) and message buses

Layer 1 — Infrastructure
- Compute, network, storage primitives

Annotations:
- Each layer has a single one-line responsibility.
- Each layer's dependency arrow points strictly downward; no upward or sideways arrows.
- A small "depends only on layers below" caption near the bottom.

Style: clean systems-architecture diagram, restrained palette (5 hues from cool to warm bottom-up), white background, sans-serif labels. Suitable for engineering blog posts and infra textbooks.

Use in Generator

When to use

For systems architecture explanations, infrastructure decks, and clean-architecture education.

Variations

With cross-cutting concerns

Add a vertical right-side band labeled "Cross-cutting concerns" with three sub-bands: Observability, Security, Configuration. The band spans all 5 layers.

Tips

Use 4-6 layers. Fewer feels trivial; more becomes unscannable.
Always show dependency direction explicitly (downward arrows). It's the defining property.
Limit each layer label to one line. Multi-line labels destroy the clean stack rhythm.

FAQ

How do I show optional layers?

Use a dashed border on optional layers and a "(optional)" label after the layer name.