Docs

BaseHalf is built for compound thinking: work should not disappear into a single chat thread. A Map keeps the shape of the project visible. A Point gives one idea, file, decision, or task a durable page. References keep related context connected without forcing you to paste the same background into every prompt.

Use these docs as the product manual for that model. Start with the core objects, then move into workflows.

What to read first

• The BaseHalf product model explains Map, Point, Block, and Reference.
• Create your first Map shows how a broad request becomes a workspace.
• Move a chat thread into a Map shows how useful AI chat output becomes durable context.
• Choose an AI workspace explains when to use chat, documents, folders, or BaseHalf.
• Reuse context across questions explains why context should be portable.
• Study from a PDF turns a lecture, paper, or brief into a connected study system.
• Plan research shows how to keep sources, claims, and open questions separate.
• Manage a project with BaseHalf shows how a complex launch can preserve decisions, risks, workstreams, meeting notes, and weekly reviews.
• Product brief workflow turns a rough brief into decisions, risks, and next work.
• Run a review gives you a cadence for keeping a Map useful over time.
• Work with References shows when to connect Points instead of copying context.

The operating principle

Every useful piece of context should be reusable. You should be able to apply it independently, combine it freely with other context, and carry it into the next question without rebuilding the entire prompt.

That is the difference between a thread and a system.