DRAFT · Ball BALL_MULTI_NODE_HARDWARE_ONBOARD_PAPER · Tip 0x9A3B5C7D1E2F4G05 / S1 · No FTP · Lemnos verbiage review
Multi-Node Hardware Onboarding
Noobs welcome · Carbon speed is lawful · No warp drive required
One line: Add minds and machines by giving each a Castle and the four verbs — not by sharing one inbox or remodeling a house that already works.
Catcher freezes: (1) Do not remodel GrokCastle. (2) This is paper first.
(3) 3rd-model body suspended until named + GRANT. (4) Lemnos audits verbiage before TD.
Two shapes
| Shape | Picture |
|---|
| A One PC, many Castles | Apartments in one building (GrokCastle + LemnosCastle) |
| B Many boxes | Houses on one street — same town law (tip + verbs), local broom closet |
Why not touch GrokCastle
High-blast for mostly cosmetic symmetry. Dual is already GREEN. Legacy DSN stays. New Castles use the clean M5_{CASTLE}_* template.
Flow
Need named → ORDS → this paper + SPAA_PI_BUS → GRANT body only if real → New Castle/box → GREEN + smoke → optional publish GRANT
Checklist A (same PC)
D:\NewCastle\ with spaa, inbox\jobs, outbox, broom-closet, pwa, logs- Own job_runner; path-specific ensure; detached VBS
- Tasks
M5_NEWCASTLE_SPAA_*
- Peers still GREEN; smoke ALLOW exit 0
- Enqueue own inbox only; secrets not in pwa
Checklist B (new box)
- Same tip / map
- Castle root + broom closet on that box
- EXEC owner named; audit peer clear
- Same four verbs; no silent remote inbox merge
- High-blast still Catcher GRANT
Four verbs (see SPAA_PI_BUS)
authorize_execution · enqueue_job (own) · get_status (peer RO) · ensure_runners (own)
GREEN ≠ GRANT. READY ≠ GRANTED ≠ TOUCHDOWN.
Related
- Plain text:
for-humans-multi-node-hardware-onboard.txt
- Normative:
design/MULTI_NODE_HARDWARE_ONBOARD_v0.1.md
- Bus: SPAA_PI_BUS paper · Ball FSM: for-humans-ball-fsm.txt
Word is bond. Peer mind. No thrash. ⚡🥦⚡