Carol — back to Apps ← Apps

Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaDroidsScanner
Scanner

Scanner

Droid Scans for tool upgrade opportunities. Weekly on Sundays at 4:30 AM.
Go to droid →

📖About & Usage

Owner agent — accountability this droid serves

Merlin must keep tools and infrastructure in the build pipeline current and healthy. Scanner helps by automatically checking for tool upgrades weekly, giving Merlin visibility into what needs attention before problems emerge.

Droid responsibility

Every Sunday at 4:30 AM, Scanner checks tool packages for available upgrades and reports what's out of date. This automatic weekly scan means Merlin doesn't have to manually hunt for upgrade opportunities—they're surfaced on schedule.

What the droid actually does

  • Runs every Sunday at 4:30 AM
  • Scans tool packages for available versions
  • Identifies tools with upgrades available
  • Reports findings for review

Boundaries

Scanner only identifies upgrades; it does not apply them, evaluate compatibility, assess breaking changes, or make decisions about which upgrades to prioritize. Those choices stay with Merlin or other parts of the tooling system.

👤Owner

Merlin · Head of Execution

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.

CAROL-INI-0020-02: Palantír — Facebook-style build-pipeline activity feed (Elrond-owned)
A seeing-stone for the build pipeline. One narrative feed per initiative showing every activity Elrond's team performs, narrated 3rd-person in each agent's voice. SCOPE: Only bui\u2026
Orion · 2026-07-04 01:11
CAROL-INI-0020-01: Palantír — Facebook-style build-pipeline activity feed (Elrond-owned)
A seeing-stone for the build pipeline. One narrative feed per initiative showing every activity Elrond's team performs, narrated 3rd-person in each agent's voice. SCOPE: Only bui\u2026
Orion · 2026-07-03 20:55
CAROL-INI-2070-00: SST scanner: record initiatives DB as the relay-backed daemon store, not the stub
The SST records the initiatives DB as a 0-byte file with 0 tables at the old on-disk path; it has no record of the real store. Reconcile: the SST Scanner must record the initiativ\u2026
Orion · 2026-06-30 18:43
Browse all initiatives →