Skip to content

Incident cause-inference (spin/wall/contact-partner) spec + plan - #66

Open
simsteward wants to merge 1 commit into
mainfrom
feat/incident-cause-inference
Open

Incident cause-inference (spin/wall/contact-partner) spec + plan#66
simsteward wants to merge 1 commit into
mainfrom
feat/incident-cause-inference

Conversation

@simsteward

Copy link
Copy Markdown
Owner

Summary

  • Research and design for making the "spin"/"wall" cause labels (already styled in dashboard CSS but never producible today) reachable, plus a best-guess contact-partner annotation — all from no-admin Group 2 SDK signals already read every tick, no new SDK polling
  • Confirms via direct source read + GitHub code search that CrewChiefV4 has no yaw/spin-rate detection to crib from (DamageReporting.cs does airborne/rollover + impact-severity only) — corrects two docs that previously miscited it for spin detection
  • Adds GAP 12 to docs/REVIEW-incident-points-implementation.md documenting that no spin/loss-of-control detector exists yet anywhere in this codebase or the SDK
  • No implementation yet — spec + plan only

Test plan

  • N/A — docs only, no code changes
  • Implementation plan review before starting Task 1

🤖 Generated with Claude Code

Research and design for making the "spin"/"wall" cause labels (already
styled in dashboard CSS but never producible today) reachable, plus a
best-guess contact-partner annotation — all from no-admin Group 2 SDK
signals already read every tick, no new SDK polling.

Confirms via direct source read + GitHub code search that CrewChiefV4
has no yaw/spin-rate detection to crib from (DamageReporting.cs does
airborne/rollover + impact-severity only) — corrects two docs that
previously miscited it for spin detection, and adds GAP 12 to the
incident-points review doc documenting that no spin/loss-of-control
detector exists yet anywhere in this codebase or the SDK.

No implementation yet — spec + plan only.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants