Society · Protocols
OptimisticSolver
High-velocity solver requiring parallel runtime
Definition
Mechanism
A high-velocity implementation of PolymorphicSolver designed for efficient multi-agent coordination. Requires a Parallel runtime (Actor Model with Mailboxes) to prevent serial deadlock. It explicitly couples the standard Solver lifecycle (Reason -> Solution) with the AtomicBid protocol. Unlike the base abstraction, this pattern MANDATES that the agent plan and execute in a single turn. It relies on Reflexion and Compensate for error correction rather than pre-action permission. Use ComputeBudget to bound resource consumption. Contrast with RigorousSolver which prioritizes safety over speed. A PathwayMemory accumulates across runs so the optimistic route-selection converges on strategies that historically succeeded under similar conditions.
Preconditions
- Runtime supports Asynchronous/Parallel message delivery (Actor Model).
- Message Bus is non-blocking (Mailbox pattern).
Invariants
- Turn Atomicity: Must output [BID] and [TOOL] in the same response.
- Non-Blocking: Cannot wait for Orchestrator approval on standard tasks.
Risks
Failure modes
Over-Eager Execution
Solving the wrong problem efficiently because feedback was skipped.
Serial Deadlock
If deployed on a single-threaded (Talking Stick) engine, multiple atomic outputs will be dropped, halting the swarm.
Caution
Executes without pre-action verification. Ensure irreversible actions have compensation or sandboxing, or use RigorousSolver at those boundaries.
Relationships
Builds on
Composes with
Declaration and execution in a single turn
Infrastructure
Structured rollback via logged inverses in LIFO order
Mind
Economic governor for cognitive spend
Mind
Learned routing memory: problem_class → route → outcome_quality
Mind
Self-critique and retry after failure
References
Infrastructure
Concurrent flow
Mind
Solver implementing the five-surface contract (polymorphic across substrates)
Mind
High-reliability, high-latency System 2 solver
Extends
Mind
Solver implementing the five-surface contract (polymorphic across substrates)
Nothing in this library builds on this pattern yet.
