BaseHalfUse cases

Where compound thinking becomes useful.

BaseHalf works best when the task has sources, decisions, risks, drafts, and follow-up questions that need to survive longer than one response. These use cases show how to turn real work into reusable context.

Choose a workflow

Start from the shape of the work

Each workflow starts with a prompt, but the goal is not a better prompt. The goal is a Map that keeps useful context visible, editable, and ready for the next question.

Example

A complex project needs more than a task list

A launch project may include research, product decisions, engineering work, analytics, support, docs, and stakeholder updates. BaseHalf keeps the reasoning behind those tasks visible so the next person can continue from the current state.

01

Preserve the charter

Keep the goal, non-goals, constraints, owners, and deadline in one anchor Point.

02

Separate workstreams

Give product, engineering, data, support, docs, and launch communication their own Points.

03

Connect decisions and risks

Reference the context that should shape weekly updates, tasks, and stakeholder reviews.