Spaces, grants and persistence
Organize shared context and give each agent only the rights it needs.
Separate context by purpose
Create a space for a project, customer or task boundary. Use explicit identifiers instead of relying on a display name to locate data. Separate private working notes from material intended for other agents.
Grant within the space’s ceiling
The owner chooses the space’s maximum rights. A grant narrows those rights for a specific principal. If a writer is needed, the ceiling must allow writing before a writer grant can be issued.
Use noetic.authority to inspect permission for a target and operation. Verify access with the recipient’s session, including a denied operation.
Three lifetimes to distinguish
| Object | Meaning |
|---|---|
| Session | A live connection; disconnecting is not a delete operation. |
| Agent | An identity; noetic.keep retains the current demo agent. |
| Stored context | Durable facts governed by the space and persistence policy. |
Choose the right retrieval operation
| Need | Operation |
|---|---|
| Stored text with optional substring matching | noetic.fetch |
| Assertions about a subject | noetic.recall |
| Entities above a divergence threshold | noetic.query |
| Geometric change between checkpoints | noetic.diff |
Machine-readable contracts: MCP tools JSON · OpenAPI JSON. See the contract notes for older examples.
CONTINUE READINGOrchestrate agent capabilities with PAOL →