/ Go Engineering / Phase 11 Phase 11 Days 51-55
Final Capstone — Disaster Relief Supply Network The resume project: needs, depots, inventory, allocation, dispatch, field delivery, and production operations
Phase Goal Integrate the entire course into a production-shaped relief-logistics backend that proves allocation correctness, security, reliability, and system design.
Day 51: Capstone Architecture & Relief Domain
Requirements, responders, coordinators, auditors, boundaries, and non-goals Define Requirements, responders, coordinators, auditors, boundaries, and non-goals in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Requirements, responders, coordinators, auditors, boundaries, and non-goals is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Requirements, responders, coordinators, auditors, boundaries, and non-goals and fix it deliberately
Depots, supply lots, needs, allocations, dispatches, deliveries, and adjustments Define Depots, supply lots, needs, allocations, dispatches, deliveries, and adjustments in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Depots, supply lots, needs, allocations, dispatches, deliveries, and adjustments is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Depots, supply lots, needs, allocations, dispatches, deliveries, and adjustments and fix it deliberately
API contracts and lifecycle state machines
Threat model, inventory invariants, and architecture decision records
Day 52: Needs, Depots & Inventory Ledger
Regional need intake and indexed priority queries
Depot, supply-lot, expiry, and inventory-ledger management Define Depot, supply-lot, expiry, and inventory-ledger management in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Depot, supply-lot, expiry, and inventory-ledger management is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Depot, supply-lot, expiry, and inventory-ledger management and fix it deliberately
Read projections versus authoritative ledger entries
Coordinator authorization and append-only audit events
Day 53: Allocation, Dispatch & Reliable Workflow
Atomic multi-lot allocation without negative stock
Idempotent dispatch and delivery commands
Carrier boundary and delayed field-update reconciliation
Outbox events and notification workflow
Day 54: Reliability, Security & Operations
Rate limits, sessions, input boundaries, and abuse cases Define Rate limits, sessions, input boundaries, and abuse cases in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Rate limits, sessions, input boundaries, and abuse cases is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Rate limits, sessions, input boundaries, and abuse cases and fix it deliberately
Unit, integration, race, fuzz, and load tests Define Unit, integration, race, fuzz, and load tests in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Unit, integration, race, fuzz, and load tests is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Unit, integration, race, fuzz, and load tests and fix it deliberately
Metrics, traces, logs, SLOs, and alerts Define Metrics, traces, logs, SLOs, and alerts in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Metrics, traces, logs, SLOs, and alerts is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Metrics, traces, logs, SLOs, and alerts and fix it deliberately
Docker Compose, CI, migrations, backup, and rollback Define Docker Compose, CI, migrations, backup, and rollback in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Docker Compose, CI, migrations, backup, and rollback is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Docker Compose, CI, migrations, backup, and rollback and fix it deliberately
Day 55: Final Project — Ship the Relief Supply Network
End-to-end need-to-delivery demonstration
Concurrent allocation proof and dependency failure injection
Deployment, recovery runbook, architecture diagram, and API docs Define Deployment, recovery runbook, architecture diagram, and API docs in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Deployment, recovery runbook, architecture diagram, and API docs is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Deployment, recovery runbook, architecture diagram, and API docs and fix it deliberately
Project requirements, constraints & review Define Resume bullets, demo video, trade-off narrative, and retrospective in plain language and explain the problem it solves Trace what the Go compiler or runtime does when Resume bullets, demo video, trade-off narrative, and retrospective is used Write a tiny example, then apply it to a realistic backend task Diagnose the beginner failure mode for Resume bullets, demo video, trade-off narrative, and retrospective and fix it deliberately
Disaster Relief Supply Network — DEPLOYED Build and deploy a production-shaped Go backend that accepts verified needs, manages depot ledgers, allocates expiring supply lots, dispatches shipments, reconciles delayed field updates, and supports audited corrections.
After this phase, you'll be able to:
Requirements, responders, coordinators, auditors, boundaries, and non-goals Depots, supply lots, needs, allocations, dispatches, deliveries, and adjustments API contracts and lifecycle state machines Threat model, inventory invariants, and architecture decision records Regional need intake and indexed priority queries Depot, supply-lot, expiry, and inventory-ledger management Read projections versus authoritative ledger entries Coordinator authorization and append-only audit events You can apply Phase 11 skills in a finished, explainable Go project.