docs(perception): record clock route A/B/A and continuous LAN canary

This commit is contained in:
DCCONSTRUCTIONS
2026-09-02 22:14:58 +03:00
parent 59a74a3677
commit 75a5320756
3 changed files with 154 additions and 3 deletions
@@ -887,3 +887,20 @@ inside the same2s horizon would not remove the measured WAIT.241 local/198 Worke
tests PASS,129 measured source hashes match code48835a0. Next investigate control-loop
scheduling/transport before another full-graph qualification, without budget widening.
[Detailed evidence](../../experiments/perception/PERCEPTION_STREAM_STAGE2_JOINT_START_2026-09-02.md).
## Stage 2 increment 17: transport-specific clock readiness (2026-09-02)
Clock-only A/B/A separates route effects from scene processing: SSH/Tailscale48/96,
strictly host-key-pinned SSH over confirmed LAN94/96 (only initial2 unready), return
to Tailscale53/96. All288 exchanges reconstruct; application handler/loop delays do
not alone explain ~100ms request tails. LAN is an observed connection option, not
a new model dependency, universal speedup or permanent product/default route change.
One full LAN canary returns32/32 byte-exact/reference-exact scenes at1x with no WAIT,
drop or reconnect;50 clock exchanges reconstruct,48 after initial warmup remain ready.
All129 prior runtime source files and the model/effective config remain unchanged.
Latency205.864/213.751ms p95/p99 still fails125ms; only12/32 scenes are fully fresh.
Do not equate complete output accounting with usable geometry/policy or autonomous
readiness. Next instrument data-plane stage boundaries before optimizing remaining
tails; no gate widening.245 local/202 Worker tests PASS,131 source hashes matched.
[Detailed route and full-profile evidence](../../experiments/perception/PERCEPTION_STREAM_STAGE2_LAN_ROUTE_2026-09-02.md).