# Know the target.

> Track the runtime environments that may host managed capabilities and make compatibility evidence part of every planned deployment decision.

Canonical: https://rangoon.ai/product/harnesses/

Status: In active development. Product screenshots are design previews with illustrative data. No general availability is implied.

## 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.

### Target-aware preparation

Deployment planning starts from what a target can represent, not from a promise that all harnesses behave alike.

## 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.

## 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.


## More information

- [Documentation index](https://rangoon.ai/llms.txt)
- [AI access and policies](https://rangoon.ai/ai/)
- [Source repository](https://github.com/hypler-dev/rangoon)