Skip to main content

Module config

Module config 

Source
Expand description

The A–H config model, one module per section.

The split follows the template’s own section boundaries rather than Rust convenience, so “where does stop_gates live” has the same answer in the docs, the schema, and the code.

Every struct here carries deny_unknown_fields. Without it a misspelled key is silently dropped and the loop runs with a default the author never chose — which is exactly how max_revisions_per_node came to be documented in four places and read in none.

Re-exports§

pub use constraints::ConstraintSet;
pub use constraints::Constraints;
pub use context::ContextPolicy;
pub use default_skills::is_safe_repo_url;
pub use default_skills::DefaultSkill;
pub use default_skills::SkillOrigin;
pub use gates::StopGates;
pub use goals::Goal;
pub use graph::Concurrency;
pub use graph::GraphSpec;
pub use graph::NodeSpec;
pub use graph::Role;
pub use graph::Tier;
pub use guidelines::parse_chain;
pub use guidelines::ExecutionGuidelines;
pub use guidelines::Guideline;
pub use guidelines::Phase;
pub use info::InfoItem;
pub use providers::ProviderKind;
pub use providers::ProviderRouting;
pub use providers::ProviderSpec;
pub use skills::AcquisitionSource;
pub use skills::SkillPolicy;
pub use success::SuccessScenario;
pub use triggers::Trigger;
pub use validation::CompareOp;
pub use validation::Detector;
pub use validation::Mode;
pub use validation::Validation;
pub use work::WorkItem;

Modules§

constraints
Section H — constraints applied per node or globally.
context
What each iteration is allowed to remember.
default_skills
Section J — sub-agents this loop always wants present.
gates
Section F — the layered exits.
goals
Section C — named goals.
graph
The execution graph: nodes are units of work, edges are real dependencies.
guidelines
Section I — execution guidelines.
info
Section A — static context every node receives.
providers
Provider routing. Every provider is a command template.
skills
Sub-agent acquisition policy.
success
Section E — what counts as success.
triggers
Section G — time and event triggers.
validation
Section D — how each goal is checked.
work
Section B — the manual work that must happen before automation is allowed.

Structs§

LoopConfig

Constants§

OVERALL
Reserved target name meaning “the loop as a whole” rather than one goal.