Version independently
Harness behavior changes quickly, so adapter evolution must remain inspectable and separately versioned.
Harness adapters
Translate with evidence.
Never pretend equivalence.
Versioned adapters are planned to discover native configuration, map supported concepts, compile canonical assets, and explain target-specific limits.
Product direction · In active development
01
A precise adapter job
An adapter should discover supported inputs, map them into the canonical model, report capabilities, generate target artifacts, and validate output.
02
Show the transformation
Planned compilation views should surface generated file structure, transformation rules, unsupported behavior, warnings, dependencies, and output differences.
Compatibility is not binary
Adaptation and partial support need a clear explanation before a team relies on them.
03
Still being designed
No adapter SDK, supported harness list, certification, or production compatibility guarantee is announced here.
Build for review
The intended ecosystem prioritizes traceable adapters over opaque conversions.
