{"slug":"triage/README","title":"Triage System — Complete Documentation","section":"triage","sectionLabel":"Triage","status":"canon","type":"document","path":"triage/README.mdx","bytes":2255,"description":"Index for the triage system documentation: the governed intake and classification boundary for organizational memory.","updated":"2026-08-24","source":"integratewise/Integratewise-docs-wiki","content":"\n\nThis directory contains the complete documentation for the IntegrateWise Triage system — the cognitive intake and classification boundary between incoming evidence and governed organizational memory.\n\n## Documentation Structure\n\n| Bucket | Document | Purpose |\n|---|---|---|\n| **Overview** | `01-OVERVIEW.mdx` | What triage is, why it exists, the canonical law |\n| **Execution Flow** | `02-EXECUTION_FLOW.mdx` | Step-by-step data flow from intake to org memory |\n| **Agents** | `03-TRIAGE_AGENTS.mdx` | All triage agents, their roles, and execution models |\n| **Intake Triggers** | `04-INTAKE_TRIGGERS.mdx` | What triggers triage and how data enters the system |\n| **Data Model** | `05-DATA_MODEL.mdx` | Schema, states, memory scopes, triage_items |\n| **Classification** | `06-CLASSIFICATION.mdx` | How triage classifies, links, evaluates conflicts |\n| **Governance** | `07-GOVERNANCE_BOUNDARY.mdx` | What triage can/cannot write, approval flow |\n| **Promotion** | `08-PROMOTION_PATH.mdx` | How approved candidates become organizational memory |\n| **Consolidation** | `09-MEMORY_CONSOLIDATION.mdx` | The scheduled consolidation pipeline |\n| **Activation** | `10-ACTIVATION_CONTRACT.mdx` | When triage is considered \"active\" |\n| **Code Map** | `11-CODE_MAP.mdx` | Where each responsibility lives in the codebase |\n| **Acceptance Tests** | `12-ACCEPTANCE_TESTS.mdx` | The 10 canonical acceptance tests |\n| **API Reference** | `13-API_REFERENCE.mdx` | All triage-related endpoints |\n| **Reference Docs** | `../architecture/_reference_*.md` | Original canonical specs (read-only) |\n\n## Architectural Law\n\n> **Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result.**\n\n## Quick Start\n\n1. Read `01-OVERVIEW.mdx` for the big picture\n2. Read `02-EXECUTION_FLOW.mdx` to understand the data path\n3. Read `11-CODE_MAP.mdx` to know where code lives\n4. Read `12-ACCEPTANCE_TESTS.mdx` to know what must pass\n"}