Unified theme family · runtime compilation · integrity
.cctheme format: one unified theme family, compiled by client Adapters
Learn how family.json, unified-theme.json, allowlisted assets, integrity validation and runtime Adapter compilation work across Codex, WorkBuddy, Doubao and Kimi client lanes.
Architecture reviewed
Required archive roots
family.json identifies the theme family and supported contract. unified-theme.json contains shared design data. assets/ contains declared local media used by that design.
This architecture replaces the old model that embedded a separate compiled target directory and exact client version inside every user-facing package.
- family.json — family identity and contract
- unified-theme.json — shared design data
- assets/ — allowlisted declared media
- manifest and integrity records — file inventory and hashes
Runtime Adapter compilation
The CC Theme App first verifies and imports the package. It then discovers supported clients and lets the user choose a client card. The selected Adapter compiles only capabilities it supports.
Public package targets currently use mac-codex for ChatGPT Desktop/Codex mode and mac-workbuddy for Tencent WorkBuddy. mac-doubao belongs to the validation lane, while mac-kimi is experimental until Manager registration and real QA evidence are complete.
- Theme family ID
- Adapter ID
- Adapter capability version
- Exact client evidence from the compatibility matrix
Rejected content
Theme archives are data, not arbitrary application code. Import should reject traversal, absolute or undeclared paths; scripts; raw CSS; HTML; SVG; remote media URLs; unsupported file signatures; and integrity mismatches.
- No JavaScript, shell or PowerShell
- No raw CSS, HTML or SVG
- No remote media URL
- No executable installer inside the theme
Compatibility and integrity are separate
SHA-256 can show that a package matches a published artifact. Compatibility records show whether a specific client + Adapter + theme combination has passed verification. Neither should be inferred from the filename alone.
- EVA WorkBuddy verified
- EVA CodeX visual verification not passed
- Intel Mac and Windows unsupported
- App software trust is evaluated separately
.cctheme format FAQ
Does one package target only one exact app version?
No. The unified theme design does not store a real host version. Runtime context supplies Adapter capabilities and compatibility evidence.
Can the same package be compiled for two clients?
Yes when both Adapters support the declared capabilities and the exact theme × target combination is verified.
Does that guarantee identical pixels?
No. Host surfaces differ; reproducibility means the same package and compile inputs can be reviewed, not that two clients render identically.
Is the CC Theme App inside the archive?
No. Theme data and App/Adapter software remain separate trust boundaries.
Can I import a package on this website?
The website is the gallery and documentation surface. Download CC Theme and import the package in the unified Mac app.
Architecture and contracts
The unified architecture document and reviewed contracts are the source of truth.