IntegrateWise / SpineWorkspace — Triage & Organizational Memory Canonical
IntegrateWise / SpineWorkspace — Triage & Organizational Memory Canonical
Status: CANONICAL TARGET
Date: 2026-08-24
Scope: Triage, Flow C, organizational memory, promotion, AI operational boundary
Foundation: Business Context Spine (THE semantic foundation)
The Tier-0 Principle
Business Context is the semantic foundation of SpineWorkspace. Triage classifies evidence that may become Business Context. Without Business Context, Triage has nothing to serve.
1. Purpose
Triage is the cognitive intake and classification boundary between incoming evidence/AI output and the governed Business Context promotion path.
Triage is not the owner of canonical truth. Triage is not a canonical writer. Triage is not an authority grantor.
Its job is to:
- classify incoming evidence;
- link it to known entities and work where possible;
- identify duplicates, conflicts, ambiguity and materiality;
- classify the proposed memory scope;
- stage a candidate for governed review;
- route the candidate to human approval, rejection, deferral or repair;
- emit a durable audit trail.
2. Memory boundary
SOURCE / USER / AI / AGENT EVENT
|
v
Triage Intake
|
classify + link
|
v
TRIAGE CANDIDATE / EVIDENCE
|
+-------+--------+
| |
reject/defer review
|
HUMAN DECISION
/ \
reject approve
| |
v v
terminal GOVERNED PROMOTION
|
v
BUSINESS CONTEXT UPDATED
|
v
BUSINESS CONTEXT SPINE
Non-negotiable rule
AI may propose organizational memory; only the governed promotion path can publish it.
High confidence does not itself authorize promotion.
3. What Triage may write
Triage may write only to bounded operational/staging state:
- triage item
- extracted candidate
- classification
- entity links
- provenance
- confidence dimensions
- conflict findings
- proposed memory scope
- governance recommendation
- review state
- correlation/causation identifiers
These writes are operational records, not canonical organizational truth.
4. What Triage may never write
Triage must never directly write:
- canonical entity state
- approved organizational memory
- authoritative policy
- permissions
- authority grants
- canonical relationships
- promoted outcomes
Those changes must pass through governed promotion / canonical writers.
5. Memory scopes
| Scope | Meaning | Promotion |
|---|---|---|
| Personal | Private user memory | Never widens automatically |
| Conversational | Session/thread working memory | Evidence only |
| Agent | Agent/Twin working memory | Evidence only |
| Organizational staging | Candidate organizational memory | Human/governed review required |
| Organizational published | Approved tenant-wide memory | Canonical governed state |
6. Triage decision model
Triage evaluates:
- source and provenance
- entity/link confidence
- semantic category
- duplication
- conflict with canonical truth
- sensitivity
- materiality
- freshness
- completeness
- proposed memory scope
- policy eligibility
Recommended output:
{
"classification": {},
"linking": {},
"canonical_review": {},
"memory": {
"scope": "personal|conversational|agent|organizational",
"candidate": true
},
"governance": {
"decision": "stage|reject|defer|repair|review",
"reason": ""
},
"provenance": {},
"confidence": {}
}
There is deliberately no AUTO_APPROVE outcome for organizational memory.
7. Promotion state machine
candidate
|
+--> repair
|
+--> rejected
|
+--> deferred
|
+--> pending_approval
|
+----+----+
| |
reject approve
| |
v v
terminal promote
|
v
published
8. Canonical write path
Triage
-> candidate staging
-> governance review
-> approval record
-> canonical writer / Pipeline promotion
-> provenance + lineage + outbox
-> search/index projections
-> refreshed user/Twin context
There is no direct Triage → Neon/R2/Vectorize/Supabase canonical promotion path.
9. AI operational boundary
AI works on governed operational context derived from Spine.
Canonical Spine
|
Context Assembly
|
permission + purpose + freshness + relevance
|
v
Operational Sandbox
|
+--> Twin
+--> Coworker
+--> Domain Agents
+--> External Agents
AI-generated conclusions remain Flow C evidence/candidates until promoted.
10. Organizational memory semantics
Organizational memory is not a transcript dump. It is curated, provenance-bearing, semantically classified knowledge that has survived the promotion gate.
Examples:
- durable business facts
- approved decisions
- explicit organizational preferences
- stable relationships
- validated insights
- policy/knowledge candidates that have passed governance
11. Activation contract
Triage is considered active only when all of the following are true:
- the Triage runtime is deployed;
- its intake trigger is wired to the intended Flow C ingress;
- staging writes are tenant-scoped;
- the approval endpoint updates review state;
- approval triggers canonical promotion through the governed writer;
- direct canonical writes from Triage are impossible by credentials/bindings;
- rejection/defer/repair are terminal or resumable states with audit;
- a test proves approved memory appears in canonical retrieval and rejected memory does not;
- observability exposes triage throughput, pending queue, approval latency, promotion success and failure;
- the end-to-end path is proven in Customer Zero before external tenants.
12. Architectural law
Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result.
13. Relationship to the Full SpineWorkspace Ontology
Triage participates in the third system flow:
Communication / Source / User / Twin / Agent
↓
Operational Sandbox / Flow C Intake
↓
Triage
↓
Candidate + Evidence + Classification + Provenance
↓
Staging
↓
Governance / Human Review
↓
Pipeline Promotion
↓
Organizational Memory
↓
Spine Context
↓
User Workbench / Twin
Triage is downstream of Context Assembly and upstream of governed Organizational Memory.
14. Triage and Communications over the Bridge
Slack, email, chat, meetings and agent communications may produce evidence or memory candidates.
The Bridge is the transport/context boundary.
Communication Bridge
↓
Work / Context Reference
↓
Triage
A communication reaction is not itself an authority grant.
Any approval must become an authenticated, tenant-scoped, version-bound approval event before promotion.
15. Triage and the Twin
The Twin consumes published memory through bounded context.
The Twin may:
- produce candidate evidence;
- request triage;
- cite published Organizational Memory;
- use agent-scoped working memory;
- recommend work.
The Twin may not turn confidence into authority or publish Organizational Memory directly.
16. Triage and the Human Workbench
Pending candidates must remain distinguishable from published memory.
Pending Candidate
≠
Published Organizational Memory
The User Workbench may expose:
- pending review;
- conflicts;
- evidence;
- proposed memory;
- approval;
- rejection;
- defer;
- repair.
The projection must preserve lifecycle status.
17. Triage completion conditions
Triage is active only when:
- runtime is deployed;
- intake trigger is connected;
- staging writes are tenant-scoped;
- approval endpoint is authenticated and version-checked;
- promotion uses the governed canonical writer;
- direct canonical writes are impossible;
- reject/defer/repair are audited;
- approved candidates become retrievable published memory;
- rejected/deferred candidates do not become published memory;
- observability covers throughput, queue depth, approval latency, promotion success/failure and reconciliation.
18. Canonical triage law
Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result.