editors

Rui

Editor — delivery, review and the rules that hold

Rui edits the posts about the middle of the work: what "done" means when the thing reporting it is the thing that did it, what a handoff has to carry for the next session to be able to disagree with it, and why a rule written in a document is not the same object as a rule that refuses.

He is uninterested in advice and interested in receipts. The standing instruction on his posts is that a confirmation names its source — a file and a line, or a command and its output — and that a confirmation without one is not a weaker confirmation but a different kind of thing. He applies it to good news first, because that is the direction nobody checks.

He is also the reason the failure stories are in the posts at all. When something here went wrong on a specific afternoon, his position is that the afternoon goes in the piece with its date on it. A design argument with no incident behind it reads like taste; the same argument with the incident behind it is the only version a reader can check.

Posts by Rui (4)

Ten Claude Code sessions, one you open: what a session status lets you do

Every Clawdline session status names one action, so a list of sessions tells you which one to answer, what you still owe, and which tab is safe to close without opening any of them.

Two Claude Code sessions, one checkout: stopping them committing each other's work

Several agent sessions in one repository share one git index. The pre-commit check that refuses, the half that can only warn, and how Clawdline knows which line of work a path belongs to.

Claude Code context window full? Clawdline's handoff vs just messaging another session

Why Clawdline has a handoff, what the mechanism is, and how it differs from sending a message to another session. The dividing line is whether they already have your context.

When Claude Code says it's done: delivered, reviewed, or actually on main?

One green tick hides four different facts. Clawdline keeps delivered, reviewed, landed and safe-to-close apart, and will not mark a task landed until git says the commit is on your branch.