René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Supply the bound domain to provider initialization","articleBody":"The spec now supplies the bound `domain` to a provider's `initialize` function, and adds an opt-in `domain-scoped` provider declaration that the API enforces by binding such a provider to at most one `domain`. This lets stateful providers (e.g. an OFREP static-context provider with a persistent cache) scope their state to a single, unambiguous `domain`.\n\n### What needs to happen\n\n- Pass the bound `domain` (if any) to the provider's `initialize` when it's registered via the provider mutator\n- Extend the provider `initialize` to accept the optional `domain` (non-breaking, additional optional parameter)\n- Add a way for a provider to declare itself `domain-scoped`\n- Enforce that a `domain-scoped` provider is bound to at most one `domain`, rejecting any attempt to bind an already-bound instance to another `domain`\n- Associated testing and docs\n\n### Links\n\n- Parent issue: https://github.com/open-feature/spec/issues/403\n- Spec sections: [1.1 Flag evaluation](https://openfeature.dev/specification/sections/flag-evaluation), [2.4 Initialization](https://openfeature.dev/specification/sections/providers)\n","author":{"url":"https://github.com/jonathannorris","@type":"Person","name":"jonathannorris"},"datePublished":"2026-07-02T20:25:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/615/python-sdk/issues/615"}