Bots & Engines — a system that behaves.
YieldCraft wasn’t built to “trade more.” It was built to trade with control — explicit rules, clear gates, and a layered architecture where intelligence informs strategy, strategy guides execution, and risk governs everything.
The why
Most people don’t need more signals. They need a system that won’t betray them under pressure.
YieldCraft is designed for repeatability. That means fewer moving parts, clear boundaries, and decision logic that can explain itself. When the right move is to do nothing, the system can do that — on purpose.
Explicit rules
If a rule isn’t explicit, it doesn’t exist. This keeps behavior stable and debuggable.
Gated execution
Trading is gated behind switches, safety conditions, and defined failure states.
Layered architecture
Intelligence cannot place orders. Execution cannot invent signals. Risk can override both.
Deliberate rollout
New engines ship behind flags — stability stays protected while capability expands.
Core engines
Enough detail to trust it — not enough to copy it.
These descriptions focus on behavior, constraints, and intent. The edge is in the orchestration, risk posture, and continuous iteration — not a single “secret indicator.”
Pulse
Execution Engine — precision over prediction.
What it does
- Places orders only when all gates are satisfied.
- Enforces sizing rules and cooldown behavior to prevent churn.
- Logs decisions so you can see “why it did nothing.”
How it behaves
- Deterministic and boring by design — consistency beats adrenaline.
- Separates decision inputs from execution actions.
- Respects global kill-switches and safety conditions.
Why it matters
- Execution quality is where most systems fail (slippage, over-trading, randomness).
- A stable execution layer is required before adding complexity.
- When signals are wrong, good gates reduce damage.
Note
Pulse is built to execute a plan safely — it does not promise performance.
Recon
Market Intelligence — context, not commands.
What it does
- Measures regime + conditions (trend, momentum decay, volatility context).
- Outputs confidence/context signals rather than orders.
- Supports “do nothing” decisions when conditions are unfavorable.
How it behaves
- Never touches execution directly — separation is intentional.
- Designed to be composable: multiple signals can be blended later.
- Can be upgraded without risking the execution engine.
Why it matters
- Most traders lose by misreading regime shifts and forcing trades.
- Context improves selectivity — fewer, higher-quality decisions.
- A clean signal interface allows safe iteration and testing.
Atlas
Long-Horizon Strategy — time as an edge.
What it does
- Runs on a longer horizon than Pulse.
- Focuses on allocation logic, thesis rules, and slower signals.
- Designed to operate independently as a stand-alone mode.
How it behaves
- Low frequency by design — discipline over constant interaction.
- Treats risk limits as first-class inputs.
- Can coordinate with Pulse/Recon without coupling.
Why it matters
- Many edges exist on longer horizons where noise is lower.
- Portfolio-minded logic reduces impulsive switching.
- Separating time horizons prevents mixed, conflicting behavior.
Advanced engines
Built to scale — without breaking what’s live.
Additional engines ship behind flags and stability checks. The promise is not speed — it’s controlled expansion.
Horizon
Regime + volatility awareness that helps Recon decide when signals should be discounted.
Ignition
Entry timing filters designed to avoid “late” participation and low-quality chase behavior.
Ascend
Allocation + risk budgeting logic aimed at scaling size only when conditions justify it.
Forge / Edge
Experimental engines that must prove stability in controlled rollout before touching production behavior.
Disclosures
YieldCraft provides software tools for structured workflows. It does not provide investment advice. Trading involves risk, including possible loss of capital. No guarantees of performance are made.