Jackfa/Overview
Preview · in development Account not linked Connect account
WORKSPACE / 00 / OVERVIEW

The planning desk.

Every plan, its conditions, and the record it leaves behind.

Draft a plan
Working plans00 Saved in this browser
Planned allocation$0 Draft amounts, not funds at work
Live positions— Account not linked
Realized outcome— Shown after verified fills
01 / YOUR NEXT PLAN
A HUNCH IS A START. A RULE IS A PROMISE.

Make room
for a plan.

Start with what you see in the market. Write what has to happen, what you’ll do, and exactly where you’re wrong.

Start drafting
WORKSPACE READINESS
01/ 04

Ready to draft.

Write the rules first.
Set your limits. Link your accounts.

  1. Planning desk ready
  2. 02Save your first plan
  3. 03Link your accounts
  4. 04Lock your first plan
Manage your accounts

From hunch to record.

The whole plan lifecycle, kept as one continuous record.

How it works
01Draft Write the rules
02Review Check and test
03Lock Timestamp the plan
04Watch Wait for conditions
05Act Order or alert
06Record Reveal the result
START WITH DRAFT + REVIEW

Check the rules before anything is signed. Every stage keeps the plan exactly as it was written.

02 / YOUR WORKING PLANSOpen journal

Every record starts with a rule.

Draft a setup, check its conditions, and save your first plan.

Draft your first plan
03 / RISK ENVELOPE
$500Maximum per plan
3× Leverage ceiling
$100 Daily loss limit

These limits apply to your drafts. Account-level limits also need a linked trading permission.

Set your limits
04 / TWO CONNECTIONS
PX

Perp exchange

Crypto perpetuals and spot pairs. Price, funding and open-interest feeds. Trade-only permission, no withdrawals.

Not connected
LR

Lock registry

Plan locks, hourly roots and your record. Every lock is timestamped and signed by you.

Not connected
Explore accounts & routes
05 / RECENT ACTIVITY
THE RECORD IS QUIET.

Saved plans and limit changes show up here. This is your workspace history, kept in this browser and separate from plan locks.

Open activity log

Every step has a reason.

Explore lock timing, follower batches, data checks, and permission limits.

Inside the architecture