From install to production.
Concrete, copy-pasteable paths for each way teams adopt Heartwood — the same flows we run against the trust suite, with generic example tenants.
Import a Markdown memory corpus
Build a derived Heartwood store from a folder of Markdown memory files while keeping Markdown as the human-readable source of truth.
RecallLow-latency warm recall
Run a local recall service that keeps the store, vector index, embedder, and reranker warm — so hook- and agent-loop calls stay under the 500ms budget.
MCPGoverned MCP memory server
Wire Heartwood into any MCP client for governed writes and agent-facing memory tools — remember, recall, explain_recall, forget, egress, and faithfulness checks.
APITenant-aware bulk writes & recall
Bulk-write and recall per tenant from the public Python API without hand-constructing Policy and Principal objects at every call site.
OnboardingEnd-to-end onboarding
The full adoption path: install, build a derived store, run warm recall, enable MCP, configure key custody, and validate before a cutover.