Creative Capability Bridge
Review portable creative plans and export restricted static SVG to PNG with preflight checks and hash receipts, alongside transactional native adapters.
The problem it solves
Creative Capability Bridge 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.
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.6.0 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Review portable creative plans and export restricted static SVG to PNG with preflight checks and hash receipts, alongside transactional native adapters.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.6.0
Capabilities below come from the current project README and release documentation.
Add ccb preflight for input hashes, output/receipt collisions, font-file availability, target lifecycles, and optional policy or document inspection.
Add ccb compare-plans for metadata fields, added/removed/changed operation fields, and operation order without printing raw parameter values or file paths.
Add validated local JSON plan import and operation editing/reordering/removal to the reference builder.
Add target-order review and bounded session Undo/Redo; preserve coordinate metadata through builder edits.
Keep execution explicit and preserve existing inputs and outputs during review.
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
Changelog
Release notes from the canonical v1.6.0 source tag.
- Add a separate strict SVG-to-PNG export contract with read-only preflight, a restricted static SVG subset, bounded dimensions and source/output hash receipts.
- Stage and structurally verify PNG output, refuse collisions atomically and preserve inputs; existing native document-plan protocol remains unchanged.
All notable changes follow Keep a Changelog and Semantic Versioning.
- Add
ccb preflightfor input hashes, output/receipt collisions, font-file availability, target lifecycles, and optional policy or document inspection. - Add
ccb compare-plansfor metadata fields, added/removed/changed operation fields, and operation order without printing raw parameter values or file paths. - Add validated local JSON plan import and operation editing/reordering/removal to the reference builder.
- Add target-order review and bounded session Undo/Redo; preserve coordinate metadata through builder edits.
- Keep execution explicit and preserve existing inputs and outputs during review.
Add portable font mappings with missing-font diagnostics, transform/pivot fixture generation and version-scoped conformance evidence.
The fonts command maps requested families per adapter, reports missing/unmapped families, accepts an optional operator-supplied family inventory, and writes a new resolved plan only when no blocking findings remain. Blender mappings use validated local TTF/OTF files through font_file and actually load the font; file presence alone is not a rendering claim. The fixture generator writes 12 transform cases plus 12 round-trip plans with explicit adapter-specific pivot semantics. conformance-matrix records exact observed application versions, separates contract-only/native-smoke/document-adapter evidence, and verifies Blender transform round-trips when available. CI requires real Blender transforms/font loading and Inkscape rendering, then uploads the measured version matrix. GIMP native semantic acceptance remains unverified when unavailable. Sources are preserved and existing output files are refused.
ccb fonts plan.json --map font-map.json --inventory installed-families.json --output mapped-plan.json
ccb conformance-fixtures new-fixtures
ccb conformance-matrix --native --output new-version-matrix.json- Updated the runtime dependency to
cryptography50.x, the first release line patched for
CVE-2026-69247. Creative Capability Bridge uses Ed25519 signing rather than the affected PKCS#7 decryption APIs, but no longer permits installation with the vulnerable 48.x release line.
Quick start
The shortest documented path into the current release.
Before running these source commands, download the v1.6.0 source archive, extract it, and open a terminal in the extracted project folder containing README.md. Follow the tagged README for required runtimes and any platform-specific setup.
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.
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.6.0, published 2026-10-15.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Creative Capability Bridge v1.6.0
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 GitHub release tag. Fingerprint: 6db118190e5f1483.