Notes · Integrity Map
The 2026-09-15 public-source snapshot closed the known reachable evaluation backlog for the target set. Remaining uncertainty is typed: non-public implementation, future releases, and surfaces that had not shipped. Research is no longer the critical path. Canonicalization, implementation and conformance tests are.
Overview
A policy can exist, be installed, and even be thoroughly tested on its primary path while effect-capable alternate admission paths never enter the policy lifecycle. Declared policy is not installed policy, and installed policy is not effective coverage. For every effect-capable lane to which a policy is semantically applicable, the lane must enroll before the first authority-bearing effect. Exempt lanes must be classified as query-only, read-only or non-authoritative.
NVIDIA Dynamo router flow-control and classifier-lifecycle issues, including stateful and Rust admission paths that can skip an installed classifier.Qwen Code request paths that skipped a consent gate until the wrapper was reused. DeepSeek Harness entrypoint verification.
The intersection of effect-capable lanes and declared applicability must sit inside the enforced set.Per-bug guards on alternate paths are not the fix.
Evidence and state have to be projected into the shape the consumer actually requires before transport.Replication plus later filtering is not the same property.
Non-public runtimes, paper-deep internals and unshipped surfaces remain watch items with named reopen triggers.They are not silent fills.
Proof
Closure is a dated public-source snapshot. Future commits, private implementations and later public surfaces reopen only their implicated family.