Creative Capability Bridge
Plan, coordinate, execute, and verify transactional creative operations across Blender, Inkscape, and GIMP with policies, pipelines, rollback, and signed evidence.
The problem it solves
Creative Capability Bridge [](https://github.com/loganpendragonmultiverse/creative-capability-bridge/actions/workflows/ci.yml) [](https://github.com/loganpendragonmultiverse/creative-capability-bridge/actions/workflows/codeql.yml) [](LICENSE)
Who Creative Capability Bridge is for
- People who need a small, purpose-built utility instead of a broad platform.
- Users working with creative tools, transactions, policies who want the documented v1.3.1 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Plan, coordinate, execute, and verify transactional creative operations across Blender, Inkscape, and GIMP with policies, pipelines, rollback, and signed evidence.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.3.1
Capabilities below come from the current project README and release documentation.
[](https://github.com/loganpendragonmultiverse/creative-capability-bridge/actions/workflows/ci.yml) [](https://github.com/loganpendragonmultiverse/creative-capability-bridge/actions/workflows/codeql.yml) [](LICENSE)
Creative Capability Bridge (CCB) is a versioned protocol, adapter toolkit, and reference plan builder for expressing common creative operations once and translating them for different applications.
Version 1.3 supports text creation, text updates, and explicit transforms through Blender, Inkscape, and GIMP 3 adapters. It adds transactional execution, rollback backups, resumable and selective plans, semantic document diffs, coordinate normalization, policy profiles, dependency-aware multi-document pipelines, adapter conformance checks, and optional Ed25519 signatures for bundles and receipts. Version 1.3.1 updates the signing dependency to the patched cryptography 50.x release line.
Open the plan builder
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Windows
- macOS
- Linux
- Web
Built with
- Python
- JavaScript
- Blender
- Inkscape
- GIMP
Quick start
The shortest documented path into the current release.
Requires Python 3.10 or newer. Native execution requires the selected application on PATH; GIMP support targets GIMP 3's bundled Script-Fu batch interpreter. Inkscape is optional unless native rendering is requested because ordinary SVG editing is handled directly.
python -m venv .venv
# Windows: .venv\Scripts\activate
# macOS/Linux: source .venv/bin/activate
python -m pip install .
ccb validate examples/inkscape-text.json
ccb preview examples/inkscape-text.json
ccb execute examples/inkscape-text.jsonThe example writes examples/output/inkscape-text.svg. It does not change an input file.
For Blender:
ccb doctor
ccb preview examples/blender-text.json
ccb execute examples/blender-text.jsonFor GIMP 3:
ccb preview examples/gimp-text.json
ccb conformance gimp --native
ccb execute examples/gimp-text.json --receipt gimp-receipt.jsonFor guarded, resumable work:
ccb key generate ccb-private.pem ccb-public.pem
ccb bundle create plan.json project.ccb.zip --signing-key ccb-private.pem
ccb bundle verify project.ccb.zip --public-key ccb-public.pem --require-signature
ccb execute plan.json --only titles --state run.state.json --receipt run.json
ccb execute plan.json --state run.state.json --resume --receipt resumed.json
ccb policy check plan.json examples/safe-policy.json --receipt run.json
ccb pipeline validate examples/two-document-pipeline.jsonThe browser plan builder creates JSON locally. It does not upload documents or execute applications.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
- Version 1 is file-oriented. It does not synchronize with a selection in an already-open GUI.
- Inspection exposes supported metadata, not a complete application scene graph, and cannot guarantee that every native object is semantically editable.
- Unsigned bundles verify integrity but not publisher identity or asset licensing; license notes remain operator-supplied. Optional signatures prove possession of a private key, not the real-world identity behind that key.
- Receipts record and hash one local execution. Optional signatures protect the receipt payload from later alteration but do not independently prove that the native application behaved honestly.
- Blender, Inkscape, and GIMP are not interchangeable. CCB exposes a common core and rejects unsupported dimensions rather than inventing equivalence.
- The Blender font-family field records the requested family because reliable cross-platform font resolution needs a future explicit font-mapping contract.
- Inkscape document edits are deterministic SVG operations; Inkscape itself is invoked only for optional native preview rendering.
- Coordinate conversion covers pixels, points, physical units, Blender units, origins, and Y-axis direction. Arbitrary pivots and full transform-order negotiation remain outside protocol v1.
- GIMP inspection reports portable layer identifiers, dimensions, and offsets; it does not expose every XCF property or claim full semantic equivalence with SVG or Blender scenes.
- Intuitiveness requires real user research and cannot be established by automated tests alone.
- Native compatibility is version-sensitive. See the [compatibility policy](docs/compatibility.md).
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
CCB runs locally on Windows, macOS, and Linux wherever Python and the selected application are available. The static plan builder runs in modern browsers and does not transmit or store content.
License and release
Creative Capability Bridge is published under MIT. The current cataloged release is v1.3.1, published 2026-08-07.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Creative Capability Bridge v1.3.1
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical local repository. Fingerprint: 081a5bd9f7af0cf9.