Triage System — Execution Flow

Two-Path Mapping

Triage spans the User Path (human experience) and System Path (operational pipeline). The diagram below shows which steps belong to which path.

┌─────────────────── SYSTEM PATH ───────────────────────────────┐
│                                                               │
│  Intake → Classify → Link → Dedup → Stage → Audit            │
│                                                               │
└───────────────────────────┬───────────────────────────────────┘
                            │
                     ┌──────▼──────┐
                     │  BOUNDARY   │
                     │  Candidates │
                     │  flow to    │
                     │  User Path  │
                     └──────┬──────┘
                            │
┌───────────────────────────▼───────────────────────────────────┐
│                                                               │
│  User Path: Discover → Understand → Contextualize → DECIDE   │
│                                                               │
└───────────────────────────┬───────────────────────────────────┘
                            │
                     ┌──────▼──────┐
                     │  BOUNDARY   │
                     │  Decisions  │
                     │  flow to    │
                     │  System Path│
                     └──────┬──────┘
                            │
┌───────────────────────────▼───────────────────────────────────┐
│                                                               │
│  System Path: Consolidate → Promote → Index → Consume        │
│                                                               │
└───────────────────────────────────────────────────────────────┘

Phase	Path	Steps
Intake & Classification	System	Intake → Classify → Link → Dedup → Stage → Audit
Governance Decision	User	Discover → Understand → Contextualize → Decide (approve/reject/defer)
Promotion & Indexing	System	Consolidate → Promote → Index → Consume

Neither path can bypass the other. The System Path never writes canonical memory. The User Path never classifies.

End-to-End Data Flow

┌─────────────────────────────────────────────────────────────┐
│                    INTAKE SOURCES                            │
│  MCP Capture · Conversation Archive · Session · Manual       │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│                  TRIAGE INTAKE                               │
│  iw-agent-runtime TriageAgent (Durable Object)              │
│  - classify(content) → route                                │
│  - triage_items (operational state)                         │
│  - emitTriageInput → Continuity service                     │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│              COGNITIVE TRIAGE (intelligence)                 │
│  TriageAgent (WorkflowStep)                                 │
│  - 4 Cognitive Dimensions: classify, link, review, govern   │
│  - Output: STAGE_FOR_REVIEW or REJECT                       │
│  - No AUTO_APPROVE for org memory                           │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│                  DURABLE WORKFLOW                            │
│  TriageWorkflow (Cloudflare Workflow)                       │
│  - Routes pending_approval → HITL DLQ                       │
│  - Routes rejected → terminal                               │
│  - NO direct writes to R2/Vectorize/D1/Pipeline             │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│              KNOWLEDGE SERVICE (triage-bot)                  │
│  AI extraction (Workers AI)                                 │
│  - All outputs: approval_status = 'pending'                 │
│  - Writes to triage_results (Neon/D1)                       │
│  - Slack notification (review channel, not authority)        │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│              HUMAN IN THE LOOP                              │
│  Knowledge Service: PATCH /v1/knowledge/triage/:id          │
│  - Authenticated principal                                  │
│  - Tenant authority                                         │
│  - Optimistic/version check                                 │
│  - Actions: approve | discard | defer                       │
└──────────┬─────────────────────┬────────────────────────────┘
           │                     │
     ┌─────▼─────┐        ┌─────▼─────┐
     │  approve   │        │  discard  │
     └─────┬─────┘        └─────┬─────┘
           │                     │
           ▼                     ▼
┌──────────────────┐    ┌──────────────┐
│  QUEUE:          │    │  TERMINAL    │
│  consolidation   │    │  No memory   │
│  trigger         │    │  published   │
└────────┬─────────┘    └──────────────┘
         │
         ▼
┌─────────────────────────────────────────────────────────────┐
│         MEMORY CONSOLIDATOR (scheduled worker)              │
│  - Hourly: topic clustering of recent sessions              │
│  - Daily: user/account consolidation + health signals       │
│  - Weekly: cross-account patterns + best practices          │
│  - Reads approved triage items only                         │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│         CANONICAL PROMOTION (pipeline/memory-promoter)      │
│  - scoreForPromotion() — 7 Promotion Signals                │
│  - Governance gate: staging vs approved                     │
│  - Writes to org_memory (D1)                                │
│  - Audit trail (memory_promotion_audit)                     │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│         INDEXING (pipeline/memory-indexer)                   │
│  - Bulk index approved org_memory → AI Search               │
│  - Markdown + metadata per vector                           │
│  - Idempotent re-upload                                     │
└──────────────────────┬──────────────────────────────────────┘
                       │
                       ▼
┌─────────────────────────────────────────────────────────────┐
│         CONSUMER                                           │
│  Twin reads published memory through bounded context        │
│  projection — never raw canonical storage                   │
└─────────────────────────────────────────────────────────────┘

Step-by-Step Walkthrough

Step 1: Intake

An event arrives from one of:

MCP Connector — saves session memory after a tool call
Conversation Archive — triggers extraction when a conversation is archived
Session Triage — /v1/triage/session endpoint receives session summary
Manual Trigger — admin triggers triage via API

The iw-agent-runtime TriageAgent (Durable Object) receives the event, classifies it by simple pattern matching, and stores it as a triage_item in operational state.

Step 2: Continuity Emission

The TriageAgent calls emitTriageInput() which posts to the Continuity service at http://internal/v1/continuity/events. This creates a cognition/system event in the continuity stream.

Step 3: Cognitive Evaluation

If the event qualifies for cognitive triage (higher-stakes content), the intelligence service’s TriageAgent performs a deep evaluation:

Intelligent Categorization — What is the true intent? (Lead, Document, Operational Request)
Contextual Linking — How does this relate to canonical memory? Which entities does it touch?
Canonical Review — Is it stale? Duplicate? Conflicts with established truths?
Guardrails & Governance — Based on sensitivity, should it be staged for review or rejected?

Output is strictly: "STAGE_FOR_REVIEW" or "REJECT". No AUTO_APPROVE.

Step 4: Workflow Routing

The TriageWorkflow durable workflow routes the result:

pending_approval → sent to HITL DLQ (Human-In-The-Loop Dead Letter Queue)
rejected → terminal state, no memory published
approved (legacy — should not occur after patching) → treated as staging_for_review

No direct writes to R2, Pipeline, D1, or Vectorize from this workflow.

Step 5: Knowledge Extraction

The knowledge service’s triage-bot.ts extracts structured knowledge using Workers AI:

Memory types: insight, preference, fact, decision, action_item, relationship
All extractions written to triage_results with approval_status = 'pending'
Slack notification sent for review (channel, not authority bypass)

Step 6: Human Review

A human reviews the triage item via:

Workspace Triage Inbox — GET /v1/knowledge/inbox shows pending/deferred items
Slack Reactions — ✅ Approve, ❌ Discard, ⏰ Defer (must be verified as approval event)
API — PATCH /v1/knowledge/triage/:id with action: approve/discard/defer

The approval endpoint requires:

Authenticated principal
Tenant authority
Optimistic/version check
Approver identity and timestamp
Immutable decision audit

Step 7: Consolidation

The Memory Consolidator runs on schedule:

Schedule	What It Does
Hourly	Topic clustering of recent sessions
Daily	Deep user/account consolidation + health signals
Weekly	Cross-account pattern extraction + best practices

It reads only approved triage items and generates consolidated memories.

Step 8: Canonical Promotion

The Pipeline’s memory-promoter.ts is the sole canonical writer:

Scores the Spine write against 7 Promotion Signals
Determines governance state (staging vs approved)
Writes to org_memory (D1)
Deduplicates by lineage_ref
Creates audit trail in memory_promotion_audit
Indexes approved memory into AI Search

Step 9: Indexing and Consumption

Approved org_memory entries are indexed into AI Search as markdown documents with full metadata. Twin reads published memory through bounded context projection — never raw canonical storage.

01 · Doctrine

02 · Product Architecture

03 · Two Paths

04 · Spine Fabric

09 · AI & Agents

10 · Triage & Organizational Memory

02 — Execution Flow

Triage System — Execution Flow

Two-Path Mapping

End-to-End Data Flow

Step-by-Step Walkthrough

Step 1: Intake

Step 2: Continuity Emission

Step 3: Cognitive Evaluation

Step 4: Workflow Routing

Step 5: Knowledge Extraction

Step 6: Human Review

Step 7: Consolidation

Step 8: Canonical Promotion

Step 9: Indexing and Consumption

​Triage System — Execution Flow

​Two-Path Mapping

​End-to-End Data Flow

​Step-by-Step Walkthrough

​Step 1: Intake

​Step 2: Continuity Emission

​Step 3: Cognitive Evaluation

​Step 4: Workflow Routing

​Step 5: Knowledge Extraction

​Step 6: Human Review

​Step 7: Consolidation

​Step 8: Canonical Promotion

​Step 9: Indexing and Consumption

Triage System — Execution Flow

Two-Path Mapping

End-to-End Data Flow

Step-by-Step Walkthrough

Step 1: Intake

Step 2: Continuity Emission

Step 3: Cognitive Evaluation

Step 4: Workflow Routing

Step 5: Knowledge Extraction

Step 6: Human Review

Step 7: Consolidation

Step 8: Canonical Promotion

Step 9: Indexing and Consumption