Core: Wireless
Requirement / business driver Authenticate and encrypt wireless access appropriately for enterprise, personal, and guest use - the air is an open medium. The options * WPA2 - AES-CCMP (avoid legacy TKIP); WPA2-Enterprise uses 802.1X/EAP (AAA and identity - RADIUS, TACACS+, 802.1X), WPA2-Personal uses a pre-shared key. * WPA3
Core: Automation
In one line Automation's real value isn't speed - it's consistency at scale and the elimination of drift, which is an operating-model change, not a tool. Why automate * Consistency - the same intent rendered identically everywhere (no snowflakes). * Scale & speed - change hundreds of devices
Core: Automation
Requirement / business driver Bring devices online at scale without a technician on the CLI - Day-0 onboarding that's fast, consistent, and secure. How ZTP works A factory-default device boots, gets an address (DHCP), and is pointed at a config/image source - then pulls and applies its Day-
Core: Automation
Requirement / business driver Manage network configuration the way software is managed - versioned, reviewed, tested, and reproducible - so changes are safe and the network never drifts from intent. The principles * Source of truth in Git - the repo defines desired state; devices are reconciled to it (not the other way round). * Declarative
Core: Automation
Requirement / business driver Pick the right tool for the job - the blueprint's emphasis is when to use each, not how to code them. Options * Ansible - agentless config management; idempotent modules push config/state to existing devices. * Terraform - declarative provisioning with a state file; stands up infrastructure/cloud resources
Core: Automation
Requirement / business driver Deliver network changes through a pipeline - validated, tested, staged, and reversible - instead of ad-hoc CLI pushes. Pipeline stages On a commit to the source of truth (Infrastructure as Code - declarative, idempotent, source of truth), a CI/CD platform (Jenkins, GitLab CI, GitHub Actions) runs: 1. Lint
Core: Automation
Requirement / business driver Move from open-loop "push config" to closed-loop: the network observes itself and acts - the bridge from automation to assurance. The loop Streaming telemetry (Network management - traditional vs model-driven) feeds analytics that detect a condition, decide a response, and act (push a change)
Study ops
Every line of the Core Technology List, the AI Infrastructure Technology List, and the Learning Matrix v1.1 AI-sheet deltas, mapped to the note(s) that own it. This is the honest answer to "is the vault blueprint-complete?" - updated whenever a gap closes. See also Glossary.
Study ops
The companion to the Scenario intake checklist: that note runs one scenario; this one runs the whole 8-hour day and gives the reusable thinking pattern for every question. The day arc (8 hours, four 2-hour scenarios) * First three scenarios = Core; the fourth = your elective (AI Infrastructure). Each is
Study ops
A fixed routine for each of the four scenarios. Independent scenarios - reset your mind; carry nothing over. No backward navigation, so decide and commit. First ~10 minutes - read and capture (don't answer yet) * Read all background + topology before answering anything. * Capture requirements and constraints in four buckets as
Templates
In one line How it works Why it matters for design Related * [[ ]] Spaced repetition Question Answer [...] fact. Cloze fact. Sources - domain: # Core | AI-Infra · blueprint-ref: # e.g. AI-Infra 2.1 Lossless fabrics · type: concept · status: stub # stub | draft | complete · tags:
Templates
Requirement / business driver Constraints * Technical: * Operational: * Application: * Business / cost: * Regulatory / sovereignty: * Dual-stack (IPv4 + IPv6): Options * A - <one line> * B - <one line> * C - <one line> Comparison ![[<matrix-file>.png]] Tradeoffs * A - when it wins / watch-outs. * B - when it wins / watch-outs.