Memories, claims & sources

Space is in development. These guides describe the current development version and the intended workflow. Public sign-ups and hosted agent connections are not available yet.

A claim is one statement the system remembers. A memory can hold several claims.

A claim is a saved statement

Your agent could save this as “The user prefers Python for scripting.” That sentence is one claim. “Claim” describes something recorded; it does not mean the system has proved it true.

A claim can express a preference, a project decision, or a fact. Keeping statements separate lets the system find or correct one without replacing everything else you saved.

A memory holds the claims

Imagine a note titled “My coding preferences.” It could hold two claims:

• The user prefers Python for scripting.
• The user prefers short explanations of code changes.

The memory is the container. Each claim is an individual statement inside it.

A source shows where a statement came from

If the Python preference came from a document, Space can link the claim to the saved version of that document. That version is called a revision. You can open it and check what the document actually said.

An agent can also save a claim directly. A directly saved claim does not necessarily have a source document. A source link gives you evidence to inspect; it does not prove the statement is correct.

“Current” means still kept in memory

If you change your preference to JavaScript, someone needs to update or remove the old claim. Space cannot know that your preference changed just because time passed.

A current claim is the version still kept in active memory. Whether it is still true in the world is a separate question.

Keep this picture: a memory holds statements, and a statement may point back to the source that supports it.