Society · Protocols
OrchestrationLoop
Interpret-Plan-Rollout Lifecycle
Definition
Mechanism
A strict lifecycle for high-stakes problem solving implementing Workflow. It enforces a sequence: 1. RequestFraming (Frame Problem → FrameSpec), 2. ManifestPlanning (Architect Solution → ExecutionManifest), 3. Rollout (Execute safely → RolloutManifest). Each transition is mediated by a typed artifact that must pass a non-compensatory AcceptSpec. The loop can iterate: failed rollouts trigger re-planning, failed plans trigger re-interpretation. At seams that cross trust boundaries (cross-organizational or commons-facing), feedback returning through each stage passes through a ReceptivityGate that validates any FailureTrace before the upstream stage absorbs the rejection.
Invariants
- Artifact Mediation: All phase transitions MUST pass through typed artifacts.
- Non-Compensatory Gates: Each AcceptSpec is binary pass/fail.
- Bounded Iteration: Within one run, the loop MUST NOT re-enter an earlier phase more than `iteration_limit` times; the next failed gate escalates.
Risks
Failure modes
Bureaucracy
Blindly following the full lifecycle for trivial tasks (using a cannon for a mosquito).
Loop Stalling
Getting stuck in Plan/Rollout cycles without shipping.
Artifact Rejection Cascade
Overly strict AcceptSpecs repeatedly send work to earlier phases until `iteration_limit` is exhausted.
Seam Leakage
Untyped data bypasses the artifact boundaries.
Relationships
Builds on
Composes with
Mind
Transform FrameSpec into ExecutionManifest via optimization
Mind
Clarify intent and constraints before planning
Progressive deployment with canary gating and recorded compensation
References
Infrastructure
Non-compensatory acceptance contract; consumer Verify yields Solution or FrameError
Infrastructure
Binding of Design and Procedure
Infrastructure
Structured problem definition artifact
Verification gate for signed, clause-specific rejection records
Infrastructure
Deployment execution log
Directed graph of operations
Nothing in this library builds on this pattern yet.
Reference
Parameters
iteration_limitPositiveInteger, unspecified- Maximum number of failed-gate re-entries within one run before escalation
Signature
Workflow(Rollout)