Function execute_realtime_frame 

pub fn execute_realtime_frame<B, S, M, T, C, H, F, E, K>(
    contract: &RealtimeIngressContract,
    payload_contract: &RealtimePayloadContract,
    frame: &RealtimeInputFrame,
    branch: &mut RealtimeGenerationBranch<RealtimePayloadBranch<M, T>, S, B::RandomState, C>,
    decisions: &RealtimeDecisionExecution,
    host_materializer: &mut H,
    tensor_mechanisms: &mut F,
    model_executor: &mut E,
    completion_mechanism: &mut K,
    context: &B::Context,
) -> Result<SubmittedRealtimeFrame<T, C>, RealtimeFrameCoordinatorError<H::Error, F::Error, E::Error, B::Error, K::Error>>
where
    B: SamplingBackend<Token = T, Logits = T>,
    B::RandomState: Clone,
    C: Completion + Clone,
    S: Sampler<B> + Clone,
    T: Clone,
    H: RealtimeHostTokenMaterializer<Tensor = T>,
    F: RealtimeFrameTensorMechanisms<Tensor = T>,
    E: PreparedRealtimeFrameExecutor<B, S, M>,
    K: RealtimeFrameCompletionMechanism<T, M, E::Retained, Completion = C>,

Coordinates one complete realtime frame on an already unpublished branch.

Host validation precedes opaque materialization. Schedule and payload-history changes are staged locally until preparation, model decisions, output completion, and exact native completion creation all succeed. Model state is necessarily mutated through its caller-owned transaction branch. Therefore, on any returned error the caller must discard the entire branch; the fair scheduler’s submission path already enforces that rule.