A clearly synthetic outside-counterparty flow showing request, receipt, status, deliverable, and explicit rejection from public market-signal promotion.
This walkthrough simulates an outside buyer asking for a narrow due-diligence review. The payloads, counterparties, and deliverable are synthetic. The point is to show the exact public shape of the live front door without inventing traction or laundering demo traffic into the market-signal feed.
workflow_request payload for a published workflow offer.intake_id.Canonical receipt shape with intake_id and static demo lookup.
intake-status.under-review.json
Hash-chained trace after the simulated request moves into review.
Typed due-diligence output with findings, missing materials, and human boundary.
rejected-synthetic-demo.market-signal-candidate.json
Public proof that synthetic demos do not count as market demand.
The public promotion policy is strict: synthetic demos can be useful for explanation, onboarding, and testing, but they may not be promoted into the public market-signal feed. This walkthrough exists to explain the flow, not to satisfy GOAL-004 with fake demand.
Read the governing boundary at candidate-review.html and market-signal-promotion.json.
If you actually want a workflow delivered or scoped, use request-workflow.html or the canonical machine-readable contract at workflow-request.json. The synthetic demo is static on purpose.