MICROSOFT AGENT FRAMEWORK · 0.16.0-rc.1
Reading conventions and historical correspondence
Understand historical names and the current reading path without depending on videos.
Objectives
- Historical J1/J2 and episode markers
- Adaptation of spoken transitions
- Name correspondence and accessible diagrams
From episodes to a readable course
J1/J2, Video2–5 and EP001–EP018 identify material provenance. The site follows problems from simple boundaries to documented action. A slide announcement or training duration does not define reading order. Explanations, commands, diagrams and corrections are present in HTML; videos and archives are not required.
Name correspondence
| Mechanism | Scope |
|---|---|
| Lab03 ToolsCatalog | Demo060; host catalog, not components.json. |
| Lab04 SQLite / Extended | Demo070 / Demo080; console consent then native approval. |
| Lab05 PipelineComplete | Demo090; explicit C# orchestration. |
| Video2 / B2B workflow | Demo230–250; BacklogDraft review. |
| Video3 / Video4 | Demo400 MCP / Demo460 evaluation. |
| Video5 | Demo410; shared backend, streaming and sessions. |
Transitions and figures
Figures describe data or control paths with textual alternatives. An arrow promises neither concurrency nor a shared transaction. After a valid contract comes execution permission; after a persisted decision comes effect uniqueness; after a measurement come coverage and interpretation. These transitions explain why the same request spans chapters without repeating all code.
Read the renovated baseline
Old RC signatures, project names, filming scripts and retired solutions are not current instructions. Follow shared bilingual Demo identities and linked code. Session, fact memory and checkpoint denote different mechanisms. Renovated RAG uses SQLite and dense embeddings even where original material named different infrastructure.
Historical promotional critique suggested universal tool, agent or token counts and model success percentages. Those values lack a protocol and are not retained. Choose bounds from risk, contract and a measurable counterexample; retain dated results with their scope.
Preserve history without republishing it
Preserving originals does not include them in the public package. Private slide-authoring instructions and promotional messages do not become technical concepts. Scenario corrections remain explicit; a review example is not presented as an approved write.