Study real implementations, then adapt them to your own product
Every example page states what the code demonstrates, which principles it supports, which libraries it uses, and how it fits into the learning and certification path.
Key Facts
- Examples
- 96
- Runnable
- 96 runnable scripts
- Browse by
- Principle, runtime pattern, difficulty, library, and product problem
- Libraries
- pydantic, python-dotenv, openai, requests, docling, gradio, streamlit, ipykernel
- Use this for
- Learning patterns, comparing implementations, and preparing your own product decisions
In this section
Providers & libraries
Start with examples that match the product problem you are working on: approvals, orchestration, retrieval, tool use, or background work. Then follow the linked principle pages and course material.
Use the example index as a working implementation map. It should help teams compare patterns, understand runtime tradeoffs, and connect code references back to product behavior and trust criteria.
Find the right example
Instead of browsing the whole library, activation uses your context to narrow the field and prepare the most credible route across examples, doctrine, runtime, or review.
Course stage
Module
Models & OpenAI31
MCP14
Agents12
Frameworks10
Knowledge11
Web Context10
Workflows8
For humans, these pages remain the inspectable editorial view. For agents, the For agents surface is the stable entry point for retrieving the same examples and linking them to the right principles.
Agent entry point
Open For agents
Use the MCP endpoint, skill pack, and rules exports to retrieve examples directly.
Doctrine
Reconnect examples to doctrine
When a pattern looks useful, return to the principles so you understand the design judgment supporting it.
Runtime branch
Move patterns into runtime architecture
Use the runtime architecture branch when code patterns need to become triggers, schedules, context hubs, or runtime boundaries.
Plan mapping
See the path by plan
Check how public access, protected validation, and shared governance connect to the pricing structure.
From agent demos to runtime discipline
A capable model is not a runtime architecture. If agents are going to trigger workflows, load files, use tools, delegate work, and act across channels, the runtime needs clear patterns for control, visibility, and recovery. This cluster helps teams design those patterns deliberately.
It should tell the reader what the pattern does, why it matters, and where it belongs in the learning path. A strong example page is a concrete bridge between doctrine and implementation.
They should know which principle page to read next, which course or lab deepens the concept, and how the example might translate into their own product or workflow.