docs(capabilities): define external provider contract - #243
Closed
627150795 wants to merge 1 commit into
Closed
Conversation
8 tasks
7 tasks
Collaborator
|
Thank you for preserving this research. We are closing this PR as a source record for the Capability, authority, and resources consolidation tracked in #277. This is not a finding that the content is wrong. The current queue contains overlapping contracts from one stale base, so we will extract only settled boundaries into at most one successor record, citing this PR explicitly. Please do not spend time rebasing this 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
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.
Problem\n\nOpenPI can compose external Skills, MCP servers, and Pi packages, but the repository did not yet define a reviewable boundary for their permissions, ownership, child safety, replay safety, credentials, or lifecycle evidence.\n\n## Value\n\nGive contributors and maintainers one explicit contract for integrating Browser, Web, GitHub, Computer, Security, and media providers without turning OpenPI into a second provider stack or silently widening child authority.\n\n## Approach\n\n- Add a design contract for provider identity, version, source, schema fingerprint, permissions, owner scope, safety classification, lifecycle, bounded results, credential ownership, and prompt-shape impact.\n- Define fail-closed intersection of parent authority, provider declaration, and child/Workflow policy, with Replay requiring an additional stable side-effect-free classification.\n- Define cancellation, cleanup, uncertainty, and result receipts and map the contract to existing OpenPI and Pi ownership seams.\n- Add a validation matrix and explicit non-goals so real provider work is only implemented when a concrete integration needs it.\n\n## Validation\n\n- git diff --check — passed\n- bun run lint — passed\n- bun run typecheck — passed\n- No runtime behavior was changed; this is a documentation/design-only PR.\n\n## Impact\n\n- User-visible behavior: None.\n- Model-visible context/tools: None.\n- Runtime/lifecycle: None.\n- Persisted config/data: None.\n- Compatibility/risk: Documentation only; it explicitly avoids adding a provider registry, external tool inheritance, or credential storage.\n\nFixes #169