Project shape before polish
See sources, decisions, risks, tasks, and drafts as separate objects before they become a finished document.
FeaturesMap workspace
A visual thinking interface.
BaseHalf gives each project a Map: a surface where ideas, files, decisions, and questions can be arranged as Points, opened as pages, and kept connected as the work evolves.
Mapwhere a line of thinking becomes visible.
Pointone idea, file, question, task, or decision you can open and keep building.
Blockeditable material written by you or AI.
Referencea context link between Points.
What it does
Designed for work that keeps changing
BaseHalf is not trying to make another static document. It gives AI work stable objects, visible boundaries, and enough structure to keep useful context alive.
Context you can inspect
The Map shows which pieces exist and how they relate, so AI work is not hidden inside one transcript.
Room for messy work
A useful Map can hold open questions, weak assumptions, and unfinished branches without pretending the work is done.
Reusable structure
Turn the shape of one project into a pattern for the next research plan, product brief, or launch review.
In practice
Example: one onboarding launch
A team is changing onboarding, pricing copy, analytics, support docs, and launch messaging at the same time. A Map keeps the project readable while each stream changes.
Create a charter Point
Preserve the launch goal, non-goals, owners, and deadline so every later decision has an anchor.
Split the workstreams
Create Points for product flow, engineering, data, support, docs, and go-to-market instead of one giant plan.
Promote decisions
When the team decides where plan selection belongs, turn the choice into a Decision Point and reference it from every affected stream.
Review the map weekly
Ask what changed, which risks are still active, and which Point should become the next action.
Best for
Use it when context has to survive the first answer
- Cross-functional projects with more context than a task list can hold.
- Research and product work where evidence, questions, and decisions change over time.
- Teams that need to preserve why something was decided, not only what the final answer said.