Workflow Architecture

20 workflows organized in 4 layers. Design principle: Composable & Atomic (SC5) — each does ONE thing, complex operations compose atomics.

Created: A122 (2026-03-21)

System Map — 4 Layers

┌───────────────────────────────────────────────────────────────┐
│  ⚡ ATOMIC — do one thing, no side effects                    │
│                                                               │
│  /commit       commit & push (conventional commits)           │
│  /log          log file + D1 log + D1 velocity                │
│  /ongoing      add/update/remove ongoing.md entries           │
│  /discuss       discussion mode (no execution)                 │
│  /hub-status   read-only daily pulse                          │
│  /hub-clean    data hygiene: logs, tasks, git                 │
│  /hub-archive  archive done tasks + old logs + reports        │
│  /skill        create new skill                               │
└───────────────────────────────────────────────────────────────┘

┌───────────────────────────────────────────────────────────────┐
│  🔵 TASK LIFECYCLE — track work from start to finish          │
│                                                               │
│  /task start   config → folder? → D1? → comments? → go       │
│  /task save    /commit → D1 sync → audit comment → /log       │
│  /task done    mark done + ongoing + D1 + audit (atomic)      │
│  /task archive move to archive                                │
│  /task spawn   full work package for later                    │
└───────────────────────────────────────────────────────────────┘

┌───────────────────────────────────────────────────────────────┐
│  🟠 SESSION LIFECYCLE — capture, assess, transition           │
│                                                               │
│  /session save     full reasoning trail (by topic)            │
│  /session summary  quick session status (chat)                │
│  /session health   subjective quality gauge                   │
│                    → if <60%: suggest /handoff                 │
│  /session quality  rate smoothness + hypotheses               │
│  /handoff          save state → next-session.md               │
│                    → consider /task spawn                      │
│                    → suggest /wrapup                           │
└───────────────────────────────────────────────────────────────┘

┌───────────────────────────────────────────────────────────────┐
│  🎯 ORCHESTRATOR — compose atomics into sequences             │
│                                                               │
│  /wrapup session                                              │
│    0.5  handoff check   (if degraded → /handoff first)        │
│    1.   /session save   (if discussion)                       │
│    2.   /learn          (if learnings)                         │
│    3.   /learn scan     (if KB-worthy)                        │
│    4.   /hub-evolve     (if hub changed)                      │
│    5.   /task done|save (always)                              │
│    6.   /log            (always)                              │
│    7.   /commit         (always)                              │
│    8.   wellness check  (always)                              │
│                                                               │
│  /wrapup day                                                  │
│    → run /wrapup session for each active task                  │
└───────────────────────────────────────────────────────────────┘

Composition Map — Who Calls Who

/wrapup ─────┬─ /session save
             ├─ /learn
             ├─ /learn scan
             ├─ /hub-evolve
             ├─ /task done ─── /ongoing
             ├─ /log
             └─ /commit

/handoff ────┬─ /task spawn   (if scope grew)
             └─ suggests → /wrapup

/task save ──┬─ /commit
             └─ /log

Strategic Workflows

Alignment — Three Zoom Levels

Zoom	Workflow	Cadence	Question
🔭 LIFE	`/vision align`	Quarterly	Stress? Energy? Life balance?
📅 WEEK	`/clara`	Weekly	Which tasks this week? Triage inbox?
🎯 WORK	`/vision`	Per-task	Does this serve the vision chain?

Assessment

Workflow	Scope	Output
`/clarity`	Project/domain	How crystallized is the context?
`/hub-audit`	Hub system	Quality inspection against principles
`/hub-status`	Daily	Read-only pulse check

Knowledge & Learning

Workflow	Purpose
`/learn`	Extract and store session learnings → rules/memory
`/hub-evolve`	Sync stale docs/architecture after hub changes
`/learn scan`	Scan for content worthy of centralized KB

Decision Flow — "What Do I Call?"

Session ending?
├─ YES → Context degraded?
│         ├─ YES → /handoff → /wrapup
│         └─ NO  → /wrapup
│
└─ NO  → What am I doing?
          ├─ Working        → /task save  or  /commit
          ├─ Need direction → /vision align (life) | /clara (week) | /vision (task)
          ├─ Quick pulse    → /hub-status
          ├─ Discussion     → /discuss
          └─ Process inbox  → /clara

Task Start Decision Matrix

Local Folder	D1 Record	Action
✅	✅	Resume — read README, go
✅	❌	Resume + create D1 record
❌	✅	Fresh start with D1 context
❌	❌	Fully new — ask user

Design Decisions (A122)

#	Decision	Rationale
D1	Atomic vs Orchestrator split	Each workflow does ONE thing; `/wrapup` composes them
D2	`/handoff` as first-class	Clean exit path when context degrades
D3	Task start: folder-first + comments	Prevent duplicate folders, leverage D1 audit trail
D4	Subjective health over token math	Token % gives false confidence; trust the feeling
D5	Three alignment zoom levels	LIFE / WEEK / WORK — clear when to use which
D6	`/clarity` simplified 4→3 modes	Merged `next` into `report`

Workflows

On this page