planning_context
An overview, the requirements from spec and plan documents, and a decisions section drawn from transcripts and minutes — assembled for one implementation task.
Knowledge Briefs Experimental
Beyond chunk search — a structured model of the project.
Raw retrieval returns similar-looking paragraphs. A ContextHarbor project can also hold a hierarchical knowledge tree — domains, then modules — with consolidated briefs an agent can read top-down before it ever touches a chunk.
One question, structured answer
What do we need to know before changing the Atlas billing workflow?
Return the area brief, not forty paragraphs.
ContextHarbor answers with the consolidated billing brief — rules, constraints, dependencies, and open decisions — each line traceable to the document it came from.
Agent-facing tools
Structured retrieval when a project has a knowledge tree.
ToolWhat it returns
get_project_structureThe hierarchical knowledge-area tree for a project.
get_area_briefA consolidated brief for one area at summary, standard, or full
depth.
get_knowledge_itemOne consolidated knowledge item with its provenance.
search_areaSearch consolidated knowledge within an area and, optionally, its
descendants.
get_project_briefThe hierarchy when present; falls back to top chunks when it is
not.
Built for how agents plan work
Planning context routes to the right kind of document.
requirement_lookup
Look up a single requirement, spec and plan documents first, with the historical decision and related requirements attached.
Provenance kept
Every consolidated line carries the source it was derived from, so a reviewer can check the brief against the original document.
Where this stands
Experimental, and improving with each project it runs on.
Working todayKnowledge-tree storage, area and project briefs with provenance,
and
planning_context / requirement_lookup
over MCP.
Coming nextBroader automatic consolidation, better handling of conflicting
sources, and richer cross-area linking.
Fallback is always safeWhere no tree exists, the same tools return source-backed chunk
results, so agents never get an empty answer.
Knowledge Briefs
Give agents the project's shape, not just its paragraphs.
Start with one project where developers keep reconstructing the same background.
Pricing depends on deployment, integration, and support requirements.