Runtime Adapter Authoring

Build PermeantOS runtime adapters with explicit contracts, conformance fixtures, and evidence requirements.

Runtime adapters are the boundary between PermeantOS state exchange and runtime-specific internals. Adapter changes must preserve shape, tokenizer, position, policy, and evidence contracts.

Read These First

Minimum Adapter Evidence

A runtime adapter should provide:

capability manifest describing supported import/export features;
deterministic fixture or conformance test;
tensor shape and dtype evidence;
tokenizer/span/position alignment evidence where decode continuation is claimed;
explicit limitations for runtime internals, private headers, model families, or unsupported layouts;
reverse export proof when the path claims round-trip continuation.

Conformance Tests

Run the relevant local tests before opening a PR:

python -m pytest   tests/test_runtime_adapters.py   tests/test_agent_framework_adapters.py   tests/test_pytorch_runtime_adapter.py   tests/test_llamacpp_runtime_adapter.py

For real-runtime claims, attach the proof report and update the evidence index.