One durable object
A Point can hold one question, decision, source, task, file, or draft without mixing it into the whole project.
FeaturesPoint pages
Open one thought without losing the whole map.
A Point is where a question, task, file, or decision becomes durable work. You can write with AI inside it, keep useful Blocks, and return to the surrounding Map whenever the context matters.
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.
Editable AI output
Keep useful AI output as Blocks that can be revised, deleted, split, or reused later.
Local depth
Work deeply on one idea while the Map preserves where that idea belongs.
Clear ownership
A teammate can open a Point and understand what it is for, what it depends on, and what should happen next.
In practice
Example: a decision that needs history
A product team needs to decide whether plan selection belongs inside onboarding or in billing settings. The decision cannot live as a single chat answer because several streams depend on it.
Open the decision Point
Write the decision, alternatives, reason for the current choice, and condition that would reopen it.
Attach the evidence
Reference support notes, activation data, customer interviews, and engineering constraints.
Keep the draft close
Store the stakeholder summary and launch note as Blocks inside the same Point.
Reuse it later
Bring this Point into implementation planning, support docs, and the post-launch review without copying a thread.
Best for
Use it when context has to survive the first answer
- Decisions that need alternatives, evidence, and revisit conditions.
- Drafts that should stay connected to their source context.
- Tasks that need enough background for someone else to resume them.