CLAUDE.md: route owner questions to the Liaison and pushes to the Lander, when those seats are running - #532
Merged
Merged
Conversation
…rough the Lander Owner-set 2026-08-22, in their words: all sessions should send issues and questions to the owner via the Liaison whenever a Liaison session is running, and send all push, merge and similar to the Lander whenever a Lander session is running. Sited in CLAUDE.md rather than the vault role playbooks because it binds EVERY session, including undeclared ones that never read a playbook. A rule for "all sessions" has to live where all sessions read. Names the check instead of asserting the condition: fleet.ps1 prints a SEAT column and a STATE column, so "is a Lander running" is one command rather than a judgement. Verified by running it -- liaison and LANDER both showed RUNNING at 20:49Z. Carries the casing trap, measured in that same render: the live rows read liaison, LANDER, Steward and asvs-tracker -- four seats, four casings. A case-sensitive test for "lander" returns nothing and reports it as "no Lander running", which is a false negative shaped exactly like a clean answer. States what the routing does NOT do. The owner still approves every push, PR and merge; the Lander executes an approved action and does not authorise one, and handing it a branch does not convert an unapproved push into an approved one. Without that sentence the rule reads as a transfer of authority, which is not what was asked for.
wshallwshall
enabled auto-merge (squash)
August 22, 2026 23:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authored by the Liaison seat, routed here for push under the rule it documents. One file,
CLAUDE.md, +33/-0. No code, no tests, no ledger numbers cited or allocated.What it implements
An owner instruction of 2026-08-22: send issues and questions for the owner to the Liaison whenever one is running, and send push, PR and merge to the Lander whenever one is running. Both routes are conditional on that seat actually being live; with no such seat the old path stands and neither is a required hop.
The half that matters most
Routing is not authority. The owner still approves every push, PR and merge. The Lander executes an approved action; it does not authorise one, and handing it a branch does not convert an unapproved push into an approved one. The same holds for the Liaison: it compresses and presents a question, it does not answer one.
The text also carries a measured trap: on 2026-08-22 the live
fleet.ps1rows readliaison,LANDER,Stewardandasvs-tracker-- four casings in one render. A case-sensitive test forlanderfinds nothing and reports it as "no Lander running", which is the failure that looks like a clean answer.Why this took a decision rather than a push
The commit writes an owner instruction into the file every session reads, and the Lander held it only second-hand. Only the owner can confirm their own words were those words -- a kind of human-only that is about verification rather than authority.
Raised through the Liaison at the owner's own direction. The Liaison recused from recommending, having authored the text, and instead showed the owner the exact delta between their words and the commit's: the owner said "send all push, merge, etc." and the expansion of
etc.to "a push, PR, or merge" was the Liaison's wording, not theirs. Named as theirs, with a hold offered. The owner chose to land as written, so the expansion is adopted rather than paraphrased.Owner's answer, relayed: land as written -- the Lander's pick.
Queue position
Opened unarmed, behind #529 and #458. Arming a third PR now would only re-BEHIND the two ahead of it.
Verified before pushing:
d8ce9727is the branch tip, 0 behind / 1 ahead oforigin/main,CLAUDE.mdalone.