What is execution-readiness?
Execution-readiness is a control gate rendered before money moves. It composes an intelligence check, a notional policy, and provider routing into one decision about how much human control an action needs, and records it to the Trust Ledger.
A gate, not advice
An execution-readiness verdict is a control, never a buy or sell recommendation. It answers whether a money-moving action is safe and authorized to execute, and who could execute it, not whether it is a good trade.
The decision states are ordered by block-severity: PROCEED (safe to execute now), READY (green but needs a human confirmation), WAIT (a fixable condition should clear), REVIEW (needs sign-off or dual control), NOT_READY (a prerequisite is unmet), and HIGH_RISK (a hard risk tripped).
Decide and orchestrate, never execute
LyraMind decides whether an action is ready and which connected providers could execute it. It never moves funds, custodies assets, or executes a trade. Execution stays pluggable: WireUp-class platforms, banks, and brokers register as providers and compete inside the platform.
The design is fail-safe. Any single blocking condition holds, and policy can only escalate a decision toward caution, never wave one through. The provider registry is explicit that every entry is an integration stub until a real provider is connected.
How LyraMind implements it
The decision composes the Agent Readiness gate for its intelligence basis, then applies a deterministic notional policy. Amounts at or above the dual-control minimum (default 10,000,000) force a two-person REVIEW; amounts above the auto-execute maximum (default 250,000) require a human confirmation; both thresholds are environment-overridable. Stale or sample data escalates to WAIT. Missing inputs degrade honestly to WAIT rather than guessing.
Every decision records verdict, evidence, and accountable actor to the Trust Ledger and returns a ledger_id, so the outcome can be reconciled later. That accountable record is exactly what lets the gate sit next to regulated flows without being a regulated entity.
Related concepts
Execution-readiness builds directly on the agent-readiness gate for its intelligence basis and on the Trust Ledger for its accountable record. Provider routing is the pluggable seam that keeps execution outside LyraMind.
- Six states by severity: PROCEED, READY, WAIT, REVIEW, NOT_READY, HIGH_RISK
- Composes the agent-readiness gate, a notional policy, and provider routing
- Fail-safe: any blocking condition holds; policy only escalates toward caution
- Notional thresholds (auto-execute max, dual-control min) are environment-overridable
- LyraMind decides and routes; it never moves funds or custodies assets
- Every decision records verdict, evidence, and actor to the Trust Ledger with a ledger_id
Questions
Does LyraMind execute the trade or payment?
No. It renders the go/no-go decision and routes to connected providers. It never moves funds, custodies assets, or executes a trade.
What happens if inputs are missing?
The decision degrades honestly to WAIT rather than guessing. For example, an unspecified amount or stale data escalates the state toward caution.
Can policy ever wave through a risky action?
No. The gate is fail-safe. Any single blocking condition holds, and the policy layer can only escalate a decision, never de-escalate it.