Expand description
Engine — the long-running stateful runtime plus the with_state
helper (R1-R4 discipline).
The engine owns the Domain side of the Data / Domain split:
flow control (dispatch / verdict), state (EngineState), and the
submit_output / output_tail surface that feeds it. Data-plane
traffic (Big Response bodies) is delegated to the output_store module
plus its paired SpawnerLayers and passes through here without the
engine core needing to grow.
Structs§
- Engine
- Process-wide long-running runtime. Cheap to
clone()— anArclives inside.
Enums§
- Fold
Parse - How [
fold_final_and_parts] treatsValue::Stringcontent when assembling the BP-chain value — the fold half of theSUBMIT_FORMAT_KEYcontract.
Constants§
- SUBMIT_
FORMAT_ KEY AgentContextView.extrakey carrying a step’s declared submit format. Declared through the GH #21 meta channels (Blueprint.metas/AgentMeta.ctx/ step-level$step_meta) and folded into the view at spawn time byAgentContextMiddleware. Read in two places: the HTTP submit lane (mlua-swarm-server’sresolve_submit_value, where"json"means strict parse-or-422) andEngine::fold_parse_mode_for(whereSUBMIT_FORMAT_TEXTopts the step’s fold out of the default lenient container parse — seeFoldParse).- SUBMIT_
FORMAT_ TEXT - The
SUBMIT_FORMAT_KEYvalue that opts a step’s fold out of lenient container parsing (FoldParse::Raw): every string the worker submitted — final body and staged parts alike — folds into the flow ctx as itself, even when its bytes would parse as a JSON object or array.