IDEA-001 — co-founder detector evidence

Bounded BlueBird/Chuyka display, interface and data-access evidence with explicit export and capture gaps.

Research FindingsDraft record

Finding and provenance — 2026-10-09 America/Los_Angeles

BlueBird/Chuika are user-confirmed co-founders; the website uses “Chuyka”. No identity-candidate investigation was performed. Technical material below is vendor documentation, not independent capability verification.13

The available evidence supports local analog-signal observation and video viewing. Structured contribution to IDEA-001 remains unestablished. This is an evidence gap, not a finding that an API or export capability is absent. See the canonical profile for reusable context.

Documented observations and interfaces

Subject Vendor evidence Consequence for a data contribution model
Chuyka 3.0 observation Analog-video detector; bands 900–1800, 2870–4080, 4860–6060 MHz. Small display shows signal level/count; large display shows intercepted camera video. Full scan claimed at 4–8 seconds.4 A detected signal is not a uniquely identified aircraft or geolocated track.
Chuyka 4.0 observation Four bands: 1080–2200, 2860–4500, 4860–6040, 6040–8800 MHz; analog signals. Product table claims 4–8-second scanning and ≤10 MHz steps.5 Band/version differences must accompany any later sample. Scan duration is not an event timestamp.
Displayed fields 4.0 FAQ lists signal count, band histogram, active frequencies/channels, battery and button state. Monitor mode lists frequency, channel number, signal level and RSSI.7 These are displayed fields; machine-readable field names, units, calibration and export remain unknown.
Video connections 3.0 video output is optional, described for monitors, goggles or recording devices. 4.0 includes video output for an external display.45 Video output does not establish event metadata export. Connector/pinout/video format and whether overlays are exported remain unknown.
Other connections 4.0 packaging lists USB Type-C charging, XT30 battery and XT60 vehicle-power cables; additional/continuous power is described.5 Charging/power connectors do not establish a data interface.
Connectivity/software 4.0 FAQ describes Wi-Fi hotspot OTA firmware download and firmware switching. App terms broadly describe device management/data access and connectivity via Bluetooth/Wi-Fi/Internet.79 OTA and generic app descriptions do not establish a supported detector observation API, protocol or network feed.

Required inventory: unresolved details

Dimension Evidence state / missing evidence
Exportable fields Display inventory above; structured event export, device IDs, stable target IDs, raw RF/IQ, video files and CSV/JSON fields unestablished.
Timestamps Event clock, timezone, timestamp precision, synchronization, latency, sequence IDs and sample cadence unknown.
Receiver location App privacy policy says approximate IP/network location and no precise GPS collection.10 This describes app handling, not a documented detector-location field. Surveyed receiver position, antenna position, orientation and motion handling remain unknown.
Target location and uncertainty No documented target latitude/longitude/altitude, bearing/range estimate, covariance, confidence calibration or positioning method established by inspected text. Category movement-direction wording supplies no method or uncertainty.3
Interfaces and access Video display/recording use and OTA documented; supported telemetry transports, SDK/API, authentication, rate limits, offline buffering, network resumption and bulk export unknown.
Schema/sample availability No structured schema or observation sample supplied or established in these captures. PDFs were linked but inaccessible.1112
Retention App policy gives a necessity-based retention statement and deletion request, without fixed duration.10 Detector event history, video retention, storage capacity and replay/export behavior unknown.
Permissions App terms grant personal-use app licensing; privacy policy offers access/correction/deletion of one's data.910 Neither is a demonstrated license to publish, pool or redistribute detector observations or access all contributors' records. No legal conclusion is drawn.
Quality/uptime See conditions below. No independent false-positive/false-negative rates, field uptime, outage logs, reliability study or service-level agreement established.

Operating constraints and conflicting wording

Vendor 3.0 FAQ acknowledges false alarms, EW interference, blacklisted-channel alerts suppressed, and Monitor mode stopping scans/new channels in the viewed band. It describes stationary use with environmental protection and operation while QC charging.8 The 4.0 FAQ also says Monitor mode pauses its selected band; auto threshold follows noise, video-only filtering and band-disable modes affect observations. Its example names “1.3” and “3.3” GHz and omits 8.8 GHz; request firmware-specific clarification rather than silently correcting it.7

3.0 runtime is claimed up to six hours depending on usage. 4.0 claims two hours built-in, four additional, up to six total, with −10 to +50°C operation and IP54. These are specification claims, not uptime measurements.45 The 4.0 table labels some ranges “From 4 km”, while main indicators say “up to 4 km”; range is conditional on transmitter power, antennas and propagation. Do not use it as a coverage radius.5

The app terms' broad “data access” description exceeds the product page's visible firmware-update/offline-instructions description; this does not prove a contradiction, because capabilities may vary by version. The relevant export feature, firmware and supported device need explicit documentation.95 App terms identify TOV “VPF” as provider; product footer names LLC “BLUEBIRD TECH” as seller. Their formal mapping remains unspecified, without identity investigation.93

Next evidence request and review limits

Analysis/recommendation: ask the user for an authorized, firmware-specific interface/export specification and a small sanitized example observation, including units, timestamps, receiver position, any target position/uncertainty, scan/mode state, retention, supported access and contribution/redistribution permissions. Confirm whether video output carries overlays and whether export works continuously while detecting. Do not send this request externally.

The source manifest records nine new URLs plus the reused category, including failed PDFs and the disclosed phase overrun (13 new URLs versus 12 approved). All readable captures are partial web text, not HTML or full PDF manuals. No embedded videos, app accounts, live feeds or hardware were inspected. Missing pages/attachments limit negative findings. Independent evidence review and shared index/checkpoint work belong to the parent; this worker does not mark claims verified.


  1. Preserved user clarification; technical capabilities are not inferred from co-founder status. ↩

  2. Immutable approved scope; execution gates recorded separately. 

  3. L109–141, L348–367, L567–569; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩

  4. Technical characteristics / Functions / Operating principle, L168–255; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩

  5. Technical characteristics / Functions / package / FAQ, L187–247, L296–307, L331–334, L528–536; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩↩↩↩

  6. Chuyka manual links, L121–171; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. 

  7. FAQ displayed fields, modes and firmware, L190–258; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩

  8. FAQ operation, charging and interference, L138–218; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩

  9. Sections 1, 4–6; L95–163; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩↩

  10. Sections 1.3, 5–6; L131–149, L188–204; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩

  11. Failed PDF download; capture 2026-10-10T05:31:46Z. Failed capture; no PDF contents inspected. ↩

  12. Failed PDF download; capture 2026-10-10T05:31:46Z. Failed capture; no PDF contents inspected. ↩

Sources, provenance and record details
Record type
Research Findings
Status
draft
Generated
by: codex/researcher at: '2026-10-10T05:34:00Z'
Recorded checks
No verification metadata recorded.

Sources

All record metadata
type: Research Findings
title: IDEA-001 — co-founder detector evidence
description: Bounded BlueBird/Chuyka display, interface and data-access evidence with
  explicit export and capture gaps.
status: draft
generated:
  by: codex/researcher
  at: '2026-10-10T05:34:00Z'
sources:
- id: category
  resource: /references/SRC-1e2ef4748bd5/source.md
  title: BlueBird drone detector category — user-supplied link
- id: p4
  resource: /references/SRC-95ff79592d27/source.md
  title: Chuyka 4.0 Drone Detector with 4 Bands 1080–8800 MHz | BlueBird Tech
- id: p3
  resource: /references/SRC-0a341d4fd0c9/source.md
  title: Chuyka 3.0 FPV Drone Detector | BlueBird Tech
- id: instructions
  resource: /references/SRC-88cdcd921212/source.md
  title: BlueBird Tech Device Manuals and Downloads
- id: m4
  resource: /references/SRC-cf84bccfb243/source.md
  title: User Manual for the Chuyka 4.0 Drone Detector | BlueBird Tech
- id: m3
  resource: /references/SRC-ddd422a7cb11/source.md
  title: Device User Manual Chuyka 3.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: pdf4
  resource: /references/SRC-2ea5b93e31ca/source.md
  title: Chuyka 4.0 PDF manual
- id: pdf3
  resource: /references/SRC-08a1b7ccf1d3/source.md
  title: Chuyka 3.0 PDF manual
- 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