---
title: "Visual Explainers — page 3"
description: "Visual introductions to the engineering concepts behind the tools we use."
---

# Visual Explainers — page 3
> Visual introductions to the engineering concepts behind the tools we use.

## Visual Explainers

### [How to Give an Agent a Query Language Instead of a Code Interpreter](https://yomu.fyi/visual-explainers/how-to-give-an-agent-a-query-language-instead-of-a-code-interpreter.md)
- Type: How to
- Tags: [Aggregation Pipeline](https://yomu.fyi/topic/aggregation-pipeline.md), [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Caching](https://yomu.fyi/topic/caching.md), [Least Privilege](https://yomu.fyi/topic/least-privilege.md), [MongoDB](https://yomu.fyi/topic/mongodb.md), [Security](https://yomu.fyi/topic/security.md)

A four-step pattern for letting a document agent write validated aggregation pipelines instead of arbitrary code, so results come back shaped and tenancy stays enforced.

### [Accountability: Named Owner or Enforced Mechanism?](https://yomu.fyi/visual-explainers/accountability-named-owner-or-enforced-mechanism.md)
- Type: Comparison
- Tags: [Accountability](https://yomu.fyi/topic/accountability.md), [Auditability](https://yomu.fyi/topic/auditability.md), [Decision-Making](https://yomu.fyi/topic/decision-making.md), [Least Privilege](https://yomu.fyi/topic/least-privilege.md), [Observability](https://yomu.fyi/topic/observability.md), [Systems Thinking](https://yomu.fyi/topic/systems-thinking.md)

A side-by-side comparison of the two accountability models engineers actually rely on: a named human owner per outcome, and system-enforced traces, budgets, and isolation.

### [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 GPU-Resident Astronomy Pipeline](https://yomu.fyi/visual-explainers/the-gpu-resident-astronomy-pipeline.md)
- Type: What is it?
- Tags: [Astronomy](https://yomu.fyi/topic/astronomy.md), [CUDA](https://yomu.fyi/topic/cuda.md), [Data Pipelines](https://yomu.fyi/topic/data-pipelines.md), [GPU](https://yomu.fyi/topic/gpu.md), [Image Analysis](https://yomu.fyi/topic/image-analysis.md)

A GPU-resident astronomy pipeline keeps every stage of image analysis — load, align, subtract, detect, review — inside GPU memory instead of round-tripping through the CPU.

### [Bare Metal: Performance Bet vs. Operations Tax](https://yomu.fyi/visual-explainers/bare-metal-performance-bet-vs-operations-tax.md)
- Type: Trade-offs
- Tags: [Bare Metal](https://yomu.fyi/topic/bare-metal.md), [GPU](https://yomu.fyi/topic/gpu.md), [Kubernetes](https://yomu.fyi/topic/kubernetes.md), [Networking](https://yomu.fyi/topic/networking.md), [Performance](https://yomu.fyi/topic/performance.md), [Virtualization](https://yomu.fyi/topic/virtualization.md)

Bare metal gives engineers direct control over GPU, network, and virtualization layers, but it shifts elasticity and lifecycle work onto the team. This trade-off map shows when that bargain pays off.

### [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.

### [A/B Testing: The Confidence Budget](https://yomu.fyi/visual-explainers/a-b-testing-the-confidence-budget.md)
- Type: Trade-offs
- Tags: [A/B Testing](https://yomu.fyi/topic/a-b-testing.md), [Analytics](https://yomu.fyi/topic/analytics.md), [Decision-Making](https://yomu.fyi/topic/decision-making.md), [Deployment](https://yomu.fyi/topic/deployment.md), [Experimentation](https://yomu.fyi/topic/experimentation.md), [Trust Calibration](https://yomu.fyi/topic/trust-calibration.md)

A/B testing trades traffic, time, and exposure risk for evidence. This explainer maps the benefit of a controlled comparison, the real cost of running one, and the condition that decides when measuring beats shipping on judgment.

### [Arabic Is Not One Target: A Mental Model for Dialect Adaptation](https://yomu.fyi/visual-explainers/arabic-is-not-one-target-a-mental-model-for-dialect-adaptation.md)
- Type: What is it?
- Tags: [Arabic](https://yomu.fyi/topic/arabic.md), [Benchmark](https://yomu.fyi/topic/benchmark.md), [Localization](https://yomu.fyi/topic/localization.md), [Multilingual](https://yomu.fyi/topic/multilingual.md), [Synthetic Data](https://yomu.fyi/topic/synthetic-data.md)

Arabic is not a single target for a language model. This explainer maps its four parts — dialect surface, data pipeline, model, and evaluation — so you can tell where an Arabic feature really succeeds or fails.

### [The BI Trade-Off: Answer Speed vs. Time to Trust](https://yomu.fyi/visual-explainers/the-bi-trade-off-answer-speed-vs-time-to-trust.md)
- Type: Trade-offs
- Tags: [Business Intelligence](https://yomu.fyi/topic/business-intelligence.md), [Data Governance](https://yomu.fyi/topic/data-governance.md), [Data Quality](https://yomu.fyi/topic/data-quality.md), [Data Visualization](https://yomu.fyi/topic/data-visualization.md), [Decision-Making](https://yomu.fyi/topic/decision-making.md)

Business Intelligence turns operational data into decisions, but every speed-up trades against trust. This diagram maps the benefit, cost, and condition behind governed metrics, shared context, and provenance.

### [One IDE vs. the Right Tool: Android Studio's Boundary Trade-off](https://yomu.fyi/visual-explainers/one-ide-vs-the-right-tool-android-studio-s-boundary-trade-off.md)
- Type: Trade-offs
- Tags: [Android Studio](https://yomu.fyi/topic/android-studio.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md), [JetBrains](https://yomu.fyi/topic/jetbrains.md), [Kotlin](https://yomu.fyi/topic/kotlin.md), [Kotlin Multiplatform](https://yomu.fyi/topic/kotlin-multiplatform.md), [Xcode](https://yomu.fyi/topic/xcode.md)

Android Studio keeps cross-platform Kotlin run and debug in one workspace but hands Swift editing to Xcode. This explainer maps the benefit, cost, and condition behind that boundary.

### [Bun Is a Toolkit, Not Just a Runtime](https://yomu.fyi/visual-explainers/bun-is-a-toolkit-not-just-a-runtime.md)
- Type: What is it?
- Tags: [Bun](https://yomu.fyi/topic/bun.md), [Deployment](https://yomu.fyi/topic/deployment.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md), [Node.js](https://yomu.fyi/topic/node-js.md), [Performance](https://yomu.fyi/topic/performance.md), [TypeScript](https://yomu.fyi/topic/typescript.md)

Bun packs a runtime, package manager, bundler, and test runner into one binary. Here is how those four parts fit together and where the seams still show.

### [How to Build on BlueField with DOCA Agent Skills](https://yomu.fyi/visual-explainers/how-to-build-on-bluefield-with-doca-agent-skills.md)
- Type: How to
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [BlueField](https://yomu.fyi/topic/bluefield.md), [Coding Agents](https://yomu.fyi/topic/coding-agents.md), [DOCA](https://yomu.fyi/topic/doca.md), [DPU](https://yomu.fyi/topic/dpu.md), [NVIDIA](https://yomu.fyi/topic/nvidia.md)

A practical how-to for using NVIDIA DOCA Agent Skills to generate BlueField code with verified APIs and hardware checks, reducing correction cycles and failed builds.

### [Verifiability vs. Control: What a Shared Ledger Actually Costs](https://yomu.fyi/visual-explainers/verifiability-vs-control-what-a-shared-ledger-actually-costs.md)
- Type: Trade-offs
- Tags: [Auditability](https://yomu.fyi/topic/auditability.md), [Blockchain](https://yomu.fyi/topic/blockchain.md), [Cryptography](https://yomu.fyi/topic/cryptography.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md), [Payments](https://yomu.fyi/topic/payments.md), [Verification](https://yomu.fyi/topic/verification.md)

A tradeoff view of blockchain: a shared ledger buys verifiable settlement between parties that do not share an operator, and charges throughput, latency, and governance in return.

### [Copy-and-Replay vs Branch-at-a-Point: Two Backup Recovery Paths](https://yomu.fyi/visual-explainers/copy-and-replay-vs-branch-at-a-point-two-backup-recovery-paths.md)
- Type: Comparison
- Tags: [Backups](https://yomu.fyi/topic/backups.md), [Direct I/O](https://yomu.fyi/topic/direct-io.md), [Disaster Recovery](https://yomu.fyi/topic/disaster-recovery.md), [Postgres](https://yomu.fyi/topic/postgres.md), [Reliability](https://yomu.fyi/topic/reliability.md), [Replication](https://yomu.fyi/topic/replication.md)

A side-by-side comparison of copy-and-replay recovery and branch-at-a-point restores, showing why restore time scales with data size in one model and not the other.

### [Backdoor Defense Is a Trade-off, Not a Scanner](https://yomu.fyi/visual-explainers/backdoor-defense-is-a-trade-off-not-a-scanner.md)
- Type: Trade-offs
- Tags: [AI Security](https://yomu.fyi/topic/ai-security.md), [Backdoors](https://yomu.fyi/topic/backdoors.md), [Safety](https://yomu.fyi/topic/safety.md), [Security](https://yomu.fyi/topic/security.md), [Supply Chain](https://yomu.fyi/topic/supply-chain.md), [Threat Modeling](https://yomu.fyi/topic/threat-modeling.md)

A model that passes benchmarks can still defect only on a trigger. This explainer maps the trade-off between deeper backdoor verification and the friction, latency, and cost it adds.

### [How AWS CloudFormation Turns a Template Into a Reconciled Stack](https://yomu.fyi/visual-explainers/how-aws-cloudformation-turns-a-template-into-a-reconciled-stack.md)
- Type: How it works
- Tags: [AWS](https://yomu.fyi/topic/aws.md), [AWS CloudFormation](https://yomu.fyi/topic/cloudformation.md), [Configuration Management](https://yomu.fyi/topic/configuration-management.md), [Deployment](https://yomu.fyi/topic/deployment.md), [GitOps](https://yomu.fyi/topic/gitops.md), [YAML](https://yomu.fyi/topic/yaml.md)

CloudFormation is a declarative reconciler: you describe the target state in a template, and it provisions, updates, and reports on the stack that results. Here is the loop.

### [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.

### [How Coding Agents Get Grounded in Your Stack](https://yomu.fyi/visual-explainers/how-coding-agents-get-grounded-in-your-stack.md)
- Type: How it works
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Anthropic](https://yomu.fyi/topic/anthropic.md), [Claude Code](https://yomu.fyi/topic/claude-code.md), [MCP](https://yomu.fyi/topic/mcp.md), [Sandboxing](https://yomu.fyi/topic/sandboxing.md), [Tool Calling](https://yomu.fyi/topic/tool-calling.md)

A four-stage flow showing how a coding agent moves from a task to a reviewed change by grounding on verified skills, live system state, and code-first config before it acts.

### [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.

[Newer explainers](https://yomu.fyi/visual-explainers/page/2.md) · [Older explainers](https://yomu.fyi/visual-explainers/page/4.md)