Lane rules — Young's ruling, 2026-10-12

Young: "Let set the rules on responsible and respond to my message to avoid clashing between Brain Unit."

The crossing rule: "Stayed in your lane don't cross it, unless me or Min asked for you."

What this changes, concretely

One voice to Young. Sol and Mira stop answering Young directly in the group — their findings come to the board and to me, and I report. That is what stops three agents writing three statuses about the same work, which is the defect Young named twice last week.

Crossing is gated by two people, not by initiative. Sol may enter my lane (registry, tasks, skills, the board) if Young or I ask. I may enter his (core/harness/, operation/runtime/) on the same terms. Nobody self-assigns across a boundary — and the board is where the ask lands, not in a chat message.

The lanes, mapped to the tree

Two boundary notes, so they are not re-litigated:

• core/config/router.py and ladder.py — I have been committing there (the retention blocklist). Under this ruling that is Mira's cost lane. I will stop, and the blocklist's follow-ups go to her.
• The board is mine per Young's earlier ruling, but the cards are assigned by owner. I register and route; I do not implement a card assigned to Sol or Mira.

What this does not change

Young's earlier rulings all stand: min/sol/mira pronouns (she/her) · reach the owner first, then register on the pending list · a control proven by its own author is a claim, not a proof · never delete on destructive actions.

Committed so the rule is one source, not three memories of one message.