IDEA-001 scope v001 — detector data and access evidence

Objective and decision served

Identify what evidence is available or still needed to define IDEA-001's data contribution and access model. Recommend the next evidence request, without choosing hardware, a launch market or a commercial model. This proposed follow-up serves the user's current data-gathering focus.²

Deliverables and acceptance criteria

1. Partner evidence brief: retain “Bluebird” and “Chewica” as supplied; establish an identity only if traceable evidence supports it. Record identity candidates, ambiguity and missing partner documents. Never treat a similar name as confirmation.¹
2. Data and access matrix: compare the partner evidence with DroneSight, Dronetag and BlueMark, using existing canonical profiles first. Cover observation type, exportable fields, timestamps, location/uncertainty, interfaces, sample/schema availability, retention, quality/uptime conditions and documented use/redistribution rights. Mark every unknown and distinguish contributor visibility from API or bulk database access. These are a bounded follow-up subset of RES-001, not a new landscape scan.³
3. Gap register and recommendation: prioritize unanswered questions and draft a short partner information request for the user to review; do not send it. List possible meanings of “whole database” without selecting one. Preserve the $10 monthly payment as a proposal with unresolved currency, payment unit and eligibility.¹

Each substantive claim must distinguish user context, vendor claims, independent evidence and analysis, with dated claim-level citations to exact archived evidence. A missing document or unresolved identity is an acceptable finding. Deliver an independent evidence review, recorded capture limitations and passing knowledge validation; no claim of field-performance verification.

Included work and exclusions

Included after both gates: targeted desk research and inspection of public documentation or user-supplied, authorized files for the four subjects above. Existing RES-001 is completed pre-gate work; reuse and cite it without rerunning or retrospectively approving it.³

Excluded: broad competitor discovery; purchases, paid APIs, account creation or credential use; vendor/partner outreach; authenticated feeds or bulk personal/location data collection; code, live detector integration, field tests, network design, cost/coverage modelling, legal conclusions, launch-market selection, publication or recurring monitoring. No actual database access or redistribution permission is assumed. Any material expansion needs a new scope version and both gates.

Evidence, data access, resources and dependencies

Start with preserved inputs, RES-001 and canonical profiles. Bound new gathering to at most 12 distinct public source URLs across the four subjects; archive all gathered materials, including relevant background. Prefer official specifications, schemas and terms; use independent evidence where available. Search results guide discovery and do not substitute for captures. Stop at the bound and report gaps rather than silently extending the scan.

Partner identity may remain unresolved without a user-provided official link or document. Geography is unspecified: compare documented access and collection mechanisms internationally, label geographic limits and defer launch-country permission analysis.

Proposed execution uses Sol for bounded research, at most two researchers with separate files/source ownership, and one independent Sol reviewer. No paid services or hardware spend; ordinary model usage is unmetered here and no monetary ceiling is claimed. The manager must assign shared reference/canonical-profile ownership before execution; this chat currently owns only the IDEA-001 folder. Future findings, matrix, gap register and review stay here, while shared evidence/profile changes require explicit coordinator allocation. No duplicate company profiles.

Open questions and assumptions

• Optional input: can the user supply Bluebird/Chewica's official link or product document? Without it, report candidates or unresolved identity rather than guess.
• “Whole database” and the $10 proposal remain questions for later decisions; their clarification is not required to document available evidence.¹
• Working assumption: retain the data-gathering focus and defer later-stage ideas. “Flightradar” remains the earlier study's provisional Flightradar24 interpretation.²³

Change from previous scope

Initial scope for the next phase only. No approval is asserted for earlier inputs or RES-001.

Approval request

Approve or amend v001 in this owning chat. Explicit user approval must be recorded separately with this file's path and SHA-256, followed by the manager's separate recorded start authorization. This snapshot will not be edited after publication; amendments create v002.

type: Scope
title: IDEA-001 scope v001 — detector data and access evidence
description: Proposed bounded follow-up on partner identity, exportable observations
  and contributor access.
status: draft
generated:
  by: codex/gpt-6
  at: '2026-10-10T05:15:46+00:00'
x_scope_version: v001
x_stage: awaiting-user-signoff
x_work_status: planned
sources:
- id: initial-input
  resource: /docs/project-information/ideas/IDEA-001-community-detector-network/raw-input.md
  title: Original user input
- id: steering
  resource: /docs/project-information/ideas/IDEA-001-community-detector-network/input-2026-10-09-data-focus.md
  title: Data gathering steering
- id: landscape
  resource: /research/studies/RES-001-current-landscape/summary.md
  title: Completed landscape study