Which Blinks are in your AI's memory — the status icons explained

What you see

In the Blink Library, every Blink now carries a small three-icon cluster just before its name:

• Memory icon (sparkles) — green means this Blink is in your AI's memory and up to date. Amber means it is in memory but you edited it afterwards, so the change is still waiting for the next memory refresh. Grey means it has not entered memory yet.
• Files icon (paperclip) — whether the content of the Blink's attached files is in your AI's memory. Green means it is; amber means the files are there but their content has not entered memory yet (it joins at the next refresh, on plans that include attachment reading).
• Privacy icon (eye) — an eye with a slash means you marked this Blink as private, so the AI does not read it at all.

Click the cluster to open a small panel with the details: when the Blink was added to memory, whether that happened during a refresh you asked for or an automatic background refresh, and whether later edits are reflected or still waiting.

On the Blink's own page

Each Blink's profile page ends with a Memory section that tells the same story in full sentences — for example: "This Blink entered your AI memory on Sep 8, 09:14, during a refresh you asked for. It has not changed since — the memory copy is current." No clicking needed.

Honest by design

• If your plan does not include AI memory, the cluster shows one plain state saying so — never three broken icons.
• The freshness colour compares the Blink's last edit against your last completed memory refresh, so an amber icon is your cue that a refresh (from the OrbitPilot page, or automatically at logout) will bring the AI up to date.
• The files icon only turns green when the file's content is actually stored in memory — never sooner.

For developers

Facts come from orbitpilot.services.memory_status_for_blinks(user, blink_ids) — one call per Library page (constant query bill, pinned by blink/test_memory_status_ui.py). The trigger ("refresh you asked for" vs automatic) reads OrbitPilotMemoryBuild.user_initiated (BL-357). The cluster template is templates/blink/_memory_status.html; the files flag has been computed from blink.files chunks since WO-32 Phase A (orbitpilot/test_memory_status.py pins both directions).