INTERPLANE / Developer documentation

Writing an Adapter

Follow INTERPLANE's canonical pinned Rust adapter guide, host-owned decisions and conformance requirements without assuming universal support.

Start with the canonical contract

Use the pinned Writing an adapter guide for the Rust reference, including its to-do list example and exact interfaces. This page is orientation, not a second SDK or a claim that every runtime has a supported adapter.

  1. Declare only capabilities your runtime actually implements.
  2. Normalize requests without inventing missing or ambiguous arguments.
  3. Keep capability decisions, approval and execution in the host runtime; model text cannot approve itself.
  4. Record results and refusals, then run the canonical conformance checks against the adapter.

Read Concepts before wiring execution, and Conformance before describing support. Check STATUS.md at the source pin rather than assuming planned stages are available.

Source and verification

Status snapshot: 68c00986b4bbb9e91a0a1efb11973c9253ecb0b6. Generated 2026-10-30T04:07:09Z. Raw facts.

Spark verification: NO VERDICT The Spark has not published a verdict for this commit yet.

A successful reference example is not the Spark verdict. Planned work is not implemented support. Versioned status and canonical STATUS.md retain those distinctions.