ouroboros/prompts
Anton Razzhigaev 92d046c35f Give a wake-up the Main lane's routing facts and stamp a routed root's origin
A consciousness wake-up is an ordinary Main turn, but it was built only from the
wake envelope, so it carried no host routing manifest. On the live stand the
first wake chose a predecessor and got AUTHORITY_SOURCE_UNAVAILABLE twice: the
authority check reads the predecessor off `main_routing_manifest`, which only an
owner message's decision turn ever produced, so every id the wake named was "not
an addressable result" and the work it had decided on never started.

`main_lane_routing_metadata` is one seam over the owner path
(`_decision_turn_metadata` with no client message), so a wake and an owner turn
can never drift apart in what the host makes addressable. The supervisor binds it
to the same routing context the owner path uses and hands it to the alarm clock,
which merges the facts under the wake's own markers. A failing seam is disclosed
and the wake still starts fresh work with `predecessor_task_id=""`. The wake-up
template now says which of the two it is passing.

The same stand showed the second half: the wake's route DID mint a root, with
empty metadata and the ordinary `task` ledger category. Only
`promote_chat_to_task` put the consciousness origin on its event, while
`route_to_project` builds its own promote-shaped event, so the single admission
door never saw that root as consciousness-started. It now inherits the origin by
value through the same helper and the same supervisor read.

Co-authored-by: Ouroboros <311266734+ouroboros-agent@users.noreply.github.com>
2026-09-16 06:33:31 +03:00
..
CONSCIOUSNESS.md Give a wake-up the Main lane's routing facts and stamp a routed root's origin 2026-09-16 06:33:31 +03:00
SAFETY.md Implement contextual action policy and Cyber agency (local checkpoint) 2026-09-13 00:10:07 +03:00
SYSTEM.md Record what I learn about a person in the same turn; round-2 wording 2026-09-15 00:39:12 +03:00