Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.waycore.com/llms.txt

Use this file to discover all available pages before exploring further.

The Action Bar is a thin execution surface built on top of the broader Waycore platform. It allows users to express complex financial intent in natural language or structured commands, which are then translated into deterministic platform actions today and explicit API calls once the public Transfer API is released. All actions executed through the Action Bar use the same policy engine, state machine, and audit system as Waycore’s underlying execution model. The public execution and transfer endpoints described on this page will become available once the Transfer API is released.

​
Why It Exists

Once connectivity is in place and execution APIs 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.
The Action Bar provides a structured way to express these higher-order operations.

​
What It Does

The Action Bar:
  1. Parses user intent.
  2. Validates it against account topology and permissions.
  3. Simulates the execution plan.
  4. Evaluates policies.
  5. Generates one or more execution objects.
  6. 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. The action bar also supports complex actions like multi-line spreadsheets with payment instructions and invoices, and turns them to executable objects. The agent then goes ahead and executes at the portal level.

​
Execution Model

Every Action Bar request results in:
  • A generated execution plan
  • Policy evaluation results
  • One or more execution IDs
  • A traceable audit record
State transitions mirror the transfer lifecycle that will be exposed through the public API once the Transfer API is released:
  • CREATED
  • POLICY_VALIDATED
  • QUEUED
  • EXECUTING
  • COMPLETED / FAILED
The Action Bar does not introduce a separate execution system. It is an intent translation layer.

​
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.
All intent resolution occurs within the boundaries of:
  • 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

​
It is optional. Today, treat it as a platform capability; the equivalent public execution APIs will be available once the Transfer API is released.

​
Design Principle

Connectivity enables execution. Execution enables orchestration. The Action Bar exists to compress multi-step financial workflows into explicit, policy-bound intent.