IDEA-002 assessment scope v001
Concrete proposed scope awaiting user sign-off and manager start authorization.
Approval state
Proposed scope v001. User approval: pending. Manager start authorization: pending. Work gathered before the new approval workflow is pre-gate draft evidence; it does not establish retroactive approval. This scope has not authorized training or implementation.
Question and decision served
Assess what is already implemented in the existing radio-coverage project, what would complete a credible propagation-map capability, and what additional evidence would make it useful for DroneRadar. Recommend a first bounded experiment and completion criteria for a later implementation decision.12
Included work
- Read-only inspection of
/Users/gumanist/projects/radio-coverageand its three named Claude worktrees. Reconcile code, selected recorded metrics, documentation, commit/dirty context and unresolved experiments. - Selective review of the four related Claude sessions to recover user intent and pending proposals. Preserve only relevant inspected text and provenance, excluding credentials, unrelated history and private flight logs.
- Preserve selected local originals with hashes and path/commit provenance in shared references; maintain an idea data manifest and curated session inventory.
- Produce an expanded idea brief and readiness assessment that distinguish implemented code, recorded experiment claims, independent checks, pending proposals and missing evidence.
- Propose completion milestones and measurable acceptance criteria for the existing propagation tool. Default planning target: reproducible propagation maps and benchmark first; record alternatives without treating the default as a user decision.
- Propose a DroneRadar input/output contract and describe the additional calibration/observation evidence needed to move from propagation predictions to passive detector coverage. Use existing landscape study and canonical profiles as context.
- Propose one bounded experiment with inputs, comparisons, metrics, stop conditions and estimated resource requirements where supported. Perform an independent Sol evidence review, resolve or disclose findings, and validate the knowledge bundle after the manager lifts the shared-write freeze.
Outputs
Owned directory: knowledge/docs/project-information/ideas/IDEA-002-ai-signal-coverage/.
- Updated brief and research links.
- Assessment, completion milestones, proposed interface contract, evidence gaps and first experiment plan.
data/manifest.md, curated session inventory and bounded code/result findings.- Reusable evidence in
knowledge/references/, including explicit capture limitations. - Review record and durable status/next action; coordinator index/log update only when permitted.
Exclusions
Source repository/worktree modifications; merging branches; new training or model inference runs; paid APIs; deployment; live detector integration; bulk/private flight-log import; contacting vendors; recurring monitoring. No dataset or model-weight download. Existing result arithmetic and metadata checks are included; executing new experiments requires later scope authorization.
Completion criteria
Every material current-state claim resolves to selected archived evidence with version context. The assessment explains model/domain limits, identifies a recommended completion path and alternatives, provides actionable acceptance criteria, and keeps propagation capability separate from detector validation. The contract labels units, coordinate/height conventions, model provenance, missing fields and uncertainty. The experiment can be authorized and executed as a separate bounded task. One independent review and knowledge validation are recorded, with unresolved issues disclosed.
Decisions needed
Approve or amend this scope. Optional preference: prioritize reproducible propagation maps, receiver placement, or field-calibrated detection probability. The default is a planning recommendation only; no answer is assumed to be approval.
Next action
User explicitly signs off v001 (or requests a revision) in this chat. After approval, send the exact approved version and approval evidence to manager chat 01a1241c-b623-7df3-a0d7-a85aa4a02811; await its substantive-start authorization. Preserve current draft evidence meanwhile.