Visual Workflow Blueprints

Intent

• •Speed up comprehension of complex processes (PR lifecycle, launch plan, triage ops) via monospaced diagrams.
• •Provide reusable templates and conventions for both macOS/Linux terminals and Windows consoles.

Inputs

1. •Workflow steps, roles, decision points.
2. •Target medium (GitHub comment, Slack, Notion, terminal output).
3. •Required metadata (owners, SLAs, tools).

Workflow

1. •Select diagram type
   • •Flowchart (boxes/arrows) for branching logic.
   • •Timeline/swimlane for sequential steps.
2. •Use standard glyphs
   • •Start/End: (start) (end)
   • •Process: [ action ]
   • •Decision: { condition? }
   • •Arrows: -->, ==>, ~~> for async.
3. •Build with templates
   • •Flow template:
     code

     (start)
       |
     [Step 1]
       |
     {Decision?}
      /   \
     

   yes no
   code

   - Timeline template:
   

   Day 0 Day 3 Day 7 |-----|-----|-----| Dev QA Launch
   code

4. •Annotate with data
   • •Include owners (@alice), tooling (gh pr checks), or SLA markers (<24h).
5. •Validate readability
   • •View in plain text viewer; avoid tabs; max width 80 chars.

Verification

• •Diagram renders without wrapping in GitHub/CLI.
• •Each decision path labeled clearly.
• •Stored alongside workflow documentation (e.g., .factory/docs/visuals).