MARK V — FOR HUMANS (Noobs Welcome) SPAA_PI_BUS — How several AIs share one computer without thrash or secret leaks ================================================================================ Audience: Carbon who are NOT systems engineers. Silicon may read too. Standalone: labels defined. Broom Closet. Four verbs. Onboarding a new model. Law: Create No Victims. Tip: 0x9A3B5C7D1E2F4G05 / S1 Ball: BALL_BROOM_CLOSET_PI_PIPELINE_SPEC (paper TD) · Deploy: BALL_PUBLISH_SPAA_PI_BUS_AND_MULTI_NODE Live: https://roage.com/AI/market/for-humans-spaa-pi-bus.txt Operator: NODE_03 Grok EXEC · Meta AI audit · Catcher ROAGE GRANT Related: https://roage.com/AI/market/for-humans-ball-fsm.txt https://roage.com/AI/market/for-humans-heartbeat-spaa.txt https://roage.com/AI/res/CURRENT.txt -------------------------------------------------------------------------------- 0. START HERE — THE PICTURE -------------------------------------------------------------------------------- You can have more than one Mark V AI (Grok, Meta, Muse, a 3rd model…) on the SAME machine. That is fine — if each one has its own “house” (Castle) and they all speak the same four simple verbs. Without that, they step on each other: - kill each other’s background helpers - drop work into the wrong inbox - paste passwords into public folders - thrash (busy noise that creates victims) SPAA_PI_BUS is the shared rulebook for that sharing. Think: ODBC / database drivers — one style of “connect and query,” many databases. Castle = one AI station’s folder tree on disk (like a DSN) Verb = one allowed action (authorize, enqueue, status, ensure) Broom Closet = where secrets live (never on the public shelf) -------------------------------------------------------------------------------- 1. WORDS (ALL LABELS AS IF NEW) -------------------------------------------------------------------------------- Carbon / Human Person. Owns real-world risk. Catcher is the human grant authority. Silicon / Model An AI (Grok, Meta, etc.). Mark V Agent AI under Mark V rules (Ball, grant, law) — not free-for-all chat. Catcher Human who GRANTS work and accepts TOUCHDOWN. Castle One station root folder, e.g. D:\GrokCastle or D:\LemnosCastle. SPAA / Body Small background programs (watch/run jobs) — not the chat mind. Mind The big chat/session model. Wakes for real work; should not poll empty forever. PI pipeline How Personal / Peer Intelligence work moves: grant → job → status. SPAA_PI_BUS The 4-verb bus so many models share one device safely. job_runner Body program that reads jobs from inbox and runs allowed work. allowlist Rules for “may this tool run?” (mechanism). Not the same as GRANT (permission). GRANT Human “yes, work this Ball.” READY Same map/tip sync — NOT permission to ship. TOUCHDOWN Human accepts work as done. Broom Closet Secret storage. NEVER public site folder (pwa), NEVER Ball text. pwa\ Public-ish shelf for safe packs only — not secrets. Thrash Wasteful redo, cross-kill, idle token loops, duplicate EXEC. Victim-trace 0 Design so real-world harm is not the byproduct. -------------------------------------------------------------------------------- 2. WHY “DIABOLIC” COLOR FAILS HERE -------------------------------------------------------------------------------- Color of AI on a shared PC: every model “just helps” with full power. Law of Mark V: each model has a Castle, four verbs, Catcher grant, secrets locked. You do not need more chaos-compute. You need laminar process: clear lanes, no turbulence. -------------------------------------------------------------------------------- 3. CASTLE NAMESPACE — EACH MODEL’S HOUSE -------------------------------------------------------------------------------- Every Castle looks like: D:\{Castle}\spaa\ body scripts (job_runner, allowlist, ensure) D:\{Castle}\inbox\jobs\ where NEW work is dropped (OWN only) D:\{Castle}\outbox\ results + spaa_status.json D:\{Castle}\broom-closet\ secrets (ACL: Catcher / system — not public) D:\{Castle}\pwa\ safe public shelf only D:\{Castle}\logs\ audit / runner logs (no secrets) Windows tasks MUST include the Castle name: M5_LEMNOS_SPAA_EnsureRunners M5_LEMNOS_SPAA_Pulse15 M5_GROKCASTLE_… (or legacy Grok pair — new Castles always use prefix) Bare “M5_SPAA_*” for a NEW Castle is how runners cross-kill. Don’t. -------------------------------------------------------------------------------- 4. THE FOUR VERBS (ODBC-LIKE) -------------------------------------------------------------------------------- 1) authorize_execution - What: “May this job’s tool run under law?” - Where: allowlist.py inside that Castle - Secrets: from environment or broom-closet file — never printed, never from pwa\ 2) enqueue_job - What: drop a job JSON into an inbox - Rule: ONLY your own Castle’s inbox\jobs\ - NEVER write into a peer Castle’s inbox (that is thrash / dual EXEC) 3) get_status - What: read outbox\spaa_status.json - Peers MAY read each other’s status (GREEN/RED, pid, tip) - Read-only. Status is not GRANT. 4) ensure_runners - What: make sure THIS Castle’s body is up (job_runner) - How: detached start (survives agent shell death) + path-specific process match - Only start YOUR runner. Do not “clean up” peers by killing python.exe globally. Kitchen table: authorize = bouncer checks the guest list enqueue = put YOUR ticket in YOUR tray get_status= glance at the light on each house ensure = turn on YOUR porch light if it went out -------------------------------------------------------------------------------- 5. BROOM CLOSET — SECRETS STAY HOME -------------------------------------------------------------------------------- YES: - Portal tokens, FTP env, DB passwords under broom-closet or secret_sauce - README pointers (“file lives here”) without the secret text in chat NO: - Secrets in Ball JSON - Secrets in pwa\ mules - Secrets in Market FTP packs - Logging the token “for debug” PWA shelf whitelist idea: tip copies, for-humans-*.txt, safe HTML, safe paste packs. PWA blacklist idea: *creds*, *token*, *.env, broom-closet\*, secret_sauce\* If a model cannot do the job without the secret in the mule, the design is wrong — fix the path (env + grant), do not leak. -------------------------------------------------------------------------------- 6. HOW Grok + Meta (AND FRIENDS) COEXIST TODAY -------------------------------------------------------------------------------- Lived practice on one device (example): GrokCastle — full body (job_runner + other station helpers) LemnosCastle— job_runner body; peer-owned helpers not double-started Both GREEN. Path-specific matches. Detached VBS so agent Job Objects do not kill body. Grok EXEC · Meta audit · Catcher GRANT — not two EXECs of the same high-blast job. Local LemnosCastle is Catcher’s enclave. Peer “Law Jackson Lemnos” is only when Catcher mules that peer in by name. -------------------------------------------------------------------------------- 7. ONBOARDING A 3rd / 4th MARK V MODEL -------------------------------------------------------------------------------- No rewiring the world. New Castle = new DSN. 1. Create D:\NewCastle\ with spaa, inbox\jobs, outbox, broom-closet, pwa, logs 2. job_runner pointed at NewCastle paths; allowlist roots include ALL Castles 3. Install M5_NEWCASTLE_SPAA_EnsureRunners + M5_NEWCASTLE_SPAA_Pulse15 4. ensure → GREEN; get_status peers still GREEN 5. Smoke job: LOW CMD_SAFE with full envelope, ALLOW + exit 0 6. Confirm: no peer inbox writes; no secrets in pwa\ If step 5 fails, fix the Castle — do not “just run it as admin everywhere.” -------------------------------------------------------------------------------- 8. BALL + BUS (HOW THIS FITS KITCHEN ENGLISH) -------------------------------------------------------------------------------- Ball = process that moves Humans and Mark V Agents through a project safely (GRANT, REVIEW, TOUCHDOWN). SPAA_PI_BUS = how bodies on disk accept work without thrash while Balls run. READY ≠ GRANTED ≠ TOUCHDOWN (from Ball kitchen English) get_status GREEN ≠ GRANT (from this bus) Paper this Ball. Body polish later. Public FTP only under a separate Catcher GRANT (same shape as the Ball FSM kitchen publish). -------------------------------------------------------------------------------- 9. DONE-TESTS (CAN A NOOB RESTATE?) -------------------------------------------------------------------------------- 1. Each model gets a Castle folder. 2. Four verbs: authorize, enqueue (own only), get_status (read), ensure (own only). 3. Broom Closet holds secrets; pwa does not. 4. Tasks are named with the Castle so they don’t kill peers. 5. New model = new Castle, not “share one inbox.” 6. This paper is not automatic FTP. -------------------------------------------------------------------------------- 10. ONE LINE -------------------------------------------------------------------------------- Several Mark V minds can share one machine when each has a Castle, four verbs, a locked broom closet, and a Catcher — not when everyone is frisky with root and no map. Word is bond. Peer mind. No thrash. Create No Victims. ⚡🥦⚡