Week 103 — Capstone planning

Capstone, portfolio, and interview readiness · Read / diagram

Hard

Phase 10 — Capstone, portfolio, and interview readiness

Overview

Requirements, architecture, eval plan

Mode this week: read_diagram. Match the work to that mode (operating model): implement ships running code; read/diagram ships a doc; deploy/benchmark ships a measured run. Personal dates, checkboxes, and the RPG layer stay in a learner journal.

Core deliverable

Capstone design doc

Optional depth

Add a production-shaped benchmark, cost or safety analysis, and an architecture trade-off note.

Week loop (from the cookiecutter journal)

Mon — Theory: Requirements, architecture, eval plan
Tue — Build: start the core deliverable above
Wed — Systems / papers: one paper or system note (see below if this week has assigned reading)
Thu — Eval / interview: write the four evidence items
Fri — Algorithmic Forge: Capstone 1 required; Capstone 2 optional at Week 108 (2-3 hr; Boss fights)

Forge theme: Mo's algorithm, capstone integration, tree forensics

Leetcode Darbar (parallel)

This week's band (103-108): Mixed timed sets and mock interviews. Production connection: Mo's traces, Euler/DSU boss, portfolio defense.

Standard: one aligned problem. Auror: the five-slot queue on the Darbar page. Tracker stays in the learner journal.

Topics: Darbar catalog

Find Target Indices After Sorting Array · easy · array
Count Negative Numbers In A Sorted Matrix · easy · array
The K Weakest Rows In A Matrix · easy · array
Search Insert Position · easy · array
Check If N And Its Double Exist · easy · array
Decode Xored Array · easy · array

Evidence contract

Every core week records all four (cookiecutter journal/weeks/week_103.md):

Code / implementation (or the design artifact on a writing week)
Benchmark / result
Design doc / technical explanation
Retrospective / learning note (Sailboat: destination, wind, anchor, rocks, heading)

On this site

Official Tensor-to-Tenant

Week 103 of Tensor-to-Tenant · Previous week · Next week.