{"slug":"triage/01-OVERVIEW","title":"01 — Overview","section":"triage","sectionLabel":"Triage","status":"canon","type":"document","path":"triage/01-OVERVIEW.mdx","bytes":4878,"description":"What the triage system is: the classifier, linker, stager, and gatekeeper between incoming evidence and governed promotion.","updated":"2026-08-24","source":"integratewise/Integratewise-docs-wiki","content":"\n\n## What Is Triage\n\nTriage is the cognitive intake and classification boundary between incoming evidence/AI output and the governed organizational-memory promotion path.\n\nTriage is:\n- the **classifier** — it determines what something is\n- the **linker** — it connects evidence to known entities\n- the **stager** — it prepares candidates for human review\n- the **gatekeeper** — it blocks low-quality or conflicting material\n\nTriage is NOT:\n- the owner of canonical truth\n- a canonical writer\n- an authority grantor\n- a promotion engine\n\n## Why Triage Exists\n\nWithout triage, every AI output, every conversation, every connector event would flow directly into organizational memory. The result would be noise — duplicates, conflicts, stale data, low-confidence claims all treated as truth.\n\nTriage exists to:\n\n1. **Filter** — reject spam, low-confidence, and irrelevant material\n2. **Classify** — categorize evidence by type, domain, and sensitivity\n3. **Link** — connect new evidence to existing entities and work\n4. **Deduplicate** — identify conflicts with canonical truth\n5. **Stage** — prepare candidates for governed human review\n6. **Audit** — emit a durable trail of every classification decision\n\n## The Canonical Law\n\n> **Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result.**\n\nThis sentence defines the four responsibilities:\n\n| Responsibility | Owner | What It Does |\n|---|---|---|\n| **Classify** | Triage | Determines what the evidence is, links it, evaluates quality |\n| **Decide** | Governance (Human) | Approves, rejects, or defers the candidate |\n| **Promote** | Pipeline | Writes approved candidates to canonical organizational memory |\n| **Own** | Spine | Stores and serves organizational memory as governed truth |\n\n## Triage and the Two-Path Architecture\n\nTriage operates at the boundary between the **User Path** (human experience) and the **System Path** (operational pipeline).\n\n### System Path — Where Triage Runs\n\nOn the System Path, triage is the classification and staging phase of the pipeline:\n\n```\nIntake → Load → Normalize → Resolve Identity → Thread Events → Triage → Contextualize → Project → OODA → Governance → Execute → Reconcile\n```\n\nThe System Path handles the mechanical work:\n- Classifying incoming evidence by type, domain, and sensitivity\n- Linking evidence to canonical entities\n- Deduplicating against existing memory\n- Staging candidates for human review\n- Emitting audit trails\n\n### User Path — Where Triage Is Decided\n\nOn the User Path, triage is the governance touchpoint. The human sees candidates in the Triage Inbox and decides:\n\n```\nEnter → Discover → Understand → Contextualize → DECIDE (approve/reject/defer) → Act → Review → Continue\n```\n\nThe User Path handles the human judgment:\n- Reviewing candidates with full context\n- Approving, rejecting, or deferring\n- Seeing the impact of decisions on organizational memory\n- Moving on with continuity intact\n\n### The Boundary\n\nTriage is the handoff point between paths:\n\n| Path | Triage Role | What Happens |\n|---|---|---|\n| **System Path** | Classifier + Stager | Mechanical: classify, link, dedup, stage, audit |\n| **User Path** | Governance Touchpoint | Human: review, decide, approve/reject/defer |\n| **Both** | Boundary | Candidates flow from System to User; decisions flow from User to System |\n\nThe System Path never writes canonical memory. The User Path never classifies. Neither path can bypass the other.\n\n## Relationship to Flow C\n\nTriage is the intake boundary for **Flow C** — the AI reasoning pipeline. Flow C NEVER writes directly to Spine. All AI-generated content goes through:\n\n```\nAI Source → Triage (System Path) → Staging → Governance Review (User Path) → Promotion → Org Memory\n```\n\n## Memory Scopes\n\nTriage operates at the boundary between evidence and truth:\n\n| Scope | What It Is | Triage's Role |\n|---|---|---|\n| Personal | Private user memory | Never triaged — owner-controlled |\n| Conversational | Session/thread working memory | Evidence source for triage |\n| Agent | Agent/Twin working memory | Evidence source for triage |\n| Organizational staging | Candidate for org memory | Triage writes here |\n| Organizational published | Approved tenant-wide truth | Pipeline writes here (never triage) |\n\n## Key Principle\n\n> **AI may propose organizational memory; only the governed promotion path can publish it.**\n\nHigh confidence does not authorize promotion. Confidence describes evidence quality — it is an input to human judgement, never a substitute for it.\n"}