# Cross-Runtime Conformance Comparison

Version: `0.1.0-COMPILER-CONFORMANCE`
Date: `2026-08-22`
Status: `REFERENCE TEXT + JSON ADAPTERS / OTHER PROFILES CONTRACT-ONLY`

| Profile | Current implementation | Authority preservation | Declared limitation |
|---|---|---|---|
| lean text/manual | reference adapter | full required semantic trace in controlled text | machine-native structure falls back to text |
| IDE/coding agent | contract only | scope and authority fields required | execution suspended until target declares it |
| structured multi-agent | contract only | delegation/return metadata required | no agent runtime supplied |
| JSON/graph-capable | deterministic JSON reference adapter | typed state round-trip | no graph-engine execution implied |
| optional game engine | unavailable | fallback retains text evidence | engine execution rejected |

The text and JSON adapters agree on unit identity, status, result class,
P0/P1/P2 contents and hashes, semantic IDs, typed relations, agent authority,
finite-loop exhaustion, and upward-revisit state. Their layout and native
structure differ without semantic or authority loss.

The remaining profiles are conformance targets, not simulated runtimes. Their
negotiation records expose suspension, rejection, fallback, and declared loss.

## Comparison result

The first corpus supports a runtime-neutral interface claim for the declared
semantic subset. It does not support a universal compiler, deployed agent,
graph engine, game-engine adapter, or automatic source revision claim.