Using the app

uncapped is one integrated system with four views over the same work. Nothing you do in one view is invisible to the others — a journal line can become a task, land on a venture board, surface in your weekly review, and end up executed by crew, all as one connected thread.

Logbook — capture #

The input wedge. Write what's actually happening — plans, calls, decisions, worries — in plain language. Your journal is private to you, always: entries never leave your account, are never shared with teammates or clients, and are structurally unreachable by any connected AI channel.

• Focus mode expands the capture box into a full-screen, distraction-free writer.
• Today shows the day as two columns: what you wrote, and what came out of it.
• AI extraction runs on every entry and proposes tasks — which brings us to the one habit that makes uncapped work:

Confirm, don't enter. You rarely create tasks by hand. You write honestly, then confirm (or dismiss) what the AI extracted. Confirmed items become real work on the graph; dismissed ones teach the system.

More on why the journal works this way: the journal.

Ventures — the boards #

Each venture (a business, a client, a big project) gets a board of confirmed work, a goal, and phase-gate reviews. Because tasks arrive from the journal with their origin attached, the board carries why something exists, not just what it is. Details: work and boards.

Command center — the review loop #

The operator view: what's waiting on you, what changed per venture this week, the weekly review, and the decision ledger. When you have ten minutes, this is the tab that tells you where they go.

Crew — the AI workers #

Deploy queued work to AI crew roles and review what comes back. Crew has its own section of these docs: how crew works.

Portals — what clients see #

Each client can get a portal at their own address with visibility tiers — you decide, per item, what's client-visible. Drafts and internal work stay internal by default.

The principle underneath #

Every state-changing action in uncapped is reversible or pausable: unconfirm a task, revert a phase, pause a crew run mid-flight. That's deliberate — a system you trust with your real operations has to be a system you can always walk back.

This section grows doc-by-doc as questions come in. Missing something? Say so in your onboarding session — the gap becomes the next page.