PI Architecture EXPLAINED | Agent Loop, Tools, TUI and More

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: PI Architecture EXPLAINED | Agent Loop, Tools, TUI and More
- URL: https://www.youtube.com/watch?v=gTeujlv8qK0
- Topic: Interfaces + Open Design
- My current learning frame: Sketch your own minimal coding agent by re-implementing Pi's loop on paper — context init, compaction check, LLM call, tool loop — and decide which tools you'd expose and which you'd disable for a read-only automation mode.
- Why this matters: New playlist item from Alejandro AO; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:14 / Evidence 1: "world by storm and it's actually very minimalist and it's very beautifully architected and designed. So, we're going to be taking a look at how it works actually so that you can think about probably creating your own."
- 1:55 / Evidence 2: "the first time and send the first message, is it's going to initialize its context. Okay? Now, what does this mean? This means that it's going to put together a bunch of different things. First, it's going to..."
- 19:42 / Evidence 3: "beware that these packages are naturally loading and executing code in your system, so you probably don't want to install packages from third-party sources that you do not trust. Uh, or if you uh want to use them,..."
- 27:14 / Evidence 4: "actually not only very minimalist, but also very simple and very intuitive. So, I have seen some agents, for example, uh try to measure how long your context is by taking the number of characters in the entire..."
- 30:38 / Evidence 5: "show you the actual compaction prompt. And here we are. We are inside packages agent source harness compaction and inside compaction still TS. And as you can see here we have the summarization system prompt. It says, let..."
- 34:18 / Evidence 6: "skills are managed. So, remember we mentioned before in the system prompt that here there is a section with all the skills available, and that is, of course, the first part of the skills workflow. So, in the..."
- 36:37 / Evidence 7: "uh agent skills. It can be, for example, located in {dot} agents {slash} skills. And this can be either in the current working directory or in your home directory. And this is going to be very important because..."

Video-aware target:
- Prompt lane: Agent harness
- Mechanism to extract: Identify what surrounding harness makes the model more useful than chat alone.
- Artifact to produce: A one-page agent harness map with tool boundaries, state ownership, and proof signals.
- Artifact must include: model role; tools; state/memory; permission boundary; verification proof

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Identify what surrounding harness makes the model more useful than chat alone. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page agent harness map with tool boundaries, state ownership, and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: User intent -> Model role -> Tool surface -> State and memory -> Verification loop -> Reusable operating rule
   - answers to these source questions: What does the video claim the agent can do? | What surrounding system makes that claim plausible? | What proof is shown instead of merely asserted?
   - 3 concrete examples that apply the video idea to real agentic work, such as a repo-editing harness; a local research assistant; a recurring refresh agent
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: treating model choice as architecture; ignoring tool permissions; missing verification evidence
   - a checklist for the next real workflow, focused on: tool boundaries, state ownership, done signal, recovery path
   - one practical exercise with a clear done signal: Map one current coding workflow as a harness and mark the first missing proof signal.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "PI Architecture EXPLAINED | Agent Loop, Tools, TUI and More", not a generic Interfaces + Open Design essay.
- Tie each harness element to a transcript anchor that names a tool, state boundary, permission, model behavior, or verification step.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic agent definitions; model leaderboard claims; tool list without operating boundaries.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.