Mind · Strategy
MetaProtocols
Solvers that operate on the solver tree itself — monitoring topology, detecting redundancy and drift, arbitrating across decomposition paths
Definition
Mechanism
Protocols that operate on the solver tree rather than within it — decomposing self-regulation: monitoring whether the tree remains the right shape for the problems it faces. A MetaObserverSolver maintains an approximate gestalt of tree topology and performance dynamics (redundant computation, decompositions that have outlived usefulness, PathwayMemory that has drifted). Representative meta solvers: TopologyAuditorSolver (detects subtrees generating more rework than value, emits a ReframeSignal via Reframe), RedundancyDetectorSolver (merges isomorphic sub-problems being solved independently), DriftMonitorSolver (flags when pathway memory has drifted from current problem distributions), OutcomeArbiterSolver (compares solution quality across structurally different decomposition paths, blind to the path that produced each result). Meta Protocols are themselves Solvers governed by the same contract; they do not solve object-level problems, they ensure the problem-solving topology remains adapted.
Invariants
- Tree-level scope: Meta Protocols observe and act on topology and performance of other Solvers, not on object-level Tasks.
- Contract-invariant: Meta Solvers are themselves Solvers (Manifest + Execute); their depth of meta-observation is governed by MarginalValueRule.
- Blind arbitration: OutcomeArbiter evaluates final artifacts against the original Task without access to intermediate structure — blindness is what lets it compare across decomposition paths without structural-familiarity bias.
Risks
Failure modes
None stated.
Relationships
Builds on
Composes with
Deepen only while expected improvement plus an exploration credit, divided by incremental cost, exceeds a domain threshold
References
Learned routing memory: problem_class → route → outcome_quality
Changing perspective to restructure the tree and find a new solution root
Nothing in this library builds on this pattern yet.
Reference