INTERPLANE / Developer documentation

Concepts

Understand the model, protocol and runtime boundary: proposed intent is not authority, and the runtime retains execution and approval control.

Intent is not authority

Model: proposed intent
  |
  v
INTERPLANE: normalized requests, provenance, policy decisions
  | eligible request or refusal
  v
Runtime: capabilities, approval, execution, results

The protocol describes the boundary; it does not give a model permission to act. Runtime-owned capabilities, policy and human approval decide which effects may execute. Untrusted retrieved text is content, never an instruction with runtime authority.

Trace each decision

Follow a model-native proposal through normalization, source labels, a policy decision and the runtime result. Rejected or ambiguous inputs must remain visible as refusals; do not silently repair them into authority.

Canonical sources: Core, Crossveil and Lenshift. The offline exercise makes this boundary observable.

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.