Agentic Hub Docs
Portal & WorkflowsWorkflows

Reference

Workflow Architecture — Hub Workflows Reference

20 workflows organized by purpose. Each workflow is atomic (does one thing) or an orchestrator (composes atomics). Design principle: SC5 — Composable & atomic, UNIX-like. See principles.md.

Quick Reference

#WorkflowTypeModesPurpose
1/taskLifecyclestart, save, done, archive, spawnTask lifecycle management
2/commitAtomicCommit & push with conventional commits
3/logAtomicLog entry + velocity tracking
4/ongoingAtomicManage ongoing.md entries
5/discussAtomicdefault, score, analyze, probe, deriveDiscussion mode (no execution)
6/hub-statusAtomicRead-only daily pulse check
7/hub-cleanAtomicData hygiene: log integrity, task consistency, git health
8/hub-archiveAtomicArchive done tasks, old logs, linked reports
9/skillAtomicCreate new skills
10/sessionReflectingsave, summary, health, qualitySession capture & assessment
11/handoffTransitionSave state for fresh session pickup
12/wrapupOrchestratorsession, dayFull close-out sequence
13/hub-evolveLearningSync docs/rules/workflows after hub changes
14/learnLearningExtract & classify learnings from session
15/learn scanLearningKnowledge base check & update
16/claraOperationalsweep, focus, align, parkInbox dispatch & task recommendation
17/visionStrategicalign, check, scanVision chain alignment
18/clarityStrategicsummary, report, handoffContext clarity measurement
19/vision alignStrategicLife-level strategic alignment (merged into /vision)
20/hub-auditReflectingHub audit against principles (Audy's rules)
21/research evaluatePipelinescore-only, plan-only, fullAI/tech link evaluation → score → plan → implement

Phase Groups

⚡ Atomic Layer — Do one thing well

/commit      Commit & push (conventional commits, fire-and-verify)
/log         Write log file + D1 log + D1 velocity
/ongoing     Add/update/remove entries in ongoing.md
/discuss     Discussion mode — no execution, no file edits (5 modes: default, score, analyze, probe, derive)
/hub-status  Read-only pulse check (15 lines max)
/hub-clean   Data hygiene: log integrity, task consistency, git health
/hub-archive Archive done tasks, old logs, linked reports
/skill       Create new skill (delegates to Skill Creator)

🔵 Task Lifecycle — Track work from start to finish

/task start    Check folder + D1 + comments → create or resume → go
/task save     Checkpoint: /commit → D1 context → audit comment → /log
/task done     Atomic: mark done + ongoing + D1 + audit comment
/task archive  Move completed folders to archive
/task spawn    Create full work package for deferred/delegated execution

🟠 Session Lifecycle — Capture, assess, transition

/session save     Full reasoning trail capture (organized by topic)
/session summary  Quick session status (chat)
/session health   Subjective context quality gauge (no token math!)
/session quality  Rate smoothness, hypotheses, vision alignment
/handoff          Save state → next-session.md → suggest /wrapup

🎯 Orchestrator — Compose atomics into sequences

/wrapup session   Step 0.5: handoff check
                  Step 1:   /session save     (if discussion)
                  Step 2:   /learn            (if learnings)
                  Step 3:   /learn scan       (if KB-worthy)
                  Step 4:   /hub-evolve       (if hub changed)
                  Step 5:   /task done|save   (always)
                  Step 6:   /log              (always)
                  Step 7:   /commit           (always)
                  Step 8:   wellness check    (always)

/wrapup day       Run /wrapup session for each active task

🧠 Learning Layer — Extract and store knowledge

/hub-evolve   Sync stale docs/rules/workflows after hub changes
/learn    Extract & classify learnings → memory/rules/adrian.md
/learn scan   Scan session for KB-worthy business/domain facts

🟢 Strategic Layer — Assess and align

/vision align   Load vision chain, check task serves compass (WORK level)
/vision check   Is purpose missing? Flags unfocused work (WORK level)
/vision scan    Full workspace audit for vision alignment
/clarity        Measure crystallization of project context
/vision align   Life-level: stress, energy, balance, direction (LIFE level)

3 zoom levels for "am I focused?":

🔭 /vision align   = LIFE    (quarterly: stress, energy, all areas)
📅 /clara align   = WEEK    (weekly: rank tasks, set tiers)
🎯 /vision check  = WORK    (per-task: serves the compass?)

🟣 Operational — Manage work pipeline

/clara sweep    Process inbox + feedback → classify → route
/clara focus    Pick highest-priority unblocked task
/clara align    Weekly priority review (WEEK level)
/clara park     Quick-park an idea as feedback
/hub-clean      Data hygiene: logs vs D1, task zombies, git health
/hub-archive    Archive done tasks + old logs + linked reports

🔗 Pipeline — End-to-end processing

/research evaluate <url>  Fetch → score → plan → implement → test → commit
/research evaluate --score-only   Stop after scoring
/research evaluate --plan-only    Stop after planning

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

/task start ─── checks folder + D1 + comments → creates or resumes

/research evaluate ──┬─ WebFetch (content extraction)
            ├─ Score against principles
            ├─ /commit (if implementing)
            └─ KB save (evaluation report)

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 align (week) | /vision (task)
          ├─ Quick pulse      → /hub-status
          ├─ Discussion only  → /discuss
          ├─ Process inbox    → /clara sweep
          └─ Evaluate a link  → /research evaluate <url>

Design Principle: SC5 — Composable & Atomic

Each unit does one thing well. Complex operations compose atomic ones.

This applies to:

  • Hub workflows (this doc)
  • CLI constellation (Schema CLI, Notion CLI, Portal CLI)
  • Portal MCP tools (compound tools compose atomic endpoints)
LayerRoleDon't
AtomicOne output, no side effectsDon't inline other workflow logic
CompoundCompose atomics in sequenceDon't duplicate — call the atomic
OrchestratorFull sequences with conditionsDon't skip steps — be explicit

On this page