MICROSOFT AGENT FRAMEWORK · 0.16.0-rc.1
Demo250 — Workflow Events
The clarification branch has two executors. The native branch has two deliveries to the same agent host; these do not count as two model calls. Local spans establish no write; the stream is consumed to completion.
Objectives
- Observe native workflow events and distinguish them from business proof.
Prepare the program
Live chat through common configuration, granite4:3b by default; no embeddings required. An optional API is selected explicitly with no automatic fallback. Start at the root of the complete distribution. Preserve shared projects and configuration files. Some historical prompts and labels in Demo260–290 remain French in public code; commands and identifiers match this revision.
dotnet build BaseTechnique.slnx -m:1 -c Release| Project | Role |
|---|---|
| demos/Demo250_WorkflowEvents/Demo250.App.csproj | App |
| shared/Maf.Workflows/Maf.Workflows.csproj | Shared implementation |
Commands from the root
dotnet run --project demos/Demo250_WorkflowEvents/Demo250.App.csproj -c Release --no-buildProcedures and variants
Compare --incomplete with the ready case. Separate planned graph, executed path, eventNames, results, errors and activities.
await foreach (var evt in run.WatchStreamAsync(stop.Token))
{
eventNames.Add(evt.GetType().Name);
if (observe) Console.WriteLine("Event: " + evt.GetType().Name);
if (evt is ExecutorInvokedEvent invoked) path.Add(invoked.ExecutorId);
if (evt is WorkflowErrorEvent error) errors.Add(error.Exception?.Message ?? "Unknown workflow error.");
if (evt is WorkflowOutputEvent { Data: ReviewResult result }) results.Add(result);
What must be observable
The clarification branch has two executors. The native branch has two deliveries to the same agent host; these do not count as two model calls. Local spans establish no write; the stream is consumed to completion.
These results are expected from the linked code. Checks actually rerun for this lot are distinguished in exercises and reception; no unmeasured live output is presented as observed.
Limits and retained state
Demo230–250 build a fresh graph per input and write no business effect. Demo260 retains its two sessions only in-process. Demo270–290 interpret a plan through simulated printing without a workflow engine. Live calls depend on the profile; scripted tests qualify no model.
dotnet test tests/Maf.Workflows.Tests/Maf.Workflows.Tests.csproj -m:1 -c Release --no-build --no-restore