Triage System — Complete Documentation

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

Documentation Structure

Bucket	Document	Purpose
Overview	`01-OVERVIEW.mdx`	What triage is, why it exists, the canonical law
Execution Flow	`02-EXECUTION_FLOW.mdx`	Step-by-step data flow from intake to org memory
Agents	`03-TRIAGE_AGENTS.mdx`	All triage agents, their roles, and execution models
Intake Triggers	`04-INTAKE_TRIGGERS.mdx`	What triggers triage and how data enters the system
Data Model	`05-DATA_MODEL.mdx`	Schema, states, memory scopes, triage_items
Classification	`06-CLASSIFICATION.mdx`	How triage classifies, links, evaluates conflicts
Governance	`07-GOVERNANCE_BOUNDARY.mdx`	What triage can/cannot write, approval flow
Promotion	`08-PROMOTION_PATH.mdx`	How approved candidates become organizational memory
Consolidation	`09-MEMORY_CONSOLIDATION.mdx`	The scheduled consolidation pipeline
Activation	`10-ACTIVATION_CONTRACT.mdx`	When triage is considered “active”
Code Map	`11-CODE_MAP.mdx`	Where each responsibility lives in the codebase
Acceptance Tests	`12-ACCEPTANCE_TESTS.mdx`	The 10 canonical acceptance tests
API Reference	`13-API_REFERENCE.mdx`	All triage-related endpoints
Reference Docs	`../architecture/_reference_*.md`	Original canonical specs (read-only)

Architectural Law

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

Quick Start

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