Skip to content

Event Logs follow-up: EventData identifier correlation keys (EnrollmentId) #856

Open

Description

@adamgell

Part of #823.
Spec: docs/superpowers/specs/2026-10-08-event-logs-workbench-ui-handoff-design.md (see the section references below).
Design: Claude Design canvas "Event Log Viewer Redesign" (board exports to be attached).

Parent: #539 · Spec: §12, §15.2, Q-9

Add explicit correlation key kinds for EventData identifiers such as EnrollmentId to the unified-timeline
correlation engine (TimelineCorrelationKeyKind currently has activityId, relatedActivityId,
providerChannelEventRecord, processStart, sessionId, deviceId, userId, secondary).

Acceptance

  • Exact edges only when the identifier is unique within one normalized machine (existing exact-match rules).
  • cargo gates, wasm32 parser check, Windows-lab evidence on an enrollment failure corpus.

Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestparserLog parser relatedrustPull requests that update rust code

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions