Open-source AI interoperability compiler that turns one portable YAML capability spec into 15 auditable artifacts across 7 target families, including MCP, OpenAI/Codex, Claude, Gemini, DeepSeek, Meta/Llama and Chromium.
AI agent ecosystems expose similar capabilities through incompatible skill, function-tool, plugin, MCP and browser formats. Maintaining the same capability separately across providers creates duplicated engineering work, compatibility drift, inconsistent validation and a larger release-verification burden. D’AUBE needed a provider-neutral way to define a capability once while preserving explicit, inspectable outputs for each target ecosystem.
D’AUBE // BRIDGE² implements a provider-neutral YAML capability specification and compiler. A validated source specification is transformed into human-readable, diffable artifacts for MCP, OpenAI/ChatGPT/Codex, Claude, Gemini, DeepSeek, Meta/Llama and Chromium surfaces. The release pipeline includes automated tests, Ruff checks, deterministic MCPB packaging, package hashes, provider-compatibility fixtures, MCP Registry validation and isolated wheel smoke testing. Authentication and provider credentials remain outside the compiler, and generated artifacts do not silently execute tool definitions.
Release v0.1.3 establishes one auditable source-of-truth capability model that generates 15 integration artifacts across 7 target families. The recorded release gate shows 15/15 tests passing, Ruff clean, deterministic MCPB packaging, valid MCP Registry metadata, published SHA256 hashes and an isolated wheel runtime smoke test. The implementation keeps outputs human-readable and provider-specific compatibility claims explicit rather than hidden behind opaque generation.
For the demonstrated reference capability, one portable YAML specification produced 15 deterministic integration artifacts across 7 target families. Release v0.1.3 recorded 15/15 automated tests passing, Ruff checks passing, valid MCP Registry metadata, deterministic package hashes and an isolated wheel smoke test. This is a builder-reported technical/operational outcome; no client-confirmed hours saved, cost savings or revenue impact is claimed.