Maintenance

The record maintains itself through triage

Nobody hand-edits 1,594 documents. A folder monitor ingests what changes, the triage agent classifies it, governance decides what becomes authority, and the promotion queue carries it across the gate. This page is the state of that loop.

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

Triage & Organizational Memory — Canonical Specification, §2

Who does what

Folder monitor
Ingests

Watches the memory folder and forwards every change. It records events; it decides nothing.

Triage agent
Classifies

Classifies, links, detects duplicates and conflicts, stages a candidate. Never writes canon.

Governance
Decides

A human approves, rejects, defers or sends back for repair. The only place authority is granted.

Twin
Consumes

Reads the published result. Twin never maintains the record it reasons over.

00Ingest — the folder monitor

Ingests

A watcher on the memory folder turns filesystem events into audit records. This is the only automatic path into the loop, and it stops at the audit log — it never reaches canon.

Watching
IntegrateWise - Memory/Conversation memory/
  1. 01
    chokidar watcher
    macOS process, file change detected
  2. 02
    HTTP POST
    signed with FOLDER_WATCHER_KEY
  3. 03
    Folder Watcher DO
    Cloudflare Durable Object
  4. 04
    audit-handler.ts
    D1 spine_audit_log + AI Search
What it feeds
  • Real-time session log processing
  • Spine audit log ingestion
  • Triage handoff documents
  • Agent continuity protocol

The monitor is a bridge, not a writer. Its output is an audit event — evidence for triage, never a promotion.

01Triage — the backlog

Classifies
1,444
Unclassified
390
Duplicate groups
29
Sections without canon
29
Superseded

Duplicate titles858 docs

The same title in more than one section. Triage cannot resolve these — it stages them for a decision about which copy is authoritative.

Showing 8 of 390

Sections without canon1,233 docs

Sections holding documents but no authority. Everything here is a claim that nothing governs.

Showing 8 of 29

02Promotion queue — the gate

Decides

Every candidate sits in exactly one state. There is deliberately no auto-approve for organizational memory — high confidence does not itself authorize promotion.

candidate
1,444docs

Ingested, not yet classified. Nothing here can be promoted.

pending_approval
390groups

Conflict staged with a recommendation. Awaiting a human decision.

repair
29sections

No canon exists to promote into. Sent back for a charter.

deferred
29docs

Replaced, but the successor is unrecorded. Resumable.

rejectedterminal
0items

Terminal. Retained with reason and audit trail.

publishedterminal
121docs

Passed the gate. This is the only state Twin may read as truth.

27ADRs against 76 canon documents

Canon states that changing a canon document requires an ADR. The record carries 76 canon documents and 27 ADRs — so most canon has no recorded decision behind it. This is the largest governance gap in the corpus, and triage cannot close it.

Open canon section

03Published — what the record holds

Consumed
76
canon
4.8%
45
current
2.8%
29
superseded
1.8%
1,444
unclassified
90.6%

Superseded, awaiting a successor link

04Book of records

Continuity

The loop now runs on a schedule and its output survives the request that produced it. Each run fingerprints the corpus, stages what triage cannot decide, and appends entries to a durable record. An entry only counts if its provenance cites something checkable.

1.0
Schema version
2026-11-03
Record updated
1,087
Entries held
10
Awaiting decision

Pillars

Every entry belongs to exactly one pillar. The pillar is what the record is about, not where the file happens to live.

  • Memory342
    memory
  • Continuity6
    continuity
  • Governance58
    governance
  • One Surface319
    one-surface
  • Operating Environment362
    operating-environment

Latest entries1,087 total

Each entry carries the fingerprint it was observed at, so a later run can prove the claim still holds.

Staged by triage, awaiting governance

Triage may stage, link and flag. It may never promote. These items are durable now — they survive the run that found them.

index2 documents resolve to the same slugrepair
operations/DE_SUPABASE_MIGRATION2 documents resolve to the same slugrepair
operations/data-recovery2 documents resolve to the same slugrepair
operations/deployment-and-rollback2 documents resolve to the same slugrepair
quickstart2 documents resolve to the same slugrepair
business/README3 copies across business, getting-started, _rootpending_approval
indexNo declared status in "_root"candidate
indexNo declared status in "_root"candidate

Run log

2026-11-03completedwrun_01M6GZ28A11YEJHKSK8V4SB6EN210
2026-11-03completedwrun_01M6GYZ2NSN6XECJZYCWCG5SCB10941386
2026-11-03failedwrun_01M6GYWM1WZYD546275A1PEB6H00
2026-11-03failedwrun_01M6GYWKW2G9KB9WB846DVXQZC00

What still needs a human

The loop runs and the record persists, but promotion is still manual by design. Triage stages candidates and the workflow can never move one to published. The approval record and the ADR gap remain open — the activation contract in §12 lists the conditions still unmet.

Agent contractRead the spec