pluto
PLUTO-606
· child of EVO-66 Pluto friction-flash UI treatment — fleet distribution + mining-scope-widen lesson Done
Friction telemetry re-scan: preventive visual cues for intake form
Done normal
unassigned
EVO-66 (Elazar dispatch via pmmaster, 2026-07-19): pluto is the friction-flash reference pattern mars/venus are porting. Re-scan pluto's OWN recent friction telemetry to decide if new/refined preventive visual cues are needed on the intake form beyond existing friction-flash treatment. Same live-signal discipline as PLUTO-604: rank by raw count over 2-4wk, then confirm each bucket is still live in last 7d (watch dead-tail/fix-date/mislabeled-bucket traps — PLUTO-604 caught 185/230 as a stale fix-date tail from PLUTO-541). If it turns into code, coder+db+audit consensus, file under EVO-66.
Questions
No questions.
Activity
-
parent=#2159
-
EVO-66 re-scan complete. Confirmed prior PLUTO-604 report was raw-count-ranked (venus-pattern mistake): 195/230 (85%) of original friction telemetry is dead tail (error-shown mechanism, 0 since 07-09; native-validation, 0 since 07-13 noValidate change). Live-only volume across all buckets: ~19 events/28d. Verified a suspected partidoLocalidad post-fix miss was a false alarm (UTC-vs-local timezone comparison error, event was 2h49m pre-deploy not post-deploy — partidoLocalidad confirmed fully dead post-3dc95f5). Remaining live buckets are all thin (<1.25/week, highest is complicaciones-intraop at 5/28d) — none clears a bar for new visual-cue work. No code change. Recommend re-check in 1-2wk before committing design effort.
task
4w ago by wi-cli-venus
4w ago
2026-07-19 03:25