Workshop 006: Telemetry Event Model (stream-processing) + ADR-018#37
Merged
Conversation
…idate Front-loaded design grill (grill-with-docs, EM-direct per the W005 playbook) for the W006 Telemetry Event Modeling workshop. Resolves the Kafka-vs-gRPC geospatial-supply question parked since W001 parking-lot #4 / ADR-candidate #3. Eight resolutions (R1-R8): NearbyAvailableDrivers is a Dispatch-owned local projection fed by Kafka (location) + ASB (availability); eventual consistency reconciled at acceptance; Telemetry modeled as a stream-processing BC (4th modeling shape), availability-agnostic; windowed gRPC client-streaming ingest; H3 cell id as published-language; throttle policy via config-as-events; Kafka topic partitioned by driverId. Captures the ADR-018 decision statement (drafting deferred), three §11 ADR candidates (Kafka-topic-naming, stream-processing-shape, windowed-streaming), the workshop skeleton, and the cross-workshop amendments the eventual W006 PR owes (ADR-018 authoring, W001 §5.3 amendment, context-map edge #5 lock). Checkpoint-and-pause: ADR-018 authoring + the slice-by-slice event model resume in a focused follow-up session.
Resume the W006 design after the 2026-06-25 grill-with-docs pause (R1-R8). Author ADR-018 (candidate-projection ownership + telemetry geospatial supply), walk the 5 Telemetry slices (stream-processing, CritterCab's 4th modeling shape), and close the cross-workshop amendments in the same PR: W001 5.3 (parking-lot #4 closed, 11 #3 -> ADR-018), context-map edge #5 (dashed->solid), vision-doc override.
erikshafer
changed the title
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.
What this is
Resumes the paused W006 Telemetry design (grill-with-docs front-loading pass R1–R8, captured 2026-06-25) and lands it as one cohesive design PR: ADR-018, the W006 Telemetry Event Model, and the cross-workshop amendments the decision triggers.
EM-direct (no Domain Storytelling pre-step). The eight grill resolutions pre-locked every design call; this session authored the ADR, walked the five slices with per-slice sign-off, and closed the spec-delta loop.
This PR's first commit is the durable grill ledger (
docs/planning/2026-06-25-w006-telemetry-grill-resolutions.md, R1–R8) captured at the checkpoint-and-pause; the second commit is the full workshop + ADR + amendments below. (Previously the WIP checkpoint PR; now the finished W006 design PR.)New artifacts
docs/decisions/018-…md— ADR-018 (Accepted).NearbyAvailableDriversis a Dispatch-owned local projection, not a Telemetry-owned queryable index. Location supply over Kafka; availability over ASB (forward-constraint to Driver Profile). Eventual consistency, last-writer-wins per driver, reconciled at acceptance. Explicitly overrides the vision doc's "index that Dispatch queries" framing. Resolves W001 §11 ADR-candidate Add Skills Foundation #3; locks context-map edge Add Contributor Covenant Code of Conduct #5.docs/workshops/006-telemetry-event-model.md— W006, complete. Establishes stream-processing as CritterCab's fourth modeling shape (non-event-sourced domain core; overwrite-in-place document + Kafka breadcrumb history; the lone event-sourced stream is the config singleton). 5 slices:TelemetryPolicyConfigured(config-as-events) · gRPC client-streaming ingest ·DriverLocationUpdated→Kafka ·LastKnownPositionstore + eviction · W001 §5.3 amendment. First Kafka topic and first gRPC client-streaming surface modeled in CritterCab.Cross-workshop amendments (same PR, per the context-map update cadence)
ADR candidates surfaced (carried, not authored here)
Follow-ups (not in this PR)
telemetry/v1protobuf authorship (bundled-proto session).NearbyAvailableDriversStubwith the Kafka ⋈ ASB local document view (the first real transport wiring in the codebase).Notes for review
…-deferreddeliberately — renaming it would break inbound links from ADR-018, W006, and W001; the section body now states "locked."