Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,8 +162,11 @@ The dependency is those observations, not the absence of a Windows host.
The [issuer/recovery follow-up](docs/roadmap/etw-issuer-recovery.md) adds held
thread/process interval proof with fresh full FILETIME joins, an authenticated
original-handle cleanup guard and a two-capture packaged qualification. This
narrows E4 and collector-crash cleanup; production/path admission, pre-arm and
simultaneous guard/collector crash, actual reuse and sleep/wake remain open.
narrows E4 and collector-crash cleanup. The subsequent
[failure-boundary qualification](docs/roadmap/etw-failure-boundaries.md) passes
seven packaged cases including pre-arm reservation recovery, guard/broker loss
and abrupt Electron exit. Production/path admission, simultaneous guard/collector
crash, protected recovery, actual reuse and sleep/wake remain open.

## C — existing rules coverage

Expand Down
14 changes: 14 additions & 0 deletions docs/development/packaged-desktop-milestone.md
Original file line number Diff line number Diff line change
Expand Up @@ -210,6 +210,20 @@ two-capture PASS, exact tested source, evidence hashes and retained failed attem
Its Read issuer subset and original-handle guard cleanup do not close production
path attribution, protected installation or all remaining ETW gates.

### ETW failure boundaries

Use `--etw-failures` instead of `--etw` for seven planned captures covering
collector exit before start/arm, guard loss, broker loss, abrupt owned Electron
exit and the two-capture issuer/recovery regression. The profile independently
queries session presence/absence and checks visible failure and blocked retry.
It has a 15-minute parent deadline and stops at the first failed scenario. Each
capture needs a same-account UAC decision; a query-only elevated witness may also
be needed when ordinary queries are denied. See the [failure contract](../roadmap/etw-failure-boundaries.md)
for capability boundaries and remaining qualification limits.
The [2026-10-18 evidence](../recon/evidence/etw-packaged-failure-boundaries.json)
records seven actual packaged PASS cases at source `278f0754`, an independently
exercised elevated query witness and the retained initial pre-capture build failure.

### Other qualification

Without `--monitoring`, PASS covers the visible packaged-window lifecycle with modeled installation
Expand Down
Loading
Loading