UNISON · 20 SEP 2026

One operating loop.
Useful work, not activity.

A small, public-safe map of how source, ownership, action, proof, and learning are meant to connect. It is a status view—not a claim that the whole system is live.

Current boundaryReliability repairs have verified pieces of the route. LCM is degraded, and the full content / design loop remains unaccepted.

THE ROUTE

From signal to useful result

01

Source

Meetings, sessions, corrections, obligations, and buyer evidence.

02

Understand

Classify the real obligation, preserve context, and name the authority.

03

Act

Send exact work to an existing owner through an authorized route.

04

Prove

Read back the destination and acceptance against the original result.

Then return the result to MTL / KITCHEN, and only call it learning when a later relevant action demonstrably improves.

Meetings→NATE→Navigator→existing owner→proof→MTL / KITCHENSessions / corrections → Check-in → Navigator is a separate input. Crack Finder is intended to add targeted evidence into the route; that binding is not connected.

SYSTEM LAYERS

What is known right now

Verified repairIntended / partialNot connected

NATE

Intended / partial

Commitments + progress

Source meaning and producer / consumer / cursor alignment still need recovery.

Navigator

Intended / partial

Exact work + next action

The route is the intended execution handoff, not proof of a live end-to-end path.

Crack Finder

Not connected

Stale-work investigation

Targeted evidence acquisition and action-owner routing are still open.

KITCHEN

Verified repair

Attention → context → action → result

Verified repair scope: readiness, identity checks, and guarded replay paths. A genuine post-release owner write remains unexercised.

Garth

Verified repair

Task integrity / reconciliation

Corrected Code bodies preserve IDs and avoid invented completion dates.

CLIO

Intended / partial

Scoped correction + learning

A stored correction is not learning until a later relevant action changes and is tested.

CODI / OTIS

Intended / partial

Improve, create, consolidate, or no change

Buyer decisions and site evidence stay upstream of page selection.

COUGAR + HONE → CONI → POLISH

Intended / partial

Content and design handoff

Intended / partial: full content/design acceptance remains unproven.

DELIVERY FORK

Handoff and release are different decisions

Research can produce a writer handoff, or an explicitly approved downstream production route can be used. Approval does not automatically authorize end-to-end publishing. Rendered composition still needs actual acceptance.

Research / writer handoffORExplicitly approved production

VERIFIED BATCH

18 date cells, not 18 completions

One bounded repair restored 18 exact completion-date cells on tasks that were already complete. It did not close 18 tasks, change statuses, or establish that the whole operating loop works.

386focused tests passed
LCMstartup degraded by a database lock
0whole-system acceptance claims

NEXT ROUTES

The useful next fixes

01

LCM runtime

Apply the scoped source fix, review concurrent registration, then verify plugin registration—not only HTTP readiness.

02

NATE meaning

Account for dropped row instances against existing sources and obligations; do not turn them into new tasks.

03

Crack Finder + KITCHEN

Acquire targeted evidence, bind the existing coordinator and CLIO projection, then prove one useful obligation returns to the same task.

04

Correction learning

Trace one source-bound correction through the responsible route and a held-out recurrence test.

05

Page / site decisions

Keep buyer decision, supported answer, proof, and whole-site coverage upstream of page selection; judge the actual rendered artifact separately from code checks.