Conversation
…ed-contracts-+-require-capability-advertisement' of https://github.com/blindzero/IdentityLifecycleEngine into issues/42-Refactor-provider-contracts-to-capability-based-contracts-+-require-capability-advertisement
…ed-contracts-+-require-capability-advertisement' of https://github.com/blindzero/IdentityLifecycleEngine into issues/42-Refactor-provider-contracts-to-capability-based-contracts-+-require-capability-advertisement
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
blindzero
deleted the
issues/42-Refactor-provider-contracts-to-capability-based-contracts-+-require-capability-advertisement
branch
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.
Summary
This PR introduces a capability-based provider contract to IdLE.
Steps can now declare required capabilities, providers explicitly advertise
supported capabilities, and the engine validates availability during plan
build (fail-fast).
Key changes
GetCapabilities()RequiresCapabilitiesWhy
This establishes a clean, explicit contract boundary between steps and providers,
enabling deeper provider implementations without hard-coding assumptions into
the core engine.
Follow-ups
Issues
Closes #42