Oliver Kieselbach
7fe0e9ef58
Plan §A enrichment (Edge-Triggered State Snapshots, 2026-05-03). For events on the lifecycle-anchor allowlist, EventTimelineEmitter.Emit now attaches the current DecisionState snapshot under data["decisionState"] after ResolveData(). Existing Data fields are always preserved — both the parameter-rebuilt path and the typedPayload-merged path mutate a fresh dict, so adding the new key is a strict merge, not a replace. Behavior: - 13 anchor event types get decisionState (full allowlist from PR1's LifecycleAnchorEventTypes). - Non-anchor events (enrollment_complete/_failed, app_install_*, performance_snapshot, download_progress) are unchanged. - Idempotent: an existing data["decisionState"] (defensive — should never occur in practice since only the emitter writes that key) is not clobbered. Why Emitter, not Reducer (per Codex rev2 review): - EffectRunner.cs:114 already passes stateAfterReduce to the emitter, so no new dependency is needed. - Reducer-side enrichment via typedPayload would have replaced existing Data via the typedPayload-as-dict branch in ResolveData — wiping espPhase, patternId, network state etc. The emitter-seam is the only place that runs after ResolveData and sees a dict ready to merge into. Tests (V2.Core +22 tests, suite 920 → 942): - All 13 anchor event types via Theory: each gets decisionState with schemaVersion matching the builder's const. - Parameter-based path: esp_phase_changed preserves reason+espPhase. - typedPayload path: network_state_change preserves from/to/transition. - Idempotence: prebuilt sentinel decisionState in typedPayload survives. - Non-anchor exclusion: 5 representative non-anchors confirmed null. - Top-level allowlist sanity-check (delegates full coverage to PR1's DecisionStateSnapshotBuilderTests). Tests (regression-clean across all suites): - V2.Core: 920 → 942 (+22) - DecisionCore: 293 (no change) - Backend Functions: 862 (no change) - Existing EventTimelineEmitterTests: 26/26 still pass. Plan: .claude/plans/v2-zero-periodicity-observability.md (rev7). PR3 (Death-Rattle / prior_run_died_with_state) is next. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Autopilot Monitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full documentation is available at autopilotmonitor.com/docs
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.