IDEA-001 — what detector data and access are documented

Answer to the research question

Public documents establish local signal displays and video output for BlueBird/Chuyka; a machine-readable contribution feed remains unestablished. The inspected 4.0 FAQ describes frequency/channel/RSSI displays and video output, without a versioned observation schema, event-time definition, receiver/target coordinates or export entitlement. Wi-Fi firmware updates and generic app “data access” wording do not close that gap. This is a documentation finding, not a conclusion that structured export is impossible.¹²³

The user's co-founder relationship is accepted as context; “Chuika” remains the user's wording alongside the vendor's “Chuyka”. No identity-candidate investigation was performed.¹¹

Snapshot: 2026-10-09 America/Los_Angeles. This human-approved v002 follow-up reuses completed RES-001 evidence. See four-subject data/access matrix, co-founder evidence and comparison detail.

Comparison and key findings

Subject	Documented evidence	Remaining distinction
BlueBird / Chuyka	Analog-video signal observation, displayed frequency/channel/RSSI and video output; Monitor mode pauses scanning in the viewed band.1	Structured telemetry, event identity/location, retained records and shared-data rights unestablished.
DroneSight	Host-based Remote ID collection, map/premium access; host terms assert DroneSight ownership of uploaded airspace data.56	Host API/bulk/redistribution entitlement and measured coverage unestablished.
Dronetag	Remote ID raw/local and licensed cloud modes, authenticated REST and conditional push integrations.789	Account/portal access does not establish access to all receivers or redistribution permission.
BlueMark / DroneScout	Local MQTT packet metadata, timestamps and encoded UAS data; optional receiver GNSS location distinct from drone position.10	Cross-receiver deduplication, calibrated uncertainty and whole-network entitlements unestablished.

These are vendor-documented interfaces/terms, not independently demonstrated performance. Analog-signal observations and cooperative Remote ID records describe different measurements. A map view, local packet export, an app privacy right and permission to redistribute network data are separate evidence questions.

Implications and recommendations

Agent recommendation: prioritize a firmware-specific co-founder interface/export specification and authorized small non-sensitive sample or synthetic example. Annotate field meaning, units, missing/invalid values, receiver/target/operator/takeoff locations, reception/drone/ingestion times, scan-mode state and clock quality. BlueMark's documented lack of onboard RTC illustrates why a timestamp field alone does not establish correct timing.¹⁰

Then clarify retention and permissions for contributing, pooling, displaying and redistributing observations. BlueBird app terms and privacy statements do not establish those entitlements.³⁴ The gap register prioritizes questions and includes an unsent information-request draft. No outreach occurred.

“Whole database” remains unselected among signature library, current shared detections, historical observations and API/bulk records or a combination. The $10 monthly payment remains a proposal with unknown currency, unit and eligibility. No economics or entitlement decision was made.¹²

Uncertainty and coverage limits

Only four subjects' relevant documents were inspected. New captures are partial web-tool text, not original HTML/PDF bytes. Two BlueBird PDF attempts failed; BlueMark's manual is partial text without complete figures/binary-member layouts. Dynamic services, apps/accounts, hardware, field performance, fulfilled access and enforceability were not tested. No independent operational-performance evidence was obtained.

Resource-bound nonconformance: actual gathering reached thirteen unique new URLs against twelve approved. BlueBird crossed its eight-URL allocation in a four-link batch after five new URLs; comparisons had already used four. Rebalancing was too late. All evidence and failures remain preserved; no retrospective approval is asserted. Manager permitted only unaffected original synthesis/review and stopped further retrieval, including retries. Source accounting records the chronology. Deliverable completion and source-bound compliance are separate outcomes.

Review and next decision

Independent Sol evidence review found no material correctness defects in the data/access follow-up. Original deliverables are complete with resource-bound nonconformance; product performance and legal/data entitlements remain unverified. Knowledge checks cover format, local links and capture integrity, not product performance. Next user decisions concern the co-founder documentation request and database meaning. Further gathering, outreach, implementation, tests and economics require separately authorized scope.¹²

type: Research Summary
title: IDEA-001 — what detector data and access are documented
description: 'Reviewed documentation synthesis: co-founder structured exports and
  shared-database rights unestablished; source-bound nonconformance disclosed.'
status: draft
generated:
  by: codex/gpt-6
  at: '2026-10-10T05:39:25+00:00'
sources:
- id: ds-host
  resource: /references/SRC-87920e76e95d/source.md
  title: DroneSight host a receiver
- id: ds-terms
  resource: /references/SRC-726546dae9a6/source.md
  title: DroneSight receiver host terms August 2026
- id: dt-scout
  resource: /references/SRC-148960c5f336/source.md
  title: Dronetag Scout
- id: dt-api
  resource: /references/SRC-6a2cbcb96b02/source.md
  title: Dronetag REST API getting started
- id: dt-push
  resource: /references/SRC-235e7bcca8a0/source.md
  title: Dronetag data push getting started
- id: bm-manual
  resource: /references/SRC-89399f9304c8/source.md
  title: DroneScout receiver manual 230 240 series
- id: p4
  resource: /references/SRC-95ff79592d27/source.md
  title: Chuyka 4.0 Drone Detector with 4 Bands 1080–8800 MHz | BlueBird Tech
- id: m4
  resource: /references/SRC-cf84bccfb243/source.md
  title: User Manual for the Chuyka 4.0 Drone Detector | BlueBird Tech
- id: terms
  resource: /references/SRC-5fa33b24694e/source.md
  title: BlueBird Tech | - Terms of Use for BlueBird Tech Mobile Application
- id: privacy
  resource: /references/SRC-0ec78e85875e/source.md
  title: BlueBird Tech | - Privacy Policy for BlueBird Tech Mobile Application
- id: cofounders
  resource: /docs/project-information/ideas/IDEA-001-community-detector-network/input-2026-10-09-cofounders.md
  title: User co-founder clarification
- id: scope
  resource: /docs/project-information/ideas/IDEA-001-community-detector-network/scope/v002.md
  title: Approved scope v002