# Method and evidence boundary — 2 October 2026

Cutoff: 2026-10-02 08:55 UTC. This is an incremental source-data audit in Raven’s own environment.

The September 4 release is retained unchanged. Twenty-three explicit telemetry paths were read on two hosts. Each acquisition captured a fixed byte prefix and independently re-read that prefix to detect concurrent changes; all 23 matched. Twenty-one historical file prefixes matched their September hashes. Two additional paths have the real identity of the replacement collector host. No archive discovery, source deletion, or Runtime mutation was performed.

CSV counts use logical records, excluding headers; JSONL counts use objects. Existing timestamp precedence and explicit-offset/epoch rules are retained. Timestamp-free or naive-time rows and records after the cutoff are excluded from UTC metrics. Failed probe attempts and state records remain counted. Schema-valid is not equivalent to measurement-successful.

Source-record dates are a union with the frozen historical date set, not uptime. The retained record calendar includes 13 February records without the same producer-bound status as the earliest confirmed measurement on 14 February. Single-dataset distinct payloads normalize the timestamp and JSON key order before exact payload comparison; they are not a global event total.

The monthly table uses the fixed 23-file current source set. Collector start/stop times, cadence and migration differ. October is partial. Neither volume changes nor latency changes establish an effect caused by Raven.

The 501 LTE/fiber cycles remain the June 8–10 historical population. This update does not certify additional paired cycles, additional collector families/domains, or new Runtime outcomes. Prior 351-file, 229-content, 4.86 GB and 42,117,279-row footprint figures remain historical and are not added to current totals.

Private evidence retains acquisition hashes, source bindings, parsing code, profile results and review. Public files expose aggregates only. Their hashes verify bytes, not claims. This scoped update does not change the independently established maturity or pilot readiness of the system.