docs(design): scope hybrid durable drone sightings + spoof_suspect#51
Merged
Conversation
FAA make/model enrichment (the other half of the old deferred drone-history slice) shipped in 0.2.10+, so mark it implemented and record the deviation: we went live-cached per-serial instead of the planned prebuilt SQLite, which suits real (low) drone volume and the Pi-SD posture. Scope the remaining half against dump3411 v1.0.0, which now persists raw track history itself (--history-db, 30-day, per-point tracks + /map). ha-airspace must not duplicate that firehose, so the decided design is hybrid: persist one enriched summary row per sighting (operator location, FAA make/model, AGL, closest-approach geometry, flags) in the journal off the existing drone_detected hook, and deep-link to dump3411's /map for the full track. Operator location is the most sensitive field, so durable storage is opt-in and bounded-retention. Fold in a behavioral spoof_suspect flag: a replay of previously-seen REAL serials defeats identity/registry validation (RID has no crypto auth), so detect via behavior — tier 1 stateless (malformed 0x00 serial, one self_id across many serials), tier 2 over the sighting store (impossible kinematics, same serial in two places, implausible operator data). Emits as an enrichment flag, reusing the flag/alert machinery. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FAA make/model enrichment (the other half of the old deferred drone-history slice) shipped in 0.2.10+, so mark it implemented and record the deviation: we went live-cached per-serial instead of the planned prebuilt SQLite, which suits real (low) drone volume and the Pi-SD posture.
Scope the remaining half against dump3411 v1.0.0, which now persists raw track history itself (--history-db, 30-day, per-point tracks + /map). ha-airspace must not duplicate that firehose, so the decided design is hybrid: persist one enriched summary row per sighting (operator location, FAA make/model, AGL, closest-approach geometry, flags) in the journal off the existing drone_detected hook, and deep-link to dump3411's /map for the full track. Operator location is the most sensitive field, so durable storage is opt-in and bounded-retention.
Fold in a behavioral spoof_suspect flag: a replay of previously-seen REAL serials defeats identity/registry validation (RID has no crypto auth), so detect via behavior — tier 1 stateless (malformed 0x00 serial, one self_id across many serials), tier 2 over the sighting store (impossible kinematics, same serial in two places, implausible operator data). Emits as an enrichment flag, reusing the flag/alert machinery.