---
title: "Architecture Visual Explainers"
description: "26 visual explainers about Architecture."
---

# Architecture Visual Explainers
> 26 visual explainers about Architecture.

## Visual Explainers

### [AI-DLC Architecture: One Spec Spine Through Inception, Design, and Construction](https://yomu.fyi/visual-explainers/ai-dlc-architecture-one-spec-spine-through-inception-design-and-construction.md)
- Type: Architecture
- Tags: [Agentic Development](https://yomu.fyi/topic/agentic-development.md), [AI-DLC](https://yomu.fyi/topic/ai-dlc.md), [Coding Agents](https://yomu.fyi/topic/coding-agents.md), [Human-in-the-Loop](https://yomu.fyi/topic/human-in-the-loop.md), [Kiro IDE](https://yomu.fyi/topic/kiro-ide.md), [Verification](https://yomu.fyi/topic/verification.md)

AI-DLC is an AI-driven development lifecycle that runs delivery through Inception, Design, and Construction, with specs, steering files, and hooks keeping agents aligned to agreed intent.

### [One Pool, Many Engines: The Architecture of Apple Silicon](https://yomu.fyi/visual-explainers/one-pool-many-engines-the-architecture-of-apple-silicon.md)
- Type: Architecture
- Tags: [Apple](https://yomu.fyi/topic/apple.md), [Apple Silicon](https://yomu.fyi/topic/apple-silicon.md), [GPU](https://yomu.fyi/topic/gpu.md), [macOS](https://yomu.fyi/topic/macos.md), [MLX](https://yomu.fyi/topic/mlx.md), [MPS](https://yomu.fyi/topic/mps.md)

Apple Silicon's defining choice is one shared memory pool for CPU, GPU, and Neural Engine. This diagram maps that fabric, the on-package bandwidth it buys, and the scaling limits it imposes.

### [The AMR Surveillance Stack: From Raw Reads to Governed Answers](https://yomu.fyi/visual-explainers/the-amr-surveillance-stack-from-raw-reads-to-governed-answers.md)
- Type: Architecture
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Antimicrobial Resistance](https://yomu.fyi/topic/antimicrobial-resistance.md), [Biology](https://yomu.fyi/topic/biology.md), [Data Governance](https://yomu.fyi/topic/data-governance.md), [Healthcare](https://yomu.fyi/topic/healthcare.md), [Public Health](https://yomu.fyi/topic/public-health.md)

Antimicrobial resistance surveillance is a layered data architecture: raw reads and demand signals flow in, get normalized into governed tables, and answer plain-language queries. The diagram maps each boundary.

### [Where Amazon Bedrock Sits: A Layered Architecture for Grounded Agents](https://yomu.fyi/visual-explainers/where-amazon-bedrock-sits-a-layered-architecture-for-grounded-agents.md)
- Type: Architecture
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Amazon Bedrock](https://yomu.fyi/topic/amazon-bedrock.md), [Architecture](https://yomu.fyi/topic/architecture.md), [AWS](https://yomu.fyi/topic/aws.md), [Guardrails](https://yomu.fyi/topic/guardrails.md), [Strands Agents SDK](https://yomu.fyi/topic/strands-agents-sdk.md)

Amazon Bedrock is the managed reasoning tier in an agent architecture, not the whole system. This layered view shows the pipelines, governed tables, query layer, and guardrails around it.

### [API Versioning as a Translation Layer](https://yomu.fyi/visual-explainers/api-versioning-as-a-translation-layer.md)
- Type: Architecture
- Tags: [API](https://yomu.fyi/topic/api.md), [API Versioning](https://yomu.fyi/topic/api-versioning.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Developer Platform](https://yomu.fyi/topic/developer-platform.md), [REST APIs](https://yomu.fyi/topic/rest-api.md), [Webhooks](https://yomu.fyi/topic/webhooks.md)

API versioning as an architecture: requests enter through a version header, pass through a chain of reversible version changes, and reach controllers that only ever see the latest model.

### [Anatomy of a Branded Call: The Trust Chain from Dial to Display](https://yomu.fyi/visual-explainers/anatomy-of-a-branded-call-the-trust-chain-from-dial-to-display.md)
- Type: Architecture
- Tags: [Branded Calling](https://yomu.fyi/topic/branded-calling.md), [RCS](https://yomu.fyi/topic/rcs.md), [Security](https://yomu.fyi/topic/security.md), [SMS](https://yomu.fyi/topic/sms.md), [Twilio](https://yomu.fyi/topic/twilio.md), [Voice AI](https://yomu.fyi/topic/voice-ai.md)

The Branded Calling trust chain, layer by layer: how identity, STIR/SHAKEN attestation, Rich Call Data, and carrier delivery combine so a verified brand name reaches the recipient's screen.

### [BIAN as a Contract Layer: Modernizing Core Banking One Domain at a Time](https://yomu.fyi/visual-explainers/bian-as-a-contract-layer-modernizing-core-banking-one-domain-at-a-time.md)
- Type: Architecture
- Tags: [Architecture](https://yomu.fyi/topic/architecture.md), [BIAN](https://yomu.fyi/topic/bian.md), [Core Banking](https://yomu.fyi/topic/core-banking.md), [Integration](https://yomu.fyi/topic/integration.md), [Microservices](https://yomu.fyi/topic/microservices.md), [Modernization](https://yomu.fyi/topic/modernization.md)

BIAN gives banks a shared vocabulary and service-domain contracts that sit between business concepts and the systems implementing them. See how domains, contracts, and governed access stack into one architecture.

### [The Agentic Ad Stack: Where Governance Sits Between Signals and Spend](https://yomu.fyi/visual-explainers/the-agentic-ad-stack-where-governance-sits-between-signals-and-spend.md)
- Type: Architecture
- Tags: [A/B Testing](https://yomu.fyi/topic/a-b-testing.md), [Advertising](https://yomu.fyi/topic/advertising.md), [Marketing](https://yomu.fyi/topic/marketing.md), [MCP](https://yomu.fyi/topic/mcp.md), [Personalization](https://yomu.fyi/topic/personalization.md), [Unity Catalog](https://yomu.fyi/topic/unity-catalog.md)

An agentic ad stack wires governed customer signals to campaign execution through a shared tool interface and server-side guardrails. The diagram shows each layer, the direction of a tool call, and where control stays human.

### [Asset Management's Four Layers: From Custodian File to Signed NAV](https://yomu.fyi/visual-explainers/asset-management-s-four-layers-from-custodian-file-to-signed-nav.md)
- Type: Architecture
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Asset Management](https://yomu.fyi/topic/asset-management.md), [Auditability](https://yomu.fyi/topic/auditability.md), [Data Governance](https://yomu.fyi/topic/data-governance.md), [Human-in-the-Loop](https://yomu.fyi/topic/human-in-the-loop.md), [Ontology](https://yomu.fyi/topic/ontology.md)

Asset management runs as a layered control plane: custodian and pricing data feed a governed context layer, agents run the overnight fund work, and a human signs off before anything is published.

### [Amazon EVS Architecture: Where vSAN Ends and FSx for ONTAP Begins](https://yomu.fyi/visual-explainers/amazon-evs-architecture-where-vsan-ends-and-fsx-for-ontap-begins.md)
- Type: Architecture
- Tags: [Amazon EVS](https://yomu.fyi/topic/amazon-evs.md), [AWS](https://yomu.fyi/topic/aws.md), [Disaster Recovery](https://yomu.fyi/topic/disaster-recovery.md), [FSx for NetApp ONTAP](https://yomu.fyi/topic/fsx-for-netapp-ontap.md), [Migrations](https://yomu.fyi/topic/migration.md), [Virtualization](https://yomu.fyi/topic/virtualization.md)

Amazon EVS runs VMware Cloud Foundation on AWS bare metal, so the design question becomes where each workload's data lives. This layered diagram shows how vSAN, FSx for ONTAP, and cross-Region DR divide the work.

### [Application Security as a Closed Loop: Discover, Govern, Protect, Learn](https://yomu.fyi/visual-explainers/application-security-as-a-closed-loop-discover-govern-protect-learn.md)
- Type: Architecture
- Tags: [Application Security](https://yomu.fyi/topic/application-security.md), [Least Privilege](https://yomu.fyi/topic/least-privilege.md), [Security](https://yomu.fyi/topic/security.md), [Threat Intelligence](https://yomu.fyi/topic/threat-intelligence.md), [Vulnerabilities](https://yomu.fyi/topic/vulnerabilities.md), [WAF](https://yomu.fyi/topic/waf.md)

Application security is a closed loop: discover and prioritize risk, govern access and agent behavior, protect at runtime, then investigate and feed findings back into the next cycle.

### [AG-UI as the Agent–UI Contract Layer](https://yomu.fyi/visual-explainers/ag-ui-as-the-agent-ui-contract-layer.md)
- Type: Architecture
- Tags: [A2UI](https://yomu.fyi/topic/a2ui.md), [AG-UI](https://yomu.fyi/topic/ag-ui.md), [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Human-in-the-Loop](https://yomu.fyi/topic/human-in-the-loop.md), [Server-Driven UI](https://yomu.fyi/topic/server-driven-ui.md), [Streaming](https://yomu.fyi/topic/streaming.md)

AG-UI is a typed event contract between an agent backend and a frontend, turning streamed agent state into UI. This diagram maps the layers and shows where human review plugs in.

### [Anatomy of a Bug Bounty Pipeline: From First Report to Upstream Patch](https://yomu.fyi/visual-explainers/anatomy-of-a-bug-bounty-pipeline-from-first-report-to-upstream-patch.md)
- Type: Architecture
- Tags: [Bug Bounty](https://yomu.fyi/topic/bug-bounty.md), [HackerOne](https://yomu.fyi/topic/hackerone.md), [Incident Response](https://yomu.fyi/topic/incident-response.md), [Security](https://yomu.fyi/topic/security.md), [Vulnerabilities](https://yomu.fyi/topic/vulnerabilities.md)

An architecture view of a bug bounty program: scope, triage, validation, containment, durable fix, and payout, plus the loop that turns each report into stronger defaults.

### [Where BPF Hooks In: Choosing the Attachment Layer](https://yomu.fyi/visual-explainers/where-bpf-hooks-in-choosing-the-attachment-layer.md)
- Type: Architecture
- Tags: [BPF](https://yomu.fyi/topic/bpf.md), [eBPF](https://yomu.fyi/topic/ebpf.md), [Linux](https://yomu.fyi/topic/linux.md), [Networking](https://yomu.fyi/topic/networking.md), [sched\_ext](https://yomu.fyi/topic/sched-ext.md), [XDP](https://yomu.fyi/topic/xdp.md)

BPF is not one hook but a set of attachment points, and each one sees different traffic. This diagram maps XDP, TC, socket-level BPF LSM, and sched\_ext so you can pick the layer that can actually enforce your rule.

### [Bot Management as an Adaptive Control Loop](https://yomu.fyi/visual-explainers/bot-management-as-an-adaptive-control-loop.md)
- Type: Architecture
- Tags: [Bot Management](https://yomu.fyi/topic/bot-management.md), [Cloudflare](https://yomu.fyi/topic/cloudflare.md), [Load Shedding](https://yomu.fyi/topic/load-shedding.md), [Security](https://yomu.fyi/topic/security.md), [Turnstile](https://yomu.fyi/topic/turnstile.md)

Bot management is an architecture, not a rule list: classify traffic, score it with continuously retrained models, enforce with challenges or blocks, then feed the outcomes back into the model.

### [The API Gateway Boundary: Where Protocol, Policy, and Protection Meet](https://yomu.fyi/visual-explainers/the-api-gateway-boundary-where-protocol-policy-and-protection-meet.md)
- Type: Architecture
- Tags: [API](https://yomu.fyi/topic/api.md), [API Gateway](https://yomu.fyi/topic/api-gateway.md), [Microservices](https://yomu.fyi/topic/microservices.md), [Observability](https://yomu.fyi/topic/observability.md), [Rate Limiting](https://yomu.fyi/topic/rate-limiting.md), [Routing](https://yomu.fyi/topic/routing.md)

The API gateway is the single boundary where protocol translation, auth, quotas, and routing become shared policy instead of per-service code. This layered diagram shows what belongs there and why.

### [Hybrid Agent Runtime: Antigravity SDK's Local and Cloud Split](https://yomu.fyi/visual-explainers/hybrid-agent-runtime-antigravity-sdk-s-local-and-cloud-split.md)
- Type: Architecture
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [AI Gateway](https://yomu.fyi/topic/ai-gateway.md), [Antigravity SDK](https://yomu.fyi/topic/antigravity.md), [Local AI](https://yomu.fyi/topic/local-ai.md), [Model Routing](https://yomu.fyi/topic/model-routing.md), [Privacy](https://yomu.fyi/topic/privacy.md)

Antigravity SDK's hybrid architecture separates planning from execution: a cloud model plans, local models run most tokens on-device. See how routing, execution, and the data boundary fit together.

### [AI Data Assimilation: Turning Scattered Signals Into One State](https://yomu.fyi/visual-explainers/ai-data-assimilation-turning-scattered-signals-into-one-state.md)
- Type: Architecture
- Tags: [AI Data Assimilation](https://yomu.fyi/topic/ai-data-assimilation.md), [Architecture](https://yomu.fyi/topic/architecture.md), [CorrDiff](https://yomu.fyi/topic/corrdiff.md), [NVIDIA Earth-2](https://yomu.fyi/topic/nvidia-earth-2.md), [Ontology](https://yomu.fyi/topic/ontology.md), [StormCast](https://yomu.fyi/topic/stormcast.md)

AI data assimilation fuses a model's prior state with fresh, uneven observations into one consistent state. See the four-layer architecture and where each layer can break.

### [Anka CI Architecture: From Layered Images to Disposable macOS Builds](https://yomu.fyi/visual-explainers/anka-ci-architecture-from-layered-images-to-disposable-macos-builds.md)
- Type: Architecture
- Tags: [Anka](https://yomu.fyi/topic/anka.md), [Architecture](https://yomu.fyi/topic/architecture.md), [CI/CD](https://yomu.fyi/topic/ci-cd.md), [Deployment](https://yomu.fyi/topic/deployment.md), [Docker](https://yomu.fyi/topic/docker.md)

Anka is a Docker-like macOS virtualization layer for disposable CI environments. This architecture shows how images, Mac hosts, snapshots, build agents, and artifacts connect.

### [Amazon EKS as a Platform Boundary Map](https://yomu.fyi/visual-explainers/amazon-eks-as-a-platform-boundary-map.md)
- Type: Architecture
- Tags: [Amazon EKS](https://yomu.fyi/topic/amazon-eks.md), [Architecture](https://yomu.fyi/topic/architecture.md), [AWS](https://yomu.fyi/topic/aws.md), [Kubernetes](https://yomu.fyi/topic/kubernetes.md)

See how a shared Amazon EKS architecture separates workloads, platform services, and network connectivity so teams can scale delivery without multiplying operational ownership.

[Older explainers](https://yomu.fyi/visual-explainers/category/architecture/page/2.md)