Nemotron 3 Ultra: The 100% Free & Open Frontier Model Built for AI Agents

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

Source video:
- Title: Nemotron 3 Ultra: The 100% Free & Open Frontier Model Built for AI Agents
- URL: https://www.youtube.com/watch?v=NoLMRvVy1gk
- Topic: Agentic Engineering
- My current learning frame: Set up Nemotron 3 Ultra in Open Code by editing opencode.json (point the provider at the endpoint, set 1M context and ~32K output), start with the medium reasoning-effort setting, and run one long batch task to test whether it holds context without drifting.
- Why this matters: New playlist item from AI Stack Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:47 / Evidence 1: "done. Nemotron 3 Ultra was built to work. Nvidia designed it for long-running agents, the kind that plan a task, call tools, read the results, hand work off to other agents, check their own output, and recover when..."
- 2:54 / Evidence 2: "the full 1 million token context and the model fully open source. Open Code connects to any OpenAI compatible endpoint, so once it's pointed at the model, you just start working. The other free option is Open Router,..."
- 4:41 / Evidence 3: "simple questions. You match the effort to the task. Now, let me show you what it looks like on a real job instead of a toy one. I gave it a batch of related content to build out,..."
- 7:04 / Evidence 4: "Nvidia put out a small content safety model and a multilingual speech recognition model in the same release, aimed at people building safer agents and voice-enabled ones. And the model itself speaks about a dozen languages, so this..."

Video-aware target:
- Prompt lane: Agentic engineering
- Mechanism to extract: Extract the engineering loop that converts an agent demo into controlled, inspectable work.
- Artifact to produce: A task packet and review rubric that a coding agent could execute without wandering.
- Artifact must include: scope; context inputs; acceptance criteria; verification command; review rubric

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 engineering loop that converts an agent demo into controlled, inspectable work. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A task packet and review rubric that a coding agent could execute without wandering.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Task packet -> Context -> Agent run -> Evidence -> Review -> Reusable standard
   - answers to these source questions: What work packet is implied? | Which context does the agent need before editing? | How does the video define proof or quality?
   - 3 concrete examples that apply the video idea to real agentic work, such as a feature patch packet; a test-fix packet; a learning-page improvement packet
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: delegating vague intent; accepting output without evidence; turning taste into loose preference instead of a rubric
   - a checklist for the next real workflow, focused on: scope, files/context, tests, review criteria
   - one practical exercise with a clear done signal: Rewrite one vague request into a bounded agent packet with explicit proof of done.
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 "Nemotron 3 Ultra: The 100% Free & Open Frontier Model Built for AI Agents", not a generic Agentic Engineering essay.
- Cite the transcript wherever the prompt names a task boundary, review habit, context move, or verification standard.
- 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 productivity advice; unsupported claims about autonomy; summaries without implementation 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.