Google OKF + MCP : Explained The New "AI Context Stack"

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

Source video:
- Title: Google OKF + MCP : Explained The New "AI Context Stack"
- URL: https://www.youtube.com/watch?v=bwQ70NMd57k
- Topic: Creative Automation
- My current learning frame: Pick one metric your team argues about, write its OKF concept file with the definition, join path, and resource URI, then connect an MCP server to the warehouse and verify the agent answers correctly by reading the file first and querying live second.
- Why this matters: New playlist item from Cloud Codes; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:14 / Evidence 1: "context is really two different things. What the model knows and what it can reach. In the last year, two open standards quietly showed up to fix exactly that. One is called OKF. The other is called MCP."
- 1:53 / Evidence 2: "an access gap. Even when it does understand, it cannot actually touch anything. Two different problems and for years we solved them badly. Take the knowledge gap first. The truth about your systems is scattered everywhere. A metadata..."
- 4:41 / Evidence 3: "model. And a server only ever offers three kinds of things. Tools, actions it can take like sending a message or running a query, resources, data it can read like files and database rows and prompts, reusable templates,..."
- 6:51 / Evidence 4: "own, a model invents what your metric means. Give it MCP alone and it runs live queries against a schema it does not understand. You need both. OKF makes the answer correct. MCP makes it current. Together, you..."

Video-aware target:
- Prompt lane: Creative automation
- Mechanism to extract: Extract the creative production loop, especially where the human keeps taste, selection, and final judgment.
- Artifact to produce: A creative production board with source inputs, prompt recipe, selection criteria, edit pass, and taste-review checkpoints.
- Artifact must include: brief; source inputs; generation recipe; selection criteria; edit/review checkpoint

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: Extract the creative production loop, especially where the human keeps taste, selection, and final judgment. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A creative production board with source inputs, prompt recipe, selection criteria, edit pass, and taste-review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source material -> Generation -> Selection -> Edit -> Taste review -> Reusable recipe
   - answers to these source questions: What asset is being produced? | What inputs and tools drive it? | Where does human taste intervene?
   - 3 concrete examples that apply the video idea to real agentic work, such as Claude-generated video campaign; image-to-site workflow; voice or video editing loop
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: mistaking novelty for quality; no source/brief discipline; shipping generated media without taste review
   - a checklist for the next real workflow, focused on: brief, inputs, generation, selection, critique
   - one practical exercise with a clear done signal: Build one reusable creative recipe and define what would make the result rejectable.
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 "Google OKF + MCP : Explained The New "AI Context Stack"", not a generic Creative Automation essay.
- Anchor each creative step to transcript evidence about inputs, model/tool choices, iteration, editing, or critique.
- 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 content advice; tool hype; creative output without selection criteria.
- 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.