Skip to content

L4 Market Gateway v3.8.9: Hardware-Aware Bidding & Telemetry Hardening#277

Open
dcplatforms wants to merge 1 commit into
mainfrom
l4-hardware-health-v3.8.9-16231099730156340809
Open

L4 Market Gateway v3.8.9: Hardware-Aware Bidding & Telemetry Hardening#277
dcplatforms wants to merge 1 commit into
mainfrom
l4-hardware-health-v3.8.9-16231099730156340809

Conversation

@dcplatforms

Copy link
Copy Markdown
Owner

This update synchronizes L4: Market Gateway with the v10.1.6 platform standard, focusing on "Hardware-Aware Resilience."

Key enhancements:

  1. Hardware Health Penalty: Implemented logic in BiddingOptimizer.js and index.js to reduce bidding confidence based on regional hardware alarms reported by L7. Each alarm deducts 0.05 from the confidence score (max 0.30 deduction).
  2. Telemetry Hardening: Standardized all physics and confidence scores to 4-decimal strings using the safeFloat utility to maintain parity with L11 ML Engine requirements.
  3. Regional Alarm Sync: The localSafetyCache now polls Redis for l4:regional:alarms:<ISO> to ensure sub-millisecond access to hardware health data during the bidding cycle.
  4. Auditability: Added regional_alarm_count and hardware_penalty to FIX-PROT-AUDIT metadata and MARKET_PRICE_UPDATED Kafka payloads.
  5. Security: Verified and reinforced fleet_id rejection for global aggregate training data endpoints.

Verified with 29 passing tests in services/04-market-gateway.


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

- Bump version to v3.8.9
- Enhance localSafetyCache to sync regional alarm counts from Redis
- Implement bidding confidence penalty (-0.05 per alarm, capped at 0.3)
- Standardize all scores to 4-decimal string format (.toFixed(4))
- Include hardware penalty metadata in bid audits and Kafka payloads
- Recalculate High-Fidelity status post-penalty to ensure bidding safety
- Audit global training endpoints for fleet_id security enforcement

Co-authored-by: dcplatforms <10982057+dcplatforms@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant