Dated source reference. Current release status: handoff state. Full original relative paths are in the developer archive.

Dependency-write observations

native/presentation/packet-dependency-watch.hpp is a diagnostic ledger for bounded input ranges. It is separate from the active resource revocation fence and cannot authorize a draw, omission or callback.

A watch belongs to one packet incarnation, source ledger, bank and consumer thread. Its ranges are validated, sorted and merged. Classified writes to disjoint ranges leave it stable. Overlapping writes and every unclassified write revoke it before their unsafe effects. Finishing a write cannot restore a revoked watch. An already-active conflicting or unknown write prevents a new watch. Missing closure, wrong-thread use, capacity exhaustion and identity exhaustion cannot silently recover authority. Packet incarnations cannot be rearmed or replayed through an older token.

The observer records write tickets on their originating threads. It uses only short internal metadata transactions and performs no native calls or resource reads. The current tests cover eight concurrent producers and 8,000 disjoint writes, later overlap, unknown writes, active conflicts, packet/bank/thread identity, capacity and monotonic revocation. Local ASan/UBSan/TSan and Windows fixtures establish that bookkeeping scope.

Native write-impact classification and complete coverage remain unimplemented. Each original allocator, source, descriptor, queue, context and resource path would need a bounded, source-backed impact description established before its first write. An unknown path must remain global. Heap metadata, parents and children, reallocation, bulk clear, constructor/destructor entry, reset and abandoned calls require explicit handling. A readable range or a successful component test cannot supply that evidence.

The production adapter still uses its existing strict fence. Enabling scoped execution would require a separate consumer/commit protocol, all native impact bindings, fault tests and exact-candidate game acceptance. This diagnostic ledger delivers none of those permissions.