Expand description
Coding harness projected from the log.
The scheduler does not keep a parked question or a tool confirmation in
process memory. Those waits are phases of the fold. The runtime runs a
transition only when the fold enables one. Answering or confirming appends
a fact, and the next resume derives the tool or model call from that fact.
Structs§
- Coding
Services - Coding
View - Completion
Request - Harness
Config - Configuration checked before an actor exists. A zero step limit or a zero model attempt count cannot construct a harness.
- Pending
Confirmation - Pending
Question - Prepared
Tool Execution - Tool
Admission Identity V1 - Tool
Call - Tool
Effect Observation V1 - Tool
Execution Result V1 - Tool
File Identity V1 - Tool
Invocation Identity V1 - Tool
Path Change V1 - Tool
Preparation Request - Tool execution for the tool transition.
- Tool
Prepared V1 - Tool
Spec
Enums§
- Coding
Phase - Model
Decision - Tool
Execution Outcome - Tool
File Kind - Tool
Observation Completeness - Tool
Recovery Policy
Constants§
Traits§
- Compactor
- Completion
- Model call for the infer transition.
- Tool
Runner
Functions§
- answer_
fact - background_
output_ fact - One background-task output line as a fact on the session’s one log.
- coding_
actor - Stock Meta Harness:
system + tools + budget + compact + infer([scheduler]). - coding_
scheduler - Infer-loop scheduler (model / tool / compact / budget deny phases).
- confirm_
fact - ingest_
coding - ingest_
coding_ with_ cancel - merge_
coding_ view - message_
fact - resume_
coding - resume_
coding_ with_ cancel - tool_
args_ digest