Skip to main content

End-to-End Workflow

Use this workflow as the backbone of the docs and the product narrative:

  1. Prepare inputs
  2. Verify inputs in PreFlight UI
  3. Submit to Computational Safety Diligence
  4. Review outputs and evidence
  5. Apply add-ons when needed
  6. Make a decision or iterate

Why this matters

The docs should mirror the actual user journey instead of exposing internal system decomposition first.

Operational rule

Whenever possible, cross-link pages according to the workflow above so a user can always move forward without guessing where to go next.