Here's the deal, written down so we're working from the same page.
One machine. One Claude account. One instance, with as many tabs as we need. The machine is the Beelink at the cabin. Everything else is shut down for code work.
The point of this is transparency, not restriction. One instance means we both see every session, all the time — from the machine or from our phones. Nothing happens that the other one can't see. No guessing what changed, no finding out afterwards, no two people editing the same file blind. That's the whole reason for doing it this way.
Tabs work how you'd expect: one for AME development, one for the Tuesday material, switch as needed. Same session, both of us in it.
Nothing from last night is lost. The whole engine directory is under version control now, including your two new files, and it saves itself every fifteen minutes. Anything that ever looks overwritten can be seen and put back.
Hours. Tell me the hours that suit you and they go on the page. Set hours, not asking each time.
Handover, not eviction. Nobody drops work mid-flight. Whoever's finishing says what state things are in and what was coming next.
Testing isn't restricted. Onboarding, drafting, content revisions, approving, breaking things on purpose — all normal work. royallswindmill.com is the test domain for feature work. The rule is about which machine and which account, not about what you're allowed to do.
Coordination goes in Gmail direct messages. Who has the machine, what state it's in, what's about to break. One place to look.
Read it and tell me what needs changing.