Getting Started with z4p
z4p is a Rust-native trading harness. It is designed so that powerful automation never means giving up control.
The philosophy
- Default posture: observe-only + dry-run.
- Every agent has a vault bible (Markdown): soul, instructions, memories, skills, loops, bot configs.
- Bots are scoped — they only see and do what their policy + wallet roles allow.
- Writes require explicit approval by default.
Core pieces
| Piece | What it is |
|---|---|
| Vault bible | Single source of truth for one agent |
| Tick engine | Drives the compose → retrieve → simulate → approve → execute loop |
| PermissionEngine | Enforces bot policies, allowances, halts |
| Gateway | Local HTTP + /vault UI + MCP endpoint |
| Loops | Reusable behavior (price_watcher, etc.) |
Your first 10 minutes
- Install + doctor
z4p gateway- Create a bot via CLI or UI
- Run dry-run ticks and read the output
- Decide what (if anything) deserves real keys and policies
z4p Mobile will surface approvals and portfolio context later.
For deeper details, read the architecture docs in the z4p repository.