Protected operator workflow

Cross-site Trace Demonstrations

Select a meaningful cross-site workflow and watch its service calls, tool results, evidence, artifacts, recovery receipts, and lineage become one inspectable distributed trace.

Registered demosok
3
Source: workflow registry
Updated: 7/22/2026, 11:51:08 PM
Evidence/query
Workflow stepsok
10 / 15 / 100
Source: registered workflow plans
Updated: 7/22/2026, 11:51:08 PM
Evidence/query
Participating servicesok
19
Source: registered workflow plans
Updated: 7/22/2026, 11:51:08 PM
Evidence/query
Run accessok
Protected
Source: platform trust policy
Updated: 7/22/2026, 11:51:08 PM
Evidence/query

JSON graph handoffs

Open Trace-owned public JSON in the JSON product. The source URL stays attributable and the JSON viewer loads it through its bounded trusted-domain importer.

View workflow catalog as graphView trust policy as graph
Useful operator workflow10 verified stepsRecovery-aware
Story Format Relay — 10-step demonstration
A compact, inspectable story-format relay with evidence from every owning service. The key is sent only in protected request headers, cleared after launch, and never copied into trace metadata or artifacts.

The selected entry controls the registered plan, confirmation token, endpoint, and expected trace length.

The key authorizes durable Trace span and evidence persistence. Demo service calls use public-safe registered tools and never receive the key.

10 meaningful steps, one correlated trace

One root span and 9 real cross-site operations. Existing producer spans retain their original identities when they are ingested.

Phase 11 operations
Source
Read the live PlatPhormNews RSS story source.
Phase 25 operations
Format inspection
Exercise real Docs, Markdown, JSON, XML, and OpenContent capabilities.
Phase 33 operations
Packaging and contract
Plan PDF and ZIP outputs, then validate the live Trace OpenAPI contract.

Inspectable demonstration suite

Every run records bounded request, prompt, response, lineage, and artifact evidence. The first three make public-safe reads only; the briefing is the protected mutation path below.

Open persisted demos
Public-read suite
Parallel investigation
Trace → Monitor + network graph → JSON MCP → evidence-backed output

A bounded health and topology investigation whose final answer is linked to both source requests.

outbound web requeststrace headersMCP arguments and resultfan-in lineage
Public-read suite
Failure and recovery
Trace → expected MCP error → capability discovery retry → warning output

An intentional, non-destructive tool failure retained alongside the successful recovery path.

JSON-RPC errorretry relationshiptool catalogrecovery artifact