Catalogue

The Verdog catalogue lists published workflow releases. Each release identifies a workflow at an exact Git commit and includes its description, graph, dependencies, and documentation.

Catalogue access follows the source repository. Workflows from public repositories are visible to every signed-in catalogue user. Workflows from private repositories are visible when the user's GitHub authorization can read the repository. See Permissions for access requirements.

Browse, inspect, import

Run Verdog: Browse Published Workflows from the VS Code Command Palette to review a workflow before adding it to your project:

1. Select a release to read its description, graph, dependencies, and README.
2. Select Inspect release to download the pinned workflow source and verify its published metadata.
3. Select Import into project… to choose a destination subroutine and dependency alias.

Browsing does not create a source checkout. Inspection opens a read-only workspace and does not run workflow nodes or modify your project. Import adds a dependency and binding; add a workflow call to use it in your graph.

The selected release is identified by its repository, workflow ID, and full 40-character commit hash. Selecting a different release updates the displayed documentation and the inspection and import target.

Metadata

A catalogue record includes a read-only graph, repository, workflow, Python package, commit, publication date, and visibility. Its requirements and dependency lists describe the packages and repositories needed by the workflow.

The README is read from the selected commit using your local Git credentials. If it cannot be retrieved, check your repository access and select Retry documentation. The workflow description and published graph remain available. Relative links refer to the selected commit; repository images become available after opening the inspected source.

Inspection

Inspect release downloads the selected commit and its Git submodules and checks that the source matches the published metadata. Open inspected source opens a read-only workspace containing the source and workflow canvas.

Inspection does not install Python dependencies, select a workflow interpreter, or execute workflow code. Editor support that requires installed dependencies becomes available after importing the workflow into a trusted project and preparing its environment.

Your Git credentials must allow access to the source repository and every nested dependency. See Consumer for the environment and dependency model.

If inspection fails, use Show output to read the error and Retry inspection after correcting the problem. Open source anyway allows you to read an incomplete inspection. Import requires a complete inspection with matching metadata.

To install dependencies or run the workflow, import it and choose Open Target Project. Environment setup and execution require trust in the destination project. Preview windows do not offer execution commands.

Import

The import review shows the repository, workflow, commit, destination project and subroutine, local dependency alias, and repository dependencies. It also identifies conflicts with an existing pin or alias.

Confirming adds the dependency pin and workflow binding to the destination project. If fetching or verifying the source fails, the project is left unchanged. If import succeeds but generation reports errors, the dependency and binding remain available for you to resolve those errors. Import generation sends project manifests and declared source files, including pinned dependencies, to the configured service without requiring an additional sign-in or a Verdog seat. Import does not add a call node or change the graph's control flow.

Matching metadata confirms the published structure against the selected source; it does not establish that the workflow's logic or dependencies are trustworthy.

Cache management

Use Verdog: Manage Catalogue Cache to remove one inspected release or all local catalogue data. Removing cached data does not change imported dependencies or source repositories.