Specification stage

The Specification stage produces a canonical contract from your diagram and policy effects. Downstream prompts and reviews depend on this output.

What happens in this stage

• Component, connection, and policy-derived constraints are merged.
• Specification artifacts are rendered in multiple output formats.
• Copy/download actions let you reuse the artifact externally.

Tabs and how to use them

• Markdown

- Best for human review and implementation checklists.

- Use in design review meetings and planning sessions.

• JSON

- Best for structured integrations and scripted consumers.

- Useful for tooling pipelines that parse schema-like content.

• YAML

- Best for policy/configuration style interchange.

- Good for manual diffing and source-control review.

• NodeEdge

- Best for graph-shaped workflows and graph-aware agents/tools.

- Keeps node/edge semantics explicit.

• Constraints

- Shows derived constraints with source provenance.

- Use to debug "why this requirement exists."

Practical workflow

1. Validate Markdown for readability and intent.

2. Spot-check Constraints for rule provenance.

3. Copy/export the format needed by your output generation method.