Explicit dependencies
Connect a claim to a source, a task to a decision, or a draft to the evidence that should constrain it.
FeaturesConnected context
Keep the trail between related ideas.
References let work travel between Points. Instead of asking AI from a blank prompt each time, BaseHalf keeps the surrounding decisions, files, and reasoning paths available.
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.
Reusable context packets
Select the Points that matter for the next request instead of pasting the same background into every prompt.
Revision without amnesia
When one assumption changes, you can see which decisions, drafts, and tasks may need another pass.
Context with boundaries
A Reference preserves relationship without merging everything into one large document.
In practice
Example: project risks tied to decisions
During a launch, a billing integration risk depends on a product decision and an unstable API contract. Connected context keeps that relationship visible.
Reference the product decision
Connect the risk Point to the decision about in-flow plan selection.
Attach the source of uncertainty
Connect the risk to the API contract notes and the engineering workstream.
Draft with the right context
Ask for a weekly status update using the risk, decision, and workstream Points together.
Revise only what changed
If the API stabilizes, update the risk Point and review the connected launch plan.
Best for
Use it when context has to survive the first answer
- Work where one decision affects several drafts, tasks, or teams.
- Research that needs source-backed claims and visible uncertainty.
- Complex projects where stale assumptions should be easy to find.