Society · Protocols
RealizationProtocol
Standard Interpret-Plan-Rollout workflow to ensure realizability
Definition
Mechanism
A standardized SolverTree that orchestrates one lifecycle run for a user_request executed by a PolymorphicSolver. It enforces a strict transition from Abstract to Concrete and evaluates feasibility before execution. 1. RequestFraming converts the request -> FrameSpec. 2. ManifestPlanning converts the spec -> ExecutionManifest. Before execution, Realizable judges the ExecutionManifest against the stated Budget, and its Value rating must pass the declared Criteria. 3. Rollout executes the ExecutionManifest -> RolloutManifest. After execution, the protocol reports the resulting real-world effects as the Outcome; the RolloutManifest remains the execution record rather than standing in for those effects.
Preconditions
Postconditions
- On successful completion, Outcome is reported separately from the frozen RolloutManifest.
- On a rejected seam or failed realizability criterion, this run halts before the next phase.
Invariants
- Typed Seams: RequestFraming yields FrameSpec, ManifestPlanning yields ExecutionManifest, and Rollout yields RolloutManifest.
- Realizability Admission: Before Rollout, Realizable judges the ExecutionManifest against the stated Budget, and its Value rating passes the declared Criteria.
- Non-Compensatory: A failed seam validation or realizability criterion halts this run; iteration requires a new run or an enclosing loop.
Risks
Failure modes
Bureaucracy
Blindly following all steps for trivial tasks.
Admission Rejection
A seam validation fails or the realizability rating does not pass Criteria, and this run halts before the next phase.
Manifest-as-Outcome
The RolloutManifest is reported as the realized Outcome even though it records actions rather than their real-world effects.
Relationships
Builds on
Composes with
Mind
Transform FrameSpec into ExecutionManifest via optimization
Mind
Evaluates execution feasibility of a plan
Mind
Clarify intent and constraints before planning
Progressive deployment with canary gating and recorded compensation
References
Infrastructure
Resource allocation limit
Infrastructure
Judgment standards
Infrastructure
Binding of Design and Procedure
Infrastructure
Structured problem definition artifact
Mind
Solver implementing the five-surface contract (polymorphic across substrates)
Infrastructure
Deployment execution log
Active hierarchy of coordinated solver instances
Yields
Infrastructure
Realized state after an action, captured for Plan-vs-reality comparison
Nothing in this library builds on this pattern yet.
Reference
Signature
SolverTree(Outcome)