Workflows
Markdown file
../../DOCS/features/workflows.md
Workflows
Routes
- Canonical index:
/workflows - Canonical entry:
/workflows/:slug
Purpose
- Publish workflow definitions as first-class entities with required diagrams.
- Link workflows back to related projects, notes, or chats.
- Highlight when workflows are reused across multiple projects and when workflows chain together.
- Keep content aligned with Constellation by treating workflows as first-class nodes.
Data Source Contract
- Server-side catalog readers:
getWorkflows()getWorkflowBySlug(slug)
- Diagrams are rendered with Mermaid using
buildWorkflowMermaidChart. - Pages are rendered with
dynamic = "force-dynamic"so updates appear at runtime. - Workflow steps are persisted in
kb_workflows/kb_workflow_stepsand can be seeded frommeta.workflow_stepsduringintake:sync:knowledge. - Related project context is derived from
relatedProjectSlugs(single project = “part of project”; multiple = reused) and rendered as text-only project links. - Workflow chains are declared via
relatedWorkflowSlugsand rendered as linked sequences on the detail page. - The workflow detail page includes a context box that surfaces project links plus the workflow chain sequence.
Primary Files
src/app/workflows/page.tsxsrc/app/workflows/[slug]/page.tsxsrc/lib/workflows/diagram.tssrc/lib/server/content-catalog.tssrc/content/workflows.tsscripts/intake/workflow/sync-workflow-intake-to-knowledge-backbone.ts