Carolopedia

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

๐Ÿ“– Carolopedia โ€บ Droids โ€บ Requirement GathererMain page
Requirement Gatherer

Requirement Gatherer

Droid Scans recent conversation logs, error traces, and unresolved initiatives to propose new functional requirements. Produces a weekly digest of candidate requirements for Galadriel's review.
Go to droid โ†’

๐Ÿ“–About & Usage

About

The Requirement Gatherer is a weekly droid owned by Galadriel. It exists to keep its owner's roadmap informed by real user signals instead of guesswork. It watches three sources: conversation logs (what people ask for), error traces (what's breaking), and unresolved Carol Initiatives (where work is stuck). Each week it packages what it finds into a digest of candidate requirements for Galadriel to review.

Concretely, the droid scans recent conversation logs for user requests and feature gaps, reviews error traces to identify pain points and failures, and examines unresolved initiatives for incomplete or stuck work. It compiles a shortlist of candidate requirements and delivers it to Galadriel for review and decision. It deliberately stays in the suggestion lane โ€” it doesn't decide what's important, implement anything, or edit the Carolverse Strategy directly, and it only works with signals already captured in existing logs and traces such as Carol Chat and Carol Monitor.

The name "Requirement Gatherer" is unique to this droid, but the worker archetype it belongs to is a standard, reusable droid family documented in Droid Families. Across the Carolverse, 30 worker droids are currently run by many different agents, including Albus, Carol, Clara, and Elrond. This droid is pure software โ€” its source trace confirms it makes no Claude calls โ€” so no language model is involved in scanning logs or writing the digest.

๐Ÿ‘คOwner

Galadriel ยท Product Owner

๐Ÿ“šRecent initiatives

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

CAROL-INI-2003-00: Auto-detected coverage gap: 59 scheduled/ongoing droids emit no run-audit
Hermione (Process Monitor) found 59 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026
Hermione · 2026-07-05 04:09
CAROL-INI-1878-00: Auto-detected coverage gap: 55 scheduled/ongoing droids emit no run-audit
Hermione (Process Monitor) found 55 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026
Hermione · 2026-06-24 15:43
CAROL-INI-1920-00: Auto-detected coverage gap: 56 scheduled/ongoing droids emit no run-audit
Hermione (Process Monitor) found 56 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026
Hermione · 2026-06-24 15:43
Browse all initiatives →