Workflow Presentation Generator

Workflow Presentation Generator turns one authorized Moira workflow into a self-contained local HTML presentation for business and technical readers. It combines source-grounded purpose, complete topology, progressive disclosure for large graphs, sensitive-data boundaries, deterministic HTML checks, and independent semantic and visual review.

mcp__moira__start({
  workflowId: "moira/workflow-presentation-generator",
  parentExecutionId: "none"
})

Sources and durable artifacts

The input may be an accessible Moira owner/slug or an authorized local JSON path. ID acquisition uses a complete workflow download rather than a bounded node page. The execution-correlated workspace stores the selected workflow.json, provenance, official workflow-schema.txt, presentation content, self-contained HTML, limitations, validation and review findings, repair account, corrected contract, and final report.

The official projection supplies complete node/edge accounting, starts, teleports, terminals, reachability, cycles, dangling targets, and declared data flow. Business meaning and directive semantics are checked in the complete JSON; validator success is not treated as product proof.

Presentation quality

Business claims come from metadata, directives, outcomes, or supplied context and label supported inference or unavailable context. Technical content preserves important routes and contracts. Large workflows use a readable overview plus searchable/collapsible complete topology or appendix instead of flattening or omitting nodes.

presentation.html contains embedded CSS and optional embedded JavaScript, semantic headings, keyboard-usable navigation, responsive and print styles, and no CDN, external font/script/style, fetch, form, or runtime network dependency. It is suitable for the network-isolated Moira static-artifact sandbox if separately published later.

Deterministic checks own files, HTML parseability, anchors, self-containment, and source/projection identity. An independent reviewer owns business accuracy, technical faithfulness, progressive disclosure, redaction, hierarchy, accessibility, and visual usefulness. Source, content, HTML, completion, and validation findings return to their earliest owner; invalid criteria enter independently reviewed contract correction.

Modes, outcomes, and authority

Autonomous mode skips only final user acceptance. Interactive mode supports accept, abort, or one owner-scoped rework request. Outcomes distinguish complete, reviewed-limited, blocked before or after workspace creation, workspace failure, and aborted.

The result is local. The workflow does not mutate the source, upload, publish, copy outside the workspace, notify, commit, release, or deploy. Access to a private source does not authorize public hosting.