Raindrop: Gap Record (not yet a context-plane authority)

Research performed

Fetched docs.raindrop.ai directly (2026-09-13). Raindrop is a production monitoring platform for AI agents: it detects silent agent failures traditional monitoring misses (confidently-wrong answers, lost conversational context, repeated failed tool calls with no raised error). Integration model per upstream docs: SDKs (TypeScript, Python), an HTTP API, framework integrations with AI platforms/cloud providers. It visualizes agent trajectories, auto-detects failure patterns, supports natural-language search over production interactions, and A/B testing of agent configurations.

Searched Bluefly docs/config/repos for evidence of an actual integration: none found. No Bluefly agent, repo, or config references a Raindrop SDK, API key, or webhook. This file exists to record that absence precisely, not to fabricate a role.

Classification

ROLE_IN_CONTEXT_PLANE=NOT_ESTABLISHED — no current Bluefly integration exists. Do not classify it as authoritative, derived, cache, client, transport, execution, or reference context until an actual integration is built and cited here with evidence (a specific repo, config file, or SDK call).

Why it is not promoted to authority

Strong default boundary, stated in advance so a future integration doesn't silently become doctrine: Raindrop (if integrated) would help discover external/behavioral signals about agent runs — it would never become Bluefly source/doctrine authority. It is conceptually closer to a post-execution behavioral-observability tool than the pre-execution discovery tools this plane otherwise documents (Orbit, QMD) — distinct role, not a merge candidate with either even if built.

If this changes

When a real integration exists, replace this file's content with the full template: ROLE= / AUTHORITY= / COLLECTIONS= / TAGGING-CLASSIFICATION= / AGENT_ACCESS= / API-CONNECTOR= / FRESHNESS= / INGESTION= / WHAT_GOES_THERE= / WHAT_MUST_NOT_GO_THERE= / RELATIONSHIP_TO_QMD= / RELATIONSHIP_TO_BLUCITY_DOCS= / RELATIONSHIP_TO_UPSTREAM_DOCS= — cite the specific repo/config that proves the integration, same evidence discipline as every other claim in this repository.