Deep-Dive DD-01 — Pi: The Minimal Baseline

Pi: The Minimal Baseline

What you get with 4 tools and a <1,000-token system prompt. Pi is the reference thin harness — every other deep-dive in the curriculum compares against it.

minutes

artifacts

25/60

rubric score

Pi is not a toy — it is a deliberate architectural statement: do as little as possible in the harness; let the model do the work. The model is the 1.6%; Pi is the 98.4% shrunk as small as it can go before it stops being a harness at all. ~80-line loop, 4 tools, <1k prompt, trust-the-model. The thinness IS the design, and every absent component is a conscious tradeoff for legibility and co-evolution.

Load-Bearing Claims

Pi is the base architecture every course builds on

Pi is the base architecture every course in this curriculum builds on. Course 2A builds security tools FOR it (the sandbox, scope, approval gate it omits). Course 2B ATTACKS it (the OWASP ASI offensive procedures find its trust-the-model posture by default). Course 3 drops fine-tuned models INTO its unchanged loop. Course 4 DEPLOYS it at scale. Understand Pi and you understand the irreducible core every thicker harness varies on.

Pi's thin-harness design is correct for its use case, not a deficiency. The 25/60 rubric score is the expected result for a deliberate thin harness — the rubric scores production-readiness across all dimensions, and Pi is deliberately not that. The score reflects what Pi IS NOT (the deliberate omissions), not a failure of what Pi IS (the irreducible core).

The correct fork adds infrastructure, not cleverness. The three 'minimal production' changes (token budget, per-turn observability, basic compaction) close scored gaps WITHOUT adding model-specific logic (so the future-proof test still passes) and WITHOUT changing the threat model (so thinness is preserved). 'Just add a sandbox' changes the threat model without the supporting layer — the cost without the benefit.

After This Deep-Dive

Apply the 6-phase deep-dive methodology (Module 0.3) to Pi and produce a scored analysis card with file:line evidence.

Defend Pi's thin-harness design as correct for its use case, not as a deficiency — the load-bearing distinction the rest of the curriculum depends on.

Score Pi on the 12-module rubric (/60) with evidence, and explain why a low absolute score is the expected result for a deliberate thin harness, not a failure.

Write the Architect's Verdict and MLSecOps Relevance note for Pi in the canonical template.

Use Pi as the benchmark for every subsequent deep-dive — every other harness is measured against Pi's minimalism: 'how much thickness does X add, and why?'

Articulate the three decisions Pi makes that every thicker harness should justify deviating from (the 4-tool set, the dumb-loop philosophy, the ultra-thin prompt).

Artifacts

Teaching Document

~2,800 words; the full 6-phase analysis (first contact, architecture map, 12-module audit, security audit, benchmark, score & synthesis) plus the curriculum-threading note, anti-patterns, key terms, references

READ

Diagrams

5 Mermaid diagrams — Pi's architecture (the three jobs minimal), Pi's position on the thickness spectrum, the ReAct loop control flow, the 12-module rubric score, how the curriculum threads through Pi

READ

Slide Deck

12 slides — reveal.js, dark theme, design-system teal; covers the thesis (Pi as base architecture), the three-jobs architecture, the 12-module audit table, three agreed/different decisions, the security audit, the curriculum threading, anti-patterns, the lab

READ

Teaching Script

Verbatim teaching transcript with [SLIDE N] cues, ~2,800 words spoken at ~140 wpm across 10 slide cues