🛰 Scan Tiles & the Healing Loop
Ask one question of a whole fleet with a single frame. Then only touch what the answer says needs touching — and watch the estate go quiet by itself.
Analogy: a group chat for chores. Mom posts ONE message
(“everyone check your room”), each kid replies to that message with what they found,
and the thread itself becomes the checklist. Next week she doesn't re-inspect the whole
house — she reads the old thread and only knocks on the doors that changed.
findings: —
work spent this round: 0
full-rescan cost would be: 5
ticks: 0
The chain — every line is a frame; children hold the tile's fingerprint.
What am I looking at? The scan tile is one frame; every
device answers with a child frame fingerprint-linked to it, and the merged report's payload
(the data exhaust) is the ONLY to-do list for the next step — devices with nothing
wrong cost zero (they grey out; the work meter doesn't move for them). Scan → heal →
scan again: when two ticks in a row find nothing new, the loop declares
converged and goes quiet. That's §3.1–3.3 of the paper — and the real estate run
went 66 findings → healed floor → quiet, with no human input.