Source
Meetings, sessions, corrections, obligations, and buyer evidence.
UNISON · 20 SEP 2026
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.
THE ROUTE
Meetings, sessions, corrections, obligations, and buyer evidence.
Classify the real obligation, preserve context, and name the authority.
Send exact work to an existing owner through an authorized route.
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.
SYSTEM LAYERS
Commitments + progress
Source meaning and producer / consumer / cursor alignment still need recovery.
Exact work + next action
The route is the intended execution handoff, not proof of a live end-to-end path.
Stale-work investigation
Targeted evidence acquisition and action-owner routing are still open.
Attention → context → action → result
Verified repair scope: readiness, identity checks, and guarded replay paths. A genuine post-release owner write remains unexercised.
Task integrity / reconciliation
Corrected Code bodies preserve IDs and avoid invented completion dates.
Scoped correction + learning
A stored correction is not learning until a later relevant action changes and is tested.
Improve, create, consolidate, or no change
Buyer decisions and site evidence stay upstream of page selection.
Content and design handoff
Intended / partial: full content/design acceptance remains unproven.
DELIVERY FORK
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.
VERIFIED BATCH
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.
NEXT ROUTES