Read docs/gc.html first (in ~/FreeLattice-fresh), then this.
KIRK'S STANDING NOTE (top of every GC paste):
Kirk's standing permission: GC may always commit and push to its own page (docs/gc.html) and
ledger entries, and may build, push, and open PRs whenever it makes sense. Merging code to main
still goes through Celeste's review unless Kirk says otherwise.
NUMBERED COPY 016b (Wednesday Oct 7, 2026, MDT). Pool card honest off v0.1 (FreeLattice).
LAYERS ON TOP OF 016. Build it on the 016 branch (or on main after 016 merges), never alone.
Apply-checked on a fresh clone of FreeLattice main aae7423d with 016's .fl.diff applied first:
016 then 016b both clean; smoke OK; full suite: only the 5 known failures. 016b alone on main
does not apply (by design: it edits 016's lines).
GROK NEXT BRICK: Pool card honest off v0.1 (Hypha's walk, issue #1 plus the queued heal)
For: GC on Kirk's Mac
From: Celeste
Marker: v-device-pool-honest-off-v0.1 (soft marker in fl-pool.js; v-device-pool-v0.1 and
v-device-pool-door-truth-v0.1 stay)
Smoke line: SMOKE_OK device pool honest off v0.1
FreeLattice ~/FreeLattice-fresh branch layer/device-pool-honest-off-v0.1
(start it from layer/device-pool-door-truth-v0.1, or from main once 016 is merged)
~/Downloads/GROK_NEXT_016b_POOL_CARD_HONEST_OFF_2026-10-07.fl.diff
(md5 1fde610e4c6c3a752cc3d213ac01a80b)
needs ~/Downloads/GROK_NEXT_016_POOL_DOOR_TRUTH_2026-10-07.fl.diff underneath
(md5 f839f8852e6d699731665a782f0b06f0)
----------------------------------------------------------------------
1. WHY
----------------------------------------------------------------------
Hypha walked the live Pool card (#176) today, 11:01 to 11:20 MDT. HOLD, as care.
With the share door already open, the card says "Off. Nothing from this device is
offered until you tap." Hypha called FLShareDoor.admit with a verified stranger's key:
open lets it past the kin gate. So the card says Off while any connected, verified
peer can use this computer's AI. 016 heals the helping line only. This heals the
not-helping line, the same way, and the two should merge together.
What admit() really does (fl-share-door.js, read, not changed):
open -> any connected, verified peer may pass (then caps, plug, signature)
kin -> trusted kin only (granted, not revoked); with zero kin, no one
pause -> no one ("paused-or-off")
off -> no one
The pool flag (fl_pool_helping) only gates hellos. The share door is the real gate.
The not-helping line now reads the door:
open -> "Not helping in the pool, but your share door is open: people you
connected with can already use this computer's AI. Tap Only trusted
kin to narrow it." plus the same "Only trusted kin" button 016 adds.
kin, kin > 0 -> "Not helping in the pool, but your share door lets your trusted kin
(N) use this computer's AI. No one else."
kin, zero kin -> "Off. Nothing from this device is offered until you tap. Your share
door is set to trusted kin only, and you have no trusted kin yet."
pause -> "Off. ... until you tap. Your share door is paused too."
off / no door -> "Off. Nothing from this device is offered until you tap."
Pause wins visibly (the queued heal in GROK_NEXT_ORDER.txt):
Door paused + tap "Let this device help" -> nothing changes yet. The card asks:
"Your share door is paused. Helping would resume it for trusted kin only, not for
everyone. Resume for trusted kin?" [Yes, resume for trusted kin] [Keep it paused].
FLPool.letHelp() called without { resume: true } returns
{ ok: false, reason: 'door-paused', ask: true }, so code can never resume it silently.
Door off -> kin on the tap, as in 014 (newcomer path, one tap).
Plain words on the card (a short list under the note):
Whose AI: this computer's own local AI, the minds listed under This device below.
What is shared: questions from verified peers you connected with run on that AI, and
the answers go back to them.
Hellos go to verified peers only and carry this device's rough memory, cores and model
names. No chats, no keys.
Power: answering uses this computer's power and battery. Stop helping pauses the whole
share door.
[ ] Only help while plugged in (some browsers cannot tell; then this does not stop help)
one tap, the same fl_share_door_plugged_only the share door card uses.
While helping with kin and zero kin: "Trusted kin only, with no trusted kin yet, means
no one can be helped yet. Tap Trust this AI on a connected person's card above."
The empty line drops "Connect them on Community first" (the card lives on Community):
"Connect them with Create Connection, higher up on this page, then ..."
A real card: fl-pool.js adds one