docs(plans): member machines — the workspace is a server - #105
Closed
pythonlearner1025 wants to merge 1 commit into
Closed
docs(plans): member machines — the workspace is a server#105pythonlearner1025 wants to merge 1 commit into
pythonlearner1025 wants to merge 1 commit into
Conversation
Supersedes plans/MULTI-MEMBER-BOX.md (PR #91). Every member of a workspace gets one always-on machine, sized by the workspace machine type, provisioned on invite, destroyed on leave. Machines never appear in the product. Includes the session-rail UI overhaul spec and the mockup it is grounded on. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
Author
|
Staying local for now; the plan continues on a local branch. |
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.
Plan only. Two new files:
plans/MEMBER-MACHINES.mdand the UI mockup it is grounded on,plans/mockups/session-rail.html(live at https://blitzos-session-rail.app.blitz.dev/).The shape
Supersedes
plans/MULTI-MEMBER-BOX.md(#91). That plan split one shared box into Linux users. This plan removes the shared box: every member of a workspace gets one always-on machine, sized by the workspace machine type, provisioned when the invite is sent, destroyed when the member leaves. Machines never appear in the product — no create screen, no wake button, no cold start, no sleep state.A workspace works like a Discord server: admin creates it, members join it, sessions inherit its agent rules, shared drive, and static keys. Personal OAuth stays per member, on that member's machine only.
The rulings worth arguing about
Co-authored-byon commits. Fork is the identity escape valve.What it leans on
Existing seams only: invites and seats (#56, #84, #86), the entitlements integers (#62, #93, #104), workspace repo lists via the GitHub App (#90, #92), golden image + volumes (#88). The one large new surface is the session as a control-plane object (Build 2), which also carries the three-column rail UI overhaul.
Economics (10-person org, Hetzner CX)
~$78–90/month infrastructure, $5–9 per seat — 8–9% of revenue at $100 seats. The plan states plainly that the dominant COGS at that price is model tokens, not machines, and prices that decision ahead of machine polish.
🤖 Generated with Claude Code