One source. Code and no-code, in sync.

Pick a workflow and flip the toggle — see it as a no-code playbook, the CLI / CloudShell commands that stand up the stack, the assets it scaffolds, or a prompt to paste into your AI assistant. Every view comes from one source through the same engine the CLI uses, so code and no-code never drift. Nothing leaves your device.

Educational and informational only — not legal or clinical advice. The Studio shows how to operate a tool with your team; it is not advice for any specific family or case.

New here? This is one of the no-code tools — pick a source and copy whichever view fits you (a plain playbook, the developer commands, the files, or a prompt for your AI). No install.

Build from one source#

Loading the studio…

See the logic — role & workflow diagrams#

Pick a role to see the skills it composes and its always-on guardrails (the child-centered & trauma-informed lens), or a workflow to see its real step graph — every call_skill, branch, and output. These are the same diagrams cotrackpro diagram role|workflow produce, and the offline mirror of the MCP server's get_role_diagrams.

Illustrative — educational only. The roles and workflows below are example compositions that show how the platform's pieces fit together. They are not a prescriptive legal process or advice for any specific family or case.

Loading diagrams…

Use it from the CLI#

The portal and the CLI render the same projections from the same catalog — the commands you copy here are byte-identical to:

cotrackpro workflow list                                       # every source
cotrackpro workflow render school-incident-tool --as playbook  # the no-code playbook
cotrackpro workflow render school-incident-tool --as commands  # the stack commands
cotrackpro workflow render school-incident-tool --as assets --out ./my-tool   # write the files
cotrackpro workflow render school-incident-tool --as prompt    # a prompt to paste into your AI

How it fits#

A source — a blueprint (richest: roles, artifacts, scenarios, workflows, guardrails), a scenario, or a workflow — is resolved once into a typed spec, then projected three ways by shared, import-free SDK cores (@cotrackpro/sdk/workflow + @cotrackpro/sdk/guide + @cotrackpro/sdk/diagram). The Playbook is the no-code markdown; the Commands are a runnable cotrackpro sequence (plus an Open in Cloud Shell launch); the Assets are the exact files the CLI scaffolds. Because the portal loads the compiled cores, what you see here equals what a developer runs — one source of truth, two audiences, zero drift.

Browse the workflows and scenarios these views are built from in the Library.