L3 VPP Weekly Review & High-Fidelity Refinement

[dcplatforms]

Weekly Review: L3 VPP Aggregator (v3.3.0)

This update synchronizes the Layer-3 (L3) VPP Aggregator with the latest platform-wide standards (March 2026) and prepares the service for the Phase 6 'AI & Optimization' transition.

Key Changes:

1. High-Fidelity Aggregation: Upgraded the background capacity aggregation engine to provide a granular breakdown of EV vs. BESS resources per region. This data is exposed via a new Redis key vpp:capacity:regional:high_fidelity and persisted in the vpp_capacity_history table to provide ground truth for the L11 ML Engine.
2. IEEE 2030.5 Expansion: Enhanced the grid_signals Kafka consumer to support specific DERControl operation modes (Peak Shaving, Frequency Response, Volt-VAR), moving beyond a simple skeleton to a functional dispatch routing structure.
3. Bug Fixes & Hardening:
   • Fixed a critical error where legacy regional mapping attempted to access properties on a numeric value.
   • Ensured all regional Redis keys (legacy and high-fidelity) are atomically cleared when an L1 Physics safety lock is active.
   • Hardened ISO normalization across all internal logic to maintain strict parity with L2 and L4.
4. Testing: Expanded the unit test suite to include direct verification of the updateGlobalCapacity background logic, specifically targeting the regional EV/BESS breakdown.

Strategic Alignment:

• L11 ML Engine (P0): Unblocks demand forecasting training by providing high-fidelity timeseries data.
• L4 Market Gateway (v3.7.0): Maintains backward compatibility while providing the audited capacity data required for CAISO/Nord Pool bidding.
• Phase 6 Transition: Moves L3 from 'Enterprise Scale' (Phase 5) toward 'Advanced Grid Services' (Phase 8).

---

PR created automatically by Jules for task 16709874403689938190 started by @dcplatforms

[google-labs-jules]

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.