Demo090 — Complete Pipeline

Prepare the demo

Start at the root of the complete solution already built in Release. Course prerequisites: Demo080. This program uses live chat from the selected profile; no embeddings are required except for Demo020 --embed. Check connectivity and required capabilities before attributing failure to the scenario.

• Actions and in-process approval

• Installation and initial setup

Launch from the root

dotnet run --project demos/Demo090_CompletePipeline/Demo090.App.csproj -c Release --no-build

Modes and procedure

Follow the complete Actions and approval procedure: isolated database, initial list, clear request, refusal, a newly approved proposal and readback. Clarify ambiguous input before attempting a write.

Console.WriteLine("Host catalogue step: " + JsonSerializer.Serialize(Catalog.Names));
var analysis = await analyst.RunAsync("Trusted component identifiers: " + string.Join(", ", Catalog.Names) + "\nUntrusted request: " + input, cancellationToken: stop.Token);
BacklogDraft? draft;
try { draft = JsonSerializer.Deserialize<BacklogDraft>(analysis.Text, new JsonSerializerOptions(JsonSerializerDefaults.Web)); }
catch (JsonException) { Console.WriteLine("Invalid structured response; no action."); continue; }
if (draft is null) { Console.WriteLine("Missing draft; no action."); continue; }

demos/Demo090_CompletePipeline/Program.cs · L35–L40 · 9a895c94534c

Source code · Demo090 · Folder

• demos/Demo090_CompletePipeline/Demo090.App.csproj

Results and useful failures

Host catalogue step runs directly in C# before analysis; it does not depend on the agent voluntarily calling list_components. The analyst receives no sensitive tool. The writer accepts only proposalId. Compare Assistant declaration, Host invocation evidence and Stored rows; inspect them to establish the effect.

These observations are expected from inspecting the indicated code revision. No new model call was made to write this page; exact generated wording is not a reference output.

Scope and limits

The pipeline is explicit C# orchestration, not the MAF graph engine. Four rounds bound approval without providing a general retry policy. A new proposal can recreate the same need; there is no durable idempotence.

Continue and verify

• Actions and in-process approval

• Demo index

• Analysis and action: Start/End