Canon

Triage System — Complete Documentation

Index for the triage system documentation: the governed intake and classification boundary for organizational memory.

This directory contains the complete documentation for the IntegrateWise Triage system — the cognitive intake and classification boundary between incoming evidence and governed organizational memory.

Documentation Structure

BucketDocumentPurpose
Overview01-OVERVIEW.mdxWhat triage is, why it exists, the canonical law
Execution Flow02-EXECUTION_FLOW.mdxStep-by-step data flow from intake to org memory
Agents03-TRIAGE_AGENTS.mdxAll triage agents, their roles, and execution models
Intake Triggers04-INTAKE_TRIGGERS.mdxWhat triggers triage and how data enters the system
Data Model05-DATA_MODEL.mdxSchema, states, memory scopes, triage_items
Classification06-CLASSIFICATION.mdxHow triage classifies, links, evaluates conflicts
Governance07-GOVERNANCE_BOUNDARY.mdxWhat triage can/cannot write, approval flow
Promotion08-PROMOTION_PATH.mdxHow approved candidates become organizational memory
Consolidation09-MEMORY_CONSOLIDATION.mdxThe scheduled consolidation pipeline
Activation10-ACTIVATION_CONTRACT.mdxWhen triage is considered "active"
Code Map11-CODE_MAP.mdxWhere each responsibility lives in the codebase
Acceptance Tests12-ACCEPTANCE_TESTS.mdxThe 10 canonical acceptance tests
API Reference13-API_REFERENCE.mdxAll triage-related endpoints
Reference Docs../architecture/_reference_*.mdOriginal canonical specs (read-only)

Architectural Law

Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result.

Quick Start

  1. Read 01-OVERVIEW.mdx for the big picture
  2. Read 02-EXECUTION_FLOW.mdx to understand the data path
  3. Read 11-CODE_MAP.mdx to know where code lives
  4. Read 12-ACCEPTANCE_TESTS.mdx to know what must pass