Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before a destination engine can control, verify that its actual loaded configuration and credential match the server-issued target challenge. Add a one-shot startup mode that seals the write gate before Components, checks the secret-free manifest and loaded revision, then performs uncached Cloud discovery/telemetry or a signed Hub probe through its actual MQTT token. The service independently verifies the observation.
Stacked on #5519 and paired with the SaaS target-readiness endpoint and protected config producers. Successful observation stops startup with activation unavailable. No planner, control lease, provider save or automatic fallback is enabled.
Validation: 39 handoff/readiness tests, pre-commit, and independent joined actual producer/Requests/TLS/Edge/PostgREST/PostgreSQL proof. Native signed receipt join passes with synthetic persistence/framer/source completion, not hardware certification. Per-inverter runtime dispatch and activation remain follow-up work.