Pod Alpha
Official NQF WIL Credential Issued • SD-WIL-2026-SPECIMEN
Your signed WIL Certificate & Academic Rubric Transcript (SD-TR-2026-SPECIMEN) are ready for download.
DAY 19 / 19 Phase 4: Automated Testing, Docker & Final Defense RES-CORE • Core Residence & Maintenance API Foundation +150 XP Deliverable

Final Presentation, Oral Code Defense & Official WIL Certification

Deliver your 15-minute live technical walkthrough and oral code defense before the Sputnik Devs Engineering Board and claim your cryptographically signed WIL Certificate & Transcript.

Engineering Implementation Tasks

Branch: feat/day-19
01

Complete your Day 19 logbook summary and final self-reflection in `docs/DAILY_CADENCE_AND_LOGBOOK.md`.

02

Walk through your merged Pull Requests, Swagger endpoints, and test suite.

03

Complete the 4-Pillar Oral Code Defense with your Pod Coordinator.

04

Download your stamped University WIL Logbook PDF and Official Verifiable Certificate.

05

Core Sandbox Scope (RES-CORE — Final Capstone Defense): Finalize 'docs/DAILY_CADENCE_AND_LOGBOOK.md' and walk through your merged PRs, Swagger endpoints, Dockerfile, and 'SputnikResidence.Tests' suite.

Assigned Feature Sub-Module • RES-CORE Zero-Collision Scope
Core Residence & Maintenance API Foundation

Core student accommodation occupancy, room capacity guardrails, maintenance ticket lifecycle, comment workflows, xUnit verification, and Docker production readiness.

Directory: SputnikDevs.Residence.SandboxApi & SputnikResidence.Tests
Entities: Room, Student, MaintenanceTicket, TicketComment
Targets: SputnikDevs.Residence.SandboxApi, SputnikResidence.Tests & docs/DAILY_CADENCE_AND_LOGBOOK.md
PR Branch: feat/day-19 (main stays clean)
Required Pull Request Deliverable

Final PR merged, 152 Notional Hours verified, and Official WIL Certificate & Academic Transcript issued.

Core Standup Defense Concepts 4 Focus Areas
End-to-End Request Lifecycle Defense Architecture Trade-Offs & Scalability Test Pyramid (Unit vs Integration) Production Readiness & NQF Sign-Off
1. Fork Upstream to Personal GitHub →
⚠️ Avoid GitHub Org Billing Blocks: Always Fork the repo to your personal GitHub account first, then create your 2-core Codespace on YOUR PERSONAL FORK (never on Sputnik-Devs-Pty-Ltd) so it runs 100% free on your 120 personal core-hours/month quota.
Active Engineering Accommodation • Fork-First Personal Codespace Protocol

☁️ Cloud Devcontainer Active (4GB RAM Laptop → GitHub Codespaces 16GB Cloud VM) • ⚡ Async Defense Window Enabled

Zero Hardware & Zero Billing Rule: Always launch your 2-core Codespace on your personal fork (github.com/<your-username>/sputnikdevs-residence-sandbox)—never on the Sputnik-Devs-Pty-Ltd org repo—so it runs 100% on your free 120 personal core-hours/month without local 4GB RAM strain or Organization billing blocks.

Specimen Testing Sandbox • SD-PORTAL-SPECIMEN

Live End-to-End Test Mode (GitHub PR Auto-Sync + 3-Min Spoken/Written Code Defense)

Use this Specimen account to test Step 1 (Auto-Sync PR from GitHub) and Step 2 (3-Minute Timed Voice/Written Code Defense) without touching Brian Mkandla's live cohort profile.

Step 1 • Gate 1 & Gate 2 GitHub PR Auto-Sync 8 WIL Hours + 150 XP upon Dual Verification

Sync & Log Day 19 Pull Request from GitHub

Already pushed your code and opened a Pull Request on GitHub? Click Auto-Sync Latest PR from GitHub to pull your PR link, changed files, commit summary, and next sprint milestone automatically—no double typing required.

Submitting syncs your GitHub PR diff and generates your 4 diff-specific questions in Step 2 below for your asynchronous 3-Minute Timed Code Defense.

Step 2 • Gate 3 Asynchronous PR Authorship Defense (Day 19) 📷 Live Webcam Proctored (3 Keyframes) 🎙️ Spoken Voice OR ⌨️ Written • No Live Call Needed PR #12 • 3 files changed (+116/-1) • GlobalExceptionMiddleware.cs, Program.cs, MaintenanceExceptionTests.cs

3-Minute Timed & Webcam-Proctored Technical Code Defense

Your camera opens in a lightweight Picture-in-Picture window while you defend your Day 19 Pull Request diff by speaking into your microphone (🎙️ Speak Answer) or typing in your own words. Three low-bandwidth verification snapshots (~15KB each at Start, Mid-Defense, and Final Submit), clipboard-paste blocks, and tab switches are logged for Kenneth Takudzwa Katsande & Takudzwa Mupanesure (@Takudzwamz).

✓ Webcam-Proctored Defense Verified
38 / 100
Logged 28 Oct 12:48 UTC • 92s
Pod Director & Principal Architect Review Posted (Kenneth Takudzwa Katsande & @Takudzwamz): Kenneth Takudzwa Katsande and Takudzwa Mupanesure have posted line-level architectural feedback on your Day 19 Pull Request.
View Review on GitHub →
Defense & Proctoring Telemetry Summary: Pre-Standup Defense Score: 38/100 in 92s • 📷 Webcam Proctored (3/3 Keyframe Snapshots Verified, 0 Camera Drops) • Clean Telemetry (0 tab switches, 0 paste attempts). Strongest on implementation flow; probe Q2 (SputnikDevs.Residence.SandboxApi/Controllers/TicketsController.cs) live during standup.
📷 WEBCAM PROCTORING FILMSTRIP VERIFIED (3/3 KEYFRAME SNAPSHOTS LOGGED IN DOSSIER) 240x180 • Low-Bandwidth JPEG/SVG
Frame 1 • T+02s Q1 Start
Frame 1 • T+02s Q1 Start
SputnikDevs.Residence.SandboxApi/Controllers/TicketsController.cs
✓ Presence Verified
Frame 2 • Mid-Defense Trace
Frame 2 • Mid-Defense Trace
SputnikDevs.Residence.SandboxApi/Controllers/TicketsController.cs
✓ Presence Verified
Frame 3 • T+92s Final Submit
Frame 3 • T+92s Final Submit
SputnikDevs.Residence.SandboxApi/Controllers/TicketsController.cs
✓ Presence Verified
Optional Warm-Up • 60-Second Self-Audit Drill Deck

Interactive Code Architecture Self-Audit Simulator

Use this optional 60-second practice deck while writing your code to make sure you can trace your execution path, edge cases, and architectural trade-offs before starting your 3-Minute Timed Code Defense above.

Standup Readiness
PROBE 01 • DAY 19 ARCHITECTURE & CONCEPT DEEP-DIVE
Full Residence Sandbox Solution (API + EF Core + xUnit Suite) +75 Practice XP

Core Concept Drill: Final Presentation, Oral Code Defense & Official WIL Certification

Walk us through the complete lifecycle of a `POST /api/v1/tickets/{id}/comments` request in your API from HTTP request to PostgreSQL persistence.

Day 19 Reference Code / Architecture Context
Client Request -> CORS & ModelState Pipeline (Program.cs)
  -> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
  -> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
  -> Automated Unit & Integration Verification (SputnikResidence.Tests)
Coordinator Evaluation Criterion Speak or write your explanation in your own words first, then click 'Reveal Senior Architect Answer Key' below to compare your technical reasoning.
Senior Architect Reference Answer (What We Listen For):Kestrel receives HTTP POST -> Routing matches `TicketsController.AddComment` -> JSON body binds to `AddTicketCommentRequest` -> Controller validates ticket existence, `Closed` status, `AuthorName`, `AuthorRole` whitelist, and `Content` length -> `TicketComment` entity added to `_context.TicketComments` -> `SaveChangesAsync()` executes SQL `INSERT` via Npgsql -> `201 Created` returns `TicketCommentDto`.
PROBE 02 • DAY 19 DESIGN RATIONALE & EDGE CASES
Full Residence Sandbox Solution (API + EF Core + xUnit Suite) +90 Practice XP

Why This Pattern Matters in Production

What was the most important engineering lesson you learned moving from university coursework to daily PR-reviewed software engineering?

Day 19 Reference Code / Architecture Context
Client Request -> CORS & ModelState Pipeline (Program.cs)
  -> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
  -> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
  -> Automated Unit & Integration Verification (SputnikResidence.Tests)
Coordinator Evaluation Criterion Mentors listen for concrete cause-and-effect reasoning (what breaks in PostgreSQL, HTTP serialization, or test runners if this pattern is skipped).
Senior Architect Reference Answer (What We Listen For):Candidate reflects on incremental PR feedback, defensive input validation (`Enum.IsDefined`, capacity guardrails), database migrations, and writing maintainable code for a team.
PROBE 03 • DAY 19 LIVE EXTENSION & 'WHAT-IF' SCENARIO
Full Residence Sandbox Solution (API + EF Core + xUnit Suite) +100 Practice XP

Live Requirement Change & Refactoring Drill

In your Final Exit Defense, if we ask you to compare how you validated and persisted data on Day 03 (Domain Models) vs Day 12 (Comments & Roles) vs Day 16 (Integration Tests), how do the layers work together to prevent invalid state from ever reaching PostgreSQL?

Day 19 Reference Code / Architecture Context
Client Request -> CORS & ModelState Pipeline (Program.cs)
  -> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
  -> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
  -> Automated Unit & Integration Verification (SputnikResidence.Tests)
Coordinator Evaluation Criterion In real engineering reviews, we test authorship by asking how you would extend your code for a new requirement. Point to the exact class and method you would touch.
Senior Architect Reference Answer (What We Listen For):Defense-in-depth across three layers: 1. **Domain & DTO Layer:** Data annotations (`[Required]`, `[MaxLength]`), computed invariants (`Room.AvailableSpots` clamped with `Math.Max(0, ...)`), and `MaintenanceTicket.IsClosedOrResolved`. 2. **Controller & Pipeline Layer:** `InvalidModelStateResponseFactory` in `Program.cs`, `Enum.IsDefined` guardrails, canonical `AllowedRoles` normalization, and business-rule checks (blocking comments on closed tickets, checking room capacity before assigning a student). 3. **Persistence & Automated Tests:** EF Core Fluent API constraints (`HasMaxLength`, foreign keys) backed by fast xUnit unit + isolated In-Memory integration tests.
PROBE 04 • DAY 19 VERIFICATION & FAILURE-PATH PROOF
Full Residence Sandbox Solution (API + EF Core + xUnit Suite) +80 Practice XP

Proving Happy Path & Negative/Boundary Cases

If you were onboarding the next cohort of WIL engineers onto `sputnikdevs-residence-sandbox` tomorrow, which single piece of code or test in your repository would you show them first as the gold standard, and why?

Day 19 Reference Code / Architecture Context
Client Request -> CORS & ModelState Pipeline (Program.cs)
  -> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
  -> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
  -> Automated Unit & Integration Verification (SputnikResidence.Tests)
Coordinator Evaluation Criterion Always verify both the happy path and the failure/boundary path before opening your Pull Request.
Senior Architect Reference Answer (What We Listen For):Point to a specific endpoint and its matching test (for example, `POST /api/v1/tickets/{id}/comments` or `GET /api/v1/tickets/summary` alongside `RoomTests` / `MaintenanceTicketTests` / `TicketsControllerIntegrationTests`), walk through how the endpoint validates edge cases cleanly, uses `.AsNoTracking()` for read queries, returns consistent `{ message }` errors, and is locked down by automated xUnit tests.
60s
60-Second Spoken Code Defense Drill
Practice explaining your PR out loud before starting the 3-Minute Defense.
Pre-Defense Authorship Self-Audit

Check off each verification gate below as you inspect your own Pull Request diff:

Pillar 01 • 40% Weight
Code Quality & Architecture
3.8 / 4.0
Pillar 02 • 30% Weight
Oral Standup Code Defense
3.7 / 4.0
Pillar 03 • 15% Weight
Git Discipline & Peer Review
3.9 / 4.0
Pillar 04 • 15% Weight
Standup & Delivery Cadence
3.8 / 4.0
Institutional WIL Evidence Ledger

Verified Pull Request & Standup Logbook (6 Entries)

Download Official Logbook PDF
D19 28 Oct 2026
Dual-Verified ✓✓

Benchmarked materialized views (v_nsfas_arrears_aging) and composite B-Tree indexes with EXPLAIN ANALYZE.

Peer Reviewer
Kenneth Takudzwa Katsande & Takudzwa Mupanesure
Defense Score
4.0 / 4.0
Hours Credited
8 h
D19 20 Oct 2026
Dual-Verified ✓✓

Completed Docker multi-stage Dockerfile, health checks, and 84% xUnit code coverage.

Peer Reviewer
Kenneth Takudzwa Katsande & Takudzwa Mupanesure
Defense Score
4.0 / 4.0
Hours Credited
8 h
D10 13 Oct 2026
Dual-Verified ✓✓

Passed Day 9 Mid-Sprint Architecture Review and added X-Execution-Time-Ms telemetry.

Peer Reviewer
Sipho Mokoena
Defense Score
4.0 / 4.0
Hours Credited
8 h
D05 06 Oct 2026
Dual-Verified ✓✓

Optimized GET /api/residents with AsNoTracking() and pagination metadata.

Peer Reviewer
Brian Ndlovu
Defense Score
4.0 / 4.0
Hours Credited
8 h
D02 03 Oct 2026
Dual-Verified ✓✓

Merged PR #1 with green CI build and verified PostgreSQL 16 container health checks.

Peer Reviewer
Lerato Dlamini
Defense Score
4.0 / 4.0
Hours Credited
8 h
D01 02 Oct 2026
Dual-Verified ✓✓

Completed onboarding orientation, configured GitHub Codespaces & Docker PostgreSQL 16 sandbox.

Peer Reviewer
Sipho Mokoena
Defense Score
4.0 / 4.0
Hours Credited
8 h
Student Welfare & Cloud Engineering Support

🛠️ Hardware, Connectivity & Hardship Log (Zero-Barrier WIL)

Working on a 4GB RAM laptop, experiencing Eskom loadshedding, or facing mobile data constraints? Log it below and we immediately provision a cloud or async engineering workaround (such as a 16GB RAM GitHub Codespaces Cloud Devcontainer) so your sprint never stops.

☁️ Open Cloud Codespace
Log a Device / Environment Constraint Instant Cloud Workaround
Your Recorded Accommodations (2) Pod Director Monitored
✓ Accommodation Active 13 Oct 2026 • HS-SPEC-01
Hardware Constraint (RAM / CPU) — 4GB RAM Windows 10 Laptop (Intel Celeron, 128GB eMMC)

Reported Issue: Local Visual Studio & Docker Desktop freeze when running .NET 10 SDK alongside PostgreSQL 16 container on 4GB RAM.

☁️ Engineering Solution Provisioned (Kenneth Takudzwa Katsande & Takudzwa Mupanesure): Provisioned GitHub Codespaces Cloud Devcontainer (4-Core / 16GB RAM remote environment) on sputnikdevs-residence-sandbox. Student develops via browser/VS Code Remote with zero local memory strain.
✓ Accommodation Active 20 Oct 2026 • HS-SPEC-02
Power / Loadshedding & Connectivity — Eskom Stage 4 (08:00–10:30 SAST Slot) + Mobile LTE Hotspot

Reported Issue: Scheduled power outage during morning 09:00 SAST window; inverter battery lasts 90 minutes.

☁️ Engineering Solution Provisioned (Kenneth Takudzwa Katsande): Enabled Asynchronous GitHub PR Auto-Sync + On-Demand 3-Minute Timed Code Defense (Voice or Written) so student can defend and unlock next sprint day outside loadshedding windows.
Sputnik Devs Studio Sputnik Devs Studio (Pty) Ltd • CIPC Reg: 2026/449455/07 • SARS Tax Ref: 9896479194
292 Surrey Ave, Ferndale, Randburg, Johannesburg, 2194