Quickstart

Your first memory, with a source.

A small, private namespace is enough to begin. Use a disposable example before importing anything sensitive.

1. Sign in and select a workspace

Open the workspace and sign in with an email code. If a workspace admin sent you an invitation link, open it and accept to join. An enrolled pilot identity can create a workspace; members pick theirs from the workspace switcher. Signing in alone does not add you to a workspace or enroll you.

2. Create a namespace

Open Namespaces and create one such as Project notes. Find any namespace later by name or ID, or paste its address. To bring in a colleague, create an invitation link from Members & settings, then give them only the capabilities they need from the namespace’s Access view. Ordinary agents should usually receive read and observe; verification, correction, deletion and administration are separate capabilities.

3. Record evidence and a candidate

Add a source locator and the exact supporting excerpt. Save the observation as a candidate and choose when it began to apply. Verification requires exact-text attestation and supporting evidence. Automatic maintenance can verify supported claims when original-author admission establishes their source authority.

4. Read it back

Open the saved memory directly to inspect its source and time intervals. Recall may report pending indexing after a write. When recall is pending, choose “Search without waiting for indexing” to request bounded retrieval without the saved-write indexing guarantee. If hybrid search is unavailable, retrieval uses a lexical slice. Keep its degraded or partial status; these results do not prove that no matching memory exists.

5. Try a historical view

Set both time controls in the workspace. After an authorized correction, compare the earlier known-at cutoff with the current one while holding as-of fixed. The temporal guide includes the exact Boston/New York fixture.

6. Connect code or an agent

Use REST for application calls or the MCP resource for a compatible client. Generate requests from the published catalog rather than guessing payloads. Every mutation needs an Idempotency-Key. Tokens are credentials, not permission to choose an arbitrary workspace.