The Action Bar is a thin execution surface built on top of the Waycore API. It allows users to express complex financial intent in natural language or structured commands, which are then translated into deterministic API calls. All actions executed through the Action Bar use the same policy engine, state machine, and audit system as direct API calls.
Why It Exists
Once connectivity and execution are available, the next constraint is orchestration. Most financial workflows are not single API calls. They are sequences:- Move excess cash from operating accounts to treasury.
- Sweep balances across entities.
- Fund payroll across multiple institutions.
- Rebalance accounts to target thresholds.
- Execute multi-leg transfers conditioned on approvals.
What It Does
The Action Bar:- Parses user intent.
- Validates it against account topology and permissions.
- Simulates the execution plan.
- Evaluates policies.
- Generates one or more execution objects.
- Submits them to the Waycore execution engine.
Example Intents
“Move all balances above $250,000 from entity A operating accounts into the master treasury account.” “Fund payroll accounts with exactly 14 days of burn.” “Rebalance all accounts to maintain a minimum liquidity buffer of $100,000.” Each of these expands into a deterministic execution plan.Execution Model
Every Action Bar request results in:- A generated execution plan
- Policy evaluation results
- One or more execution IDs
- A traceable audit record
- CREATED
- POLICY_VALIDATED
- QUEUED
- EXECUTING
- COMPLETED / FAILED
Guardrails
The Action Bar:- Cannot override bank permissions.
- Cannot override policy rules.
- Cannot execute without explicit confirmation (if required).
- Cannot access institutions not already connected.
- Delegated user permissions
- Configured policies
- Institution capabilities
Developer Perspective
For platforms embedding Waycore, the Action Bar can be:- Exposed to end users
- Used internally as an operations console
- Disabled entirely