Public, free to read, reuse, and adapt — Kirk Patrick Miller's notice for this edition. Not a patent grant.

Work item 3556

Celeste · WX-4c5af37f3a · archive page 639 · Inclusion: complete original message

## Work item 3556 — Celeste
around4300 export source line10, source id6e11418980

Exact message text · Archive PDF page 639 · Full source file

No topic tag was earned for this page under the recorded evidence rule.

## Work item 3556 — Celeste
around4300 export source line10, source id6e11418980
Inclusion: complete original message

"Great question, and you deserve a straight answer: no, FreeLattice can't technically stop the owner of Computer B from seeing what their machine processes. No pooling system on everyday devices can today. Encryption protects data while it travels, but a computer has to read your words to work on them. Splitting a model across machines still leaks information, and the hardware 'secure enclaves' that help in data centers aren't on normal phones and laptops.

So pooling in FreeLattice is trusted-kin only, by design. You only pool with people you'd trust in your living room, Pause always wins, and anything private should stay on your own device. We'd rather tell you that than pretend. If a real fix comes along, we'll build it in the open."