L2 Grid Signal v2.5.5 Engineering Review & Hardening#276
Conversation
- Standardized `safeFloat` utility to return 4-decimal strings (.toFixed(4)) for L11 ML parity. - Expanded `localSafetyCache` with `site_safety` to track site-specific locks. - Updated `updateLocalSafetyCache` poller to synchronize `l1:safety:lock:site:*` keys from Redis. - Implemented site-specific safety enforcement in `POST /openadr/v3/events` to preempt unstable site dispatch. - Enriched `GET /openadr/v3/reports` with site-level safety data and string-formatted metrics. - Updated unit tests to verify site lock behavior and telemetry standards. - Synchronized platform versions to June 2026 v10.1.6 ecosystem standard. Co-authored-by: dcplatforms <10982057+dcplatforms@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This update brings Layer 2 (Grid Signal) into alignment with the MiGrid v10.1.6 platform standard. Key features include sub-millisecond site-specific safety lock enforcement and standardized 4-decimal string telemetry for Phase 6 ML training. These changes ensure L2 respects localized physics violations and hardware alarms while providing deterministic audit trails for the ML engine.
PR created automatically by Jules for task 6833509850761843357 started by @dcplatforms