Document plugin tap governance and trust#32
Merged
eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom May 7, 2026
Merged
Document plugin tap governance and trust#32eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom
eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom
Conversation
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.
What
Documents DDPlugins as the NVIDIA-maintained curated first-party tap for Data Designer and adds trust guidance for default and non-default tap install flows.
The update covers:
Why
Issue #24 needs the docs to make tap governance explicit before the CLI follow-up work references this repository as the canonical trust model. A tap is not just a search preference; it points users at Python packages that will be resolved, installed, and imported.
Usage
First-party plugins should land in DDPlugins only when they are NVIDIA-maintained, broadly useful to Data Designer users, and have an accountable CODEOWNER.
External plugins can publish a schema v2 tap instead of landing here. The tap should be exposed as an unauthenticated raw JSON catalog URL, for example:
Future CLI install flows can reference the documented confirmation shape for non-default taps:
How
Added scoped prose to hand-authored docs only:
README.mdfor repository-level governance and trust languagedocs/authoring.mdfor first-party contribution criteria and external tap guidancedocs/index.mdfor the docs landing page repository contractdocs/tap-catalog-schema-v2.mdfor schema v2 raw JSON requirements and CLI confirmation semanticsGenerated plugin docs were not edited manually.
Validation
make syncgit diff --checkmake docsmake check