Mind · Strategy
PolymorphicSolver
Solver implementing the five-surface contract (polymorphic across substrates)
Definition
Mechanism
A PolymorphicSolver is any entity — from a fleeting thought process to a complex swarm — that implements the five-surface contract Solver specifies (Manifest via Card, Execute, Consult, Verify via Validate, Feedback — emits a typed PerformanceSignal). Manifest and Execute are mandatory; Consult/Verify/Feedback are optional but strongly recommended at hard seams. The pattern is named for its polymorphism: any substrate conforming to the contract qualifies — LLM, human, hybrid, tool-using agent, nested composition, or mechanical dispatcher — not just cognitive ones. It acts as a fractal node in the UniversalSolverTree, accepting a Task and using Reason to orchestrate a lifecycle on a SolverNode. It yields a Solution, wrapping operations like ToolInvoke with ComputeBudget checks, SocraticLoop refinement, or Reflexion for self-improvement. When operating as a dispatcher (routing sub-tasks to child solvers), it maintains a local PathwayMemory so routing decisions compound as experience accumulates — the property that gives the fractal structure its learning dynamics.
Invariants
- Polymorphism: External Runtime treats all Solvers identically via this Interface.
- Recursion: Solver must accept sub-tasks via the same Interface it exposes.
Risks
Failure modes
Interface Non-Compliance
Solver omits Manifest or Execute, or advertises an optional Consult, Verify, or Feedback surface it cannot provide.
Manifest Drift
Capabilities declared in Manifest do not match runtime behavior.
Relationships
Builds on
Accepts
Infrastructure
The atomic unit of intent
Composes with
Economic governor for cognitive spend
Learned routing memory: problem_class → route → outcome_quality
Execute a cognitive topology
Self-critique and retry after failure
Clarification before generation
Infrastructure
Execute external tool and observe result
References
Infrastructure
Structured capability advertisement: agent_id, endpoint, protocols, capabilities, metadata
Infrastructure
Typed artifact emitted by a Solver's Feedback surface — downstream evaluation that feeds Pathway Memory
Abstract five-surface contract: Manifest, Execute, Consult, Verify, Feedback
Society
Stateful container for a running solver instance
Society
Collective knowledge graph of all problem-solving
Infrastructure
Verifying inputs conform to expected schema
Yields
Infrastructure
The fractal unit of completed work
Used by
Composes with
Expansion of cognitive capability through recursive decomposition of concepts into contract-bounded sub-concepts
Deeply optimizing a solution across PURE dimensions
Extends
Society
High-velocity solver requiring parallel runtime
High-reliability, high-latency System 2 solver
References
Society
High-velocity solver requiring parallel runtime
Society
Standard Interpret-Plan-Rollout workflow to ensure realizability
High-reliability, high-latency System 2 solver
Reference
Signature
Solver(Task)