Command intelligence
Ghost Brain intent compiler
Ghost Brain converts natural-language crypto requests into a typed plan before any execution provider is called. The model can help understand language, but only schema-validated actions can reach an execution engine.
Compilation flow
User message to intent understanding to entity resolution to transaction plan to validation to the existing execution engine to a result summary.
Plans support up to five ordered actions. Each action records its chain, assets, amount basis, recipient, dependencies, runtime checks, confidence components, and current state.
Natural command support
Ghost Brain recognizes common bridge, swap, sell, transfer, claim, token launch, and limit-order language, including shorthand such as .1e, chain aliases such as hood, common typos, crypto slang, and mixed Bengali-English commands.
bridge .1e from base to hood,
swap 40% to USDC,
swap 30% to DAI,
send 20% to 0x...,
leave the restAmounts and dependencies
Percentages are attached to a specific source: wallet balance, bridged amount received, sale proceeds, purchased amount, claimable rewards, or the remaining allocation. A dependent action uses the measured onchain output of its prerequisite, not an estimated or fabricated amount.
Allocations above 100% are rejected before execution. Native assets retain a gas reserve where required.
Clarification and memory
When a token, chain, amount, or recipient is materially ambiguous, Ghost asks one targeted question and keeps the pending plan. A short answer fills that plan. Asking what or explain shows the saved state instead of discarding it.
Execution and recovery
Bridge-first Ghost Wallet plans can feed measured receipts into multiple swaps and transfers. One confirmation starts the managed workflow. Confirmed steps are never replayed automatically, and a failed step can only be retried when no transaction hash was already broadcast.
Plans containing a step without a compatible live executor remain in review. Ghost OS clearly states that no transaction was sent.
Safety boundary
Compilation is not execution. Wallet readiness, balances, gas, routes, liquidity, token risk, allowance, slippage, price impact, policy, signatures, receipts, and explorer proof are validated by the existing server-owned execution stack. Ghost OS never invents balances, fills, or transaction hashes.

