mosaicstack/stack
25
0 Fork 1
Code Issues 404 Pull Requests 13 Packages Projects Releases 15 Wiki Activity

plans: row 190 brief scopes isolation to addressing on one uid, points to row 190b (Filbert N7, mos-0986)

Browse Source
This commit is contained in:
jason.woltje committed 2026-10-20 13:58:07 -05:00
1 parent 66bdd84b8f
commit 48ebee0ffe
1 file changed
+4 -2
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/2026-10-20_multi-instance.md
+4 -2
View File
@@ -12,8 +12,10 @@ before any code, as Q175 did. Then the build follows the design, with tests and
Two or more instances run side by side on dragon-lin. Each one has its own config file, data root (store, Two or more instances run side by side on dragon-lin. Each one has its own config file, data root (store,
broker.sock, host.lock, state, runs, sessions, workspaces), businesses, bus unit, Console unit and port, broker.sock, host.lock, state, runs, sessions, workspaces), businesses, bus unit, Console unit and port,
tester port, Discord unit, Claude session env file, stack-active pointer and activation log. Nothing one tester port, Discord unit, Claude session env file, stack-active pointer and activation log. No instance's
instance does can read or change another's state. The current instance keeps working unchanged: its commands, units or tools address another instance's state by default or by mistake. On one uid this is
addressing only, not a security boundary: a same-uid process can still read another instance's files.
Isolation against that is row 190b (#1693, mos-0986), one Linux user per instance. The current instance keeps working unchanged: its
config path, data root, unit names and ports stay as they are, and no re-pin is needed for it. config path, data root, unit names and ports stay as they are, and no re-pin is needed for it.
## Known single-instance points (GAP-MAP.md, measured at 9ae8c73ac) ## Known single-instance points (GAP-MAP.md, measured at 9ae8c73ac)