Skip to content

OpenProse Flow Linter

Lint OpenProse flow graphs for unreachable stages, dangling edges, privileged paths, and approval gaps

OpenProse Flow Linter

{
  "stageCount": 4,
  "reachableCount": 4,
  "issues": [
    {
      "severity": "warning",
      "message": "Privileged stage execute should require approval."
    }
  ],
  "status": "valid-with-warnings"
}

Updated . Provided as is. Check the output before you rely on it in production.

How to use OpenProse Flow Linter

  1. 1

    Paste flow graph JSON

    Provide a stages array with stage IDs and next links. Optional fields like privileged and requiresApproval can be included for policy checks.

  2. 2

    Run lint analysis

    Click Lint Flow to evaluate graph integrity and governance posture in one deterministic pass.

  3. 3

    Inspect issue list by severity

    Review dangling references, unreachable stages, and privileged-stage policy warnings to locate design defects quickly.

  4. 4

    Fix graph and re-run until clean

    Update your flow definition, rerun linting, and keep iterating until issue count is zero or only accepted warnings remain.

Questions and answers

What is OpenProse Flow Linter?
In this linter a flow is a JSON array of workflow stages, each listing the stages that run next. It flags stages without IDs, duplicate IDs, references to missing stages, stages unreachable from the first stage, and privileged stages that do not require approval.
Which issues does OpenProse Flow Linter detect?
It flags dangling next-stage references, unreachable stages, duplicate IDs, and stage policy issues that can break orchestration at runtime.
Can it check privileged stages?
Yes. Privileged stages without explicit approval requirements are highlighted so you can add the missing gate before shipping.
Does OpenProse Flow Linter store or send my data?
No. Flow validation happens in-browser and no graph data is transmitted.
For AI agents: how to call this tool

Machine-readable contract, endpoints and examples. Humans can ignore this section.

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/openprose-flow-linter/

For automation planning, fetch the canonical contract at /api/tool/openprose-flow-linter.json.