Wayfinder map: Chapter 11 App-Dev Bootcamp — specs decision-complete

[HexSleeves]

Destination

Every Chapter 11 spec is decision-complete: spec 00 v2.0 encodes the 2026-07-23 meeting decisions, and child specs 03 (Databases), 04 (REST API), 05 (Auth), 06 (Debugging & Observability), 07 (Production/Digital Clone) plus a new standalone infrastructure spec (Terraform/AWS one-command environment) each have questions answered, spec written, and tasks listed — so building the remaining content is purely mechanical execution.

Notes

• Domain: six-month, open-source, framework-agnostic app-dev bootcamp for college seniors with no prior exposure; each section uses a different language to highlight one core principle; generous time estimates in front-matter.
• Founding decisions (2026-07-23 meeting): committed Terraform in-repo for AWS provisioning (no GitHub Actions coupling — "deploy in your own AWS account"); OTel Demo App as the production platform; everything self-contained under examples/ (cd + make).
• Decider: Jacob (@HexSleeves) resolves decision tickets; Joshua (@jburns24) reviews via spec PRs.
• Process: Liatrio SDD workflow (docs/specs/, questions → spec → tasks); use docs/specs/01-spec-design-patterns-section/ as the structural template. Consult the sdd skill when writing specs.
• Existing state: specs 00–03 live on master; spec 04 round-1 questions on add-specs-for-app-dev; sections through 11.3 are in open PRs Add Business Logic Patterns documentation and TypeScript examples (11.2.3) #822/Add Classical Gang of Four Patterns documentation and multi-language examples #824/Add Task 4.0: Integrated Refactoring Exercise (11.2.5) #826/Add 11.3 System Thinking section (spec 02) #914.

Decisions so far

• Research: OTel Demo AWS deployment options — single EC2 VM + official Docker Compose via thin committed Terraform (~$1/day, clean terraform destroy); single-node k3s as fallback if pod-level blue-green is needed; EKS and ECS/Fargate ruled out (control-plane cost, orphaned ELBs, retired compose→ECS tooling)

• Write spec 03 (Databases) tasks file — tasks file written (PR docs: add spec 03 (Databases) tasks file #927): 8 task groups from SQL fundamentals through Repository pattern, N+1/indexes, NoSQL, integration exercise, quiz, sidebar/front-matter

• Write spec 00 v2.0 — encode 2026-07-23 meeting decisions — spec 00 v2.0 written (PR docs: spec 00 v2.0 — six-month timeline, AWS/Terraform infra, meeting decisions (2026-07-23) #928): six-month timeline + generous estimates, AWS via committed Terraform (EC2+Compose direction), framework-agnostic/language-per-section + open-source design decisions, new standalone Spec 08 (infra) consumed by 06-07, status table corrected

• Validate OTel Demo locally on Apple Silicon — WORKS on ARM (2.1.3, OrbStack): ~3.5GB RAM steady-state, <1min warm startup, 26 containers; 4 required workarounds documented in otel-demo-setup README (commit 460d21b on PR Add 11.3 System Thinking section (spec 02) #914). Unblocks the infra-spec ticket.

Not yet specified

• Assessment strategy across the six months (per-section quizzes exist; capstone/e2e assessment unclear)
• Shared dev/prod cohort environment policy vs everyone-deploys-their-own
• AWS cost guidance/ceilings for learners running the stack in their own accounts
• CI improvements for front-matter checking (meeting: "could be improved")

Out of scope

• Building/merging section content — handled by the execution pipeline (PRs Add Business Logic Patterns documentation and TypeScript examples (11.2.3) #822/Add Classical Gang of Four Patterns documentation and multi-language examples #824/Add Task 4.0: Integrated Refactoring Exercise (11.2.5) #826/Add 11.3 System Thinking section (spec 02) #914 and successors), including the generous-time-estimate sweep on open PRs
• Keep-vs-regenerate for existing Copilot PRs — already resolved: keep (cleaned, tested, integrated)
• Trimming outdated non-chapter-11 content (Packer, Vagrant) — separate effort informed by duration data later