Start with a local recall.
The developer quickstart walks through installation, a local fact, and retrieval without an LLM. It then adds a configured experiment and a Python wrapper around a retrieval callable.
The repository README describes the wider memory model and deployment options. Use a virtual environment, inspect optional dependencies, and validate the interface you intend to deploy.
Product READMEUnderstand what the evidence means.
Read the measurement wrapper for the callable contract: stable memory IDs, optional content revisions, a stable occasion ID, and outcome recording. Inspect the experiment and integrity modules when validating the design.
Keep a record of the assumptions behind any conclusion: task independence, outcome completeness, scoring consistency, randomized eligibility, and the chosen estimation mode.
Measurement wrapperReview promotion and rollback.
Change-control documentation describes immutable preregistration, canonical logged trial rows, support requirements, certification, and revocation. It also explains what an offline signature can and cannot establish.
Use these contracts to plan a change review. Do not substitute a favorable average, a simulated result, or a new policy configuration for the trial that the certificate actually covers.
Change-control documentationRead the isolation boundary.
Team isolation documentation explains point-read snapshots, stale-generation checks, work leases, reviewable merges, and exact limits. It is particularly useful before allowing multiple writers to share a store.
The local guarantees assume a common lock domain and declared dependencies. Distributed deployments need a coordination design appropriate to their own topology.
Team isolation documentationUse the assumptions as part of the API.
The guarantees document separates implemented behavior, reference adapters, deployment assumptions, and experimental claims. Treat this as required reading before a serious evaluation.
The website summarizes selected capabilities from a pinned source snapshot. The source repository remains the reference for precise configuration and evolving implementation details.
Guarantees and deployment assumptionsIntegrate against an explicit contract.
The gateway OpenAPI document describes local HTTP requests, responses, limits, authentication, and errors. The Hub has a separate OpenAPI contract and generated client libraries.
Use the contract belonging to the server you actually deploy. A local gateway example does not imply that the Hub supports every newer local allocation feature.
Gateway OpenAPIPut experience to work.
Try the local loop, or bring one workflow to a pilot conversation.
Technical details link to the inspected source. Check deployment requirements before enabling optional features.