aidens-provider-kit
Provider construction, execution, routing truth, readiness, and certification fixtures.
The catalog assigns 7 packages to this responsibility boundary. This page derives its vocabulary, topology, publication state, and maturity profile directly from those audited records.
Counts expose what the catalog actually contains. They do not convert package metadata into production-readiness or quality claims.
5 package-specific limitation entries remain visible across this domain.
28 unique capability statements are attached to packages in this domain. The language below is catalog evidence, preserved without expanding the claim.
construct and invoke providers
record route truth
backend readiness matrices
certification fixture artifacts
tool registration and exposure planning
path/boundary validation
permit-aware safe dispatch
invocation reports
async ComfyUI REST client
WebSocket progress tracking
workflow construction
prompt submission and result retrieval
strip reasoning and markdown wrappers
extract structured JSON/YAML
repair common malformed output
avoid a second LLM parse call
prompt templates
Ollama and optional OpenAI calls
defensive structured parsing
streaming and sequential chaining
provider-agnostic tool definitions
registry and lookup
invocation dispatch
typed tool receipts
Ollama vision requests
image tagging and captioning
structured response parsing
local-model HTTP client
Edges are derived from sibling dependency declarations. Cross-domain traffic describes manifest topology, not runtime call direction, frequency, or activation.
Each record has a stable URL with its complete catalog scope, capabilities, targets, features, relationships, registry evidence, update trail, and known limits.
Provider construction, execution, routing truth, readiness, and certification fixtures.
Tool registry, exposure planning, boundary validation, and permit-aware dispatch.
Async Rust client for ComfyUI — REST, WebSocket progress, and workflow building
Production-grade parser for extracting structured data from LLM responses. Handles think blocks, markdown fences, malformed JSON, and real-world model output without an additional LLM call.
Reusable node payloads for LLM workflows: prompt templating, Ollama calls, defensive parsing, streaming, and sequential chaining
Provider-agnostic tool contracts, registry, dispatch, and receipt plumbing for llm-pipeline
Robust Ollama vision model toolkit for image tagging and captioning
This route reorganizes audited package metadata. It does not add implementation claims or expose access-controlled source.
p32-schema-compat / 011027f77fc7a53c6ecb05300d5c34144370fa3b