Every workflow is an API path you can call: POST /api/run → a standards-traceable report URL. Below are the paths that are live today, and the domains being onboarded. Nothing here is claimed before it has a firable workflow row.
Runnable today on the free Open Deck tier. DNV-traceable, deterministic, with report URLs published to the public gallery.
| ref (workflow path) | domain / subdomain | required inputs | deliverable | example report URL |
|---|---|---|---|---|
subsea_pipeline_wall_thickness_screenengine: digitalmodel wall-thickness quickcheck |
subsea-pipelines-integrity / pipeline |
objective configuration environment design_pressure_rating buckle_arrestors data_available deadline |
Summary-first reply + standards-traceable HTML report package in a dated sandbox run dir (DNV-ST-F101). | deckhand-sandbox gallery → .../report.html |
floating_marine_mooring_screenengine: digitalmodel mooring analysis |
floating-marine / mooring |
objective configuration environment line_material data_available deadline |
Summary-first reply + HTML report package in a dated sandbox run dir. Metallic-line screen; non-metallic escalates honestly. | deckhand-sandbox gallery → .../report.html |
ref is the workflow-row key in the source-of-truth catalog
deckhand/config/deckhand/routing/domain-workflows.yaml. The two live paths run on the
open-source digitalmodel engine; required inputs are the path's clarification keys
(branch-first inputs like buckle_arrestors / line_material are asked, never guessed).
Each call returns a report_url on the
public deckhand-sandbox gallery.
Two further utility paths back the same surface: an Open Deck public router that directs a question to the right domain channel, and isolated private-scope delivery paths for client-confidential work (reports promoted to a client wiki, never the public gallery). Talk to us about private scopes.
These domains are bound and routable but do not yet have a runnable public workflow row. They escalate to a human today — they are not shipped capability. Listed here for honesty, not as a claim.
| domain | subdomains (planned) | status |
|---|---|---|
wells-subsurface | wells, field-development | Onboarding — public workflow row owed |
electrical | electrical | Onboarding — bound, escalate-only |
cad | cad | Onboarding — bound, escalate-only |
manufacturing | manufacturing | Onboarding — bound, escalate-only |
codes-standards-maritime-law | — | Onboarding — bound, no workflow row yet |
domain-workflows.yaml and a published report URL. Until then,
a call to one of these paths escalates to a human — it never fabricates an answer.
Open Deck is the free chat client of the API. Bring a real subsea-pipeline or mooring question and watch a path run, traced to the standard, on open repos.
Try Open Deck on Telegram