Target-aware preparation
Deployment planning starts from what a target can represent, not from a promise that all harnesses behave alike.
Harness Manager
Know the target.
Respect its limits.
Track the runtime environments that may host managed capabilities and make compatibility evidence part of every planned deployment decision.
Product direction · In active development
01
Describe the runtime honestly
A planned harness record can cover runtime family and version, asset support, model and tool capabilities, hooks, context behavior, health, and drift.
02
Classify compatibility
Proposed reports distinguish fully compatible, compatible with adaptation, partially compatible, and unsupported outcomes.
Explain the reason
Warnings may point to missing tools, unsupported hook lifecycle, context limits, schemas, or permission models.
03
Use adapters as versioned boundaries
Harness adapters are planned to discover, import, map, compile, test, and report compatibility for a supported target.
Support is evolving
No individual harness adapter is represented here as released or certified.
