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

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

## Visual Explainers

### [Authorization Is a Runtime Decision](https://yomu.fyi/visual-explainers/authorization-is-a-runtime-decision.md)
- Type: How it works
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Auditability](https://yomu.fyi/topic/auditability.md), [Authentication](https://yomu.fyi/topic/authentication.md), [Authorization](https://yomu.fyi/topic/authorization.md), [OAuth2](https://yomu.fyi/topic/oauth2.md)

See how an agent request becomes an allowed or denied tool action through identity context, policy checks, scoped credentials, and an auditable decision trail.

### [Anomaly Detection: From Baseline to Action](https://yomu.fyi/visual-explainers/anomaly-detection-from-baseline-to-action.md)
- Type: What is it?
- Tags: [Analytics](https://yomu.fyi/topic/analytics.md), [Anomaly Detection](https://yomu.fyi/topic/anomaly-detection.md), [Monitoring](https://yomu.fyi/topic/monitoring.md), [Observability](https://yomu.fyi/topic/observability.md), [Time Series](https://yomu.fyi/topic/time-series.md)

Anomaly detection identifies meaningful departures from expected behavior. This explainer shows how signals, baselines, context, and alert routing turn unusual measurements into engineer-ready findings.

### [Assist or Delegate? Choosing an AI Development Tool](https://yomu.fyi/visual-explainers/assist-or-delegate-choosing-an-ai-development-tool.md)
- Type: Comparison
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [AI Development Tools](https://yomu.fyi/topic/ai-development-tools.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md), [Model Evaluation](https://yomu.fyi/topic/model-evaluation.md), [Testing](https://yomu.fyi/topic/testing.md)

Compare assistive coding tools with agentic development environments to see where human control, automation, verification, and evaluation belong in the workflow.

### [When the Pipeline Pushes Back](https://yomu.fyi/visual-explainers/when-the-pipeline-pushes-back.md)
- Type: Trade-offs
- Tags: [Backpressure](https://yomu.fyi/topic/backpressure.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md), [Performance](https://yomu.fyi/topic/performance.md), [Rate Limiting](https://yomu.fyi/topic/rate-limiting.md), [Streaming](https://yomu.fyi/topic/streaming.md)

Backpressure is a feedback loop that slows work when downstream capacity or health deteriorates. Compare its gains, costs, and signals for choosing a control point.

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

### [Apache Camel: From Many App Signals to Governed Actions](https://yomu.fyi/visual-explainers/apache-camel-from-many-app-signals-to-governed-actions.md)
- Type: How it works
- Tags: [Apache Camel](https://yomu.fyi/topic/apache-camel.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Automation](https://yomu.fyi/topic/automation.md), [Observability](https://yomu.fyi/topic/observability.md)

Apache Camel is shown as the integration path that brings application actions into one request workflow. The diagram clarifies real-time versus scheduled ingestion, mapping, merging, authorization, and audit.

### [The Context Boundary: A Backstage Architecture for Safer Engineering Decisions](https://yomu.fyi/visual-explainers/the-context-boundary-a-backstage-architecture-for-safer-engineering-decisions.md)
- Type: Architecture
- Tags: [AI Governance](https://yomu.fyi/topic/ai-governance.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Backstage](https://yomu.fyi/topic/backstage.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md), [Documentation](https://yomu.fyi/topic/documentation.md)

Backstage can act as an engineering context boundary: catalog entities, templates, and TechDocs inform an agent before it proposes changes. See where validation and review fit.

### [How to Turn Airport Pickup Into a Reliability Loop](https://yomu.fyi/visual-explainers/how-to-turn-airport-pickup-into-a-reliability-loop.md)
- Type: How to
- Tags: [Airports](https://yomu.fyi/topic/airports.md), [Decision-Making](https://yomu.fyi/topic/decision-making.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md), [Observability](https://yomu.fyi/topic/observability.md)

A practical checklist for designing reliable airport pickups: map curb constraints, stage drivers, simplify matching, and measure each handoff so improvements target the real bottleneck.

### [How to Build a Governed Azure Data-to-Agent Workflow](https://yomu.fyi/visual-explainers/how-to-build-a-governed-azure-data-to-agent-workflow.md)
- Type: How to
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Azure](https://yomu.fyi/topic/azure.md), [Data Engineering](https://yomu.fyi/topic/data-engineering.md), [Data Governance](https://yomu.fyi/topic/data-governance.md)

A practical Azure workflow for turning fragmented operational data into governed analytics and agent experiences, with checkpoints for layering, context, access, and deployment.

### [Axum at the Trust Boundary: From Request to Protected Response](https://yomu.fyi/visual-explainers/axum-at-the-trust-boundary-from-request-to-protected-response.md)
- Type: How it works
- Tags: [API](https://yomu.fyi/topic/api.md), [Authentication](https://yomu.fyi/topic/authentication.md), [Axum](https://yomu.fyi/topic/axum.md), [OAuth 2.0](https://yomu.fyi/topic/oauth-2-0.md), [Rust](https://yomu.fyi/topic/rust.md)

Axum is a Rust web framework for composing routes, middleware, and extractors. This explainer shows how different login flows become verified identity before a handler responds.

### [Autoscaling Is a Control Loop, Not a Button](https://yomu.fyi/visual-explainers/autoscaling-is-a-control-loop-not-a-button.md)
- Type: Trade-offs
- Tags: [Autoscaling](https://yomu.fyi/topic/autoscaling.md), [Cost Optimization](https://yomu.fyi/topic/cost-optimization.md), [Kubernetes](https://yomu.fyi/topic/kubernetes.md), [Monitoring](https://yomu.fyi/topic/monitoring.md), [Scalability](https://yomu.fyi/topic/scalability.md)

Autoscaling trades responsiveness, stability, and cost: this explainer shows how signal choice, scaling direction, and capacity limits shape the right control loop for a workload.

### [The Token’s Route: From Auth0 Login to API Authorization](https://yomu.fyi/visual-explainers/the-token-s-route-from-auth0-login-to-api-authorization.md)
- Type: How it works
- Tags: [API](https://yomu.fyi/topic/api.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Auth0](https://yomu.fyi/topic/auth0.md), [Authentication](https://yomu.fyi/topic/authentication.md), [OAuth2](https://yomu.fyi/topic/oauth2.md), [OIDC](https://yomu.fyi/topic/oidc.md)

See how an Auth0 login becomes an API decision: redirect the user, issue the right token, validate its claims, and apply audience, scope, and access policies.

### [ABAC: When Data Context Becomes the Access Rule](https://yomu.fyi/visual-explainers/abac-when-data-context-becomes-the-access-rule.md)
- Type: What is it?
- Tags: [Attribute-Based Access Control](https://yomu.fyi/topic/attribute-based-access-control.md), [Auditability](https://yomu.fyi/topic/auditability.md), [Data Classification](https://yomu.fyi/topic/data-classification.md), [Data Governance](https://yomu.fyi/topic/data-governance.md)

Attribute-Based Access Control uses identity and data attributes to decide access. This explainer shows how governed tags become row filters or column masks across data engines.

### [How to Move Independent Work Through an asyncio Pipeline](https://yomu.fyi/visual-explainers/how-to-move-independent-work-through-an-asyncio-pipeline.md)
- Type: How to
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [asyncio](https://yomu.fyi/topic/asyncio.md), [Latency](https://yomu.fyi/topic/latency.md), [Parallelism](https://yomu.fyi/topic/parallelism.md), [Python](https://yomu.fyi/topic/python.md)

A practical asyncio workflow for moving independent work through typed events, queues, concurrent tasks, and awaited API calls. Learn where validation and fallback belong.

### [How to Make Apache Hudi Copy-On-Write Upserts Less Wasteful](https://yomu.fyi/visual-explainers/how-to-make-apache-hudi-copy-on-write-upserts-less-wasteful.md)
- Type: How to
- Tags: [Apache Hudi](https://yomu.fyi/topic/apache-hudi.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Data Engineering](https://yomu.fyi/topic/data-engineering.md), [Data Pipelines](https://yomu.fyi/topic/data-pipelines.md), [Parquet](https://yomu.fyi/topic/parquet.md)

Learn how Apache Hudi copy-on-write upserts can use row-level file and page locations to update changed data while avoiding unnecessary decompression and rewriting.

### [AssemblyScript: the TypeScript-shaped path into WebAssembly](https://yomu.fyi/visual-explainers/assemblyscript-the-typescript-shaped-path-into-webassembly.md)
- Type: What is it?
- Tags: [AssemblyScript](https://yomu.fyi/topic/assemblyscript.md), [Performance](https://yomu.fyi/topic/performance.md), [Sandboxing](https://yomu.fyi/topic/sandboxing.md), [TypeScript](https://yomu.fyi/topic/typescript.md), [WebAssembly](https://yomu.fyi/topic/webassembly.md)

AssemblyScript is a TypeScript-like way to target WebAssembly. This explainer shows how source becomes a sandboxed module, crosses explicit host boundaries, and fits performance-sensitive services.

### [How to Build an ASL Gloss Workflow That Keeps Context](https://yomu.fyi/visual-explainers/how-to-build-an-asl-gloss-workflow-that-keeps-context.md)
- Type: How to
- Tags: [Accessibility](https://yomu.fyi/topic/accessibility.md), [AI](https://yomu.fyi/topic/ai.md), [Architecture](https://yomu.fyi/topic/architecture.md), [ASL](https://yomu.fyi/topic/asl.md)

Learn a practical workflow for translating English discourse into ASL gloss while preserving spatial references, question-answer structure, and consistent concept-to-gloss mappings.

### [ARM Is a Stack Decision, Not a CPU Checkbox](https://yomu.fyi/visual-explainers/arm-is-a-stack-decision-not-a-cpu-checkbox.md)
- Type: Architecture
- Tags: [Architecture](https://yomu.fyi/topic/architecture.md), [ARM](https://yomu.fyi/topic/arm.md), [Cloud](https://yomu.fyi/topic/cloud.md), [Edge Computing](https://yomu.fyi/topic/edge-computing.md), [GPU](https://yomu.fyi/topic/gpu.md), [Performance](https://yomu.fyi/topic/performance.md)

An architecture view of ARM deployments, from workload fit and software support to platform choice, showing where performance, memory, storage, and operations shape the decision.

### [Apple Integration Is a Boundary, Not a Feature](https://yomu.fyi/visual-explainers/apple-integration-is-a-boundary-not-a-feature.md)
- Type: What is it?
- Tags: [Apple](https://yomu.fyi/topic/apple.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Authentication](https://yomu.fyi/topic/authentication.md), [iOS](https://yomu.fyi/topic/ios.md)

Apple integrations are boundary designs: native capability, server-side mapping, and trust checks must meet a platform-agnostic product layer. See where each responsibility belongs.

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