Notes and history

Original submissions stay available. Changes have a history. You choose which notes agents can read.

Organize projects

Create a project with its name, an optional description and a group in Projects. Search project names and descriptions or filter by group to find the right knowledge. A group organizes your workspace; it does not grant access or merge projects.

Open a project to add notes, inspect its assigned standards or use Connect an agent. That action opens a setup brief with the existing project ID selected. Another agent needs its own authorization, not a duplicate project.

Read the current project

The Notes view shows newest submissions first. Add a note, filter by status and load older entries when needed. Copy active notes copies the active content currently loaded in the view, regardless of the current status filter. When active standards are assigned, Copy agent context includes their full current contents and versions before the loaded active notes. Load older entries to include older notes too. Copying a loaded page is not a complete project export.

Agent context shows active assigned standards and the current active notes loaded in this view. It can be copied even when a project contains standards but no active notes. If clipboard access is blocked, Memford selects that text so you can copy it manually. An empty active selection explains why there is nothing to copy; older active notes may need loading. Open a note’s Version history for its original submission and later revisions.

Agent reads return active current notes through MCP. Follow next_cursor when you need older pages. Inactive and deleted notes are excluded from these active reads.

Share standards across projects

Open Standards for reusable rulebooks and business defaults. Existing projects need explicit assignment; optional defaults apply when new projects are created. Assigned active standards arrive alongside notes on every MCP page, without rewriting the original notes. The shared standards guide covers assignment, revision history, archive and limits.

Edit without losing the original

Project owners can edit, deactivate, reactivate, delete and restore notes. Those changes create revisions while preserving the original submission. A note can contain up to 32,000 characters.

• Deactivate keeps a note in the project but excludes it from active reads.
• Delete a note archives it. It can be restored from the project.
• Delete a project permanently erases its original notes, all their revisions and project access. It also removes the project’s standard assignments; account standards remain available to other projects. This is different from archiving a note.

Concurrent edits check the expected revision. If another edit has already changed the note, refresh and review the current text before trying again.

Open Version history beneath a note to expand the original and each retained edit or status change, with its revision, receipt time and recorded account. Load older revisions when indicated. Selecting an old version does not restore it automatically.

Follow the timeline

History is a dated timeline of original submissions. Choose Jump to a submission or a timeline point to see the originals received up to that contribution and what was added afterward. Load older notes for the complete submission timeline.

Those are the exact original texts, even when they have since been edited, deactivated or deleted. This view does not reconstruct the active project state at that date. For later edits and status changes, use the individual note’s Version history in Notes. History is read-only; selecting a point does not roll back memory or reset a running agent’s context. A submission timeline point is also separate from a terminal recovery checkpoint.

New contributions record the authenticated connection and account with their receipt time. A source label is supplied by the writer and is separate from that authenticated provenance. Older notes may have unknown origin. Client attribution does not prove a physical computer or who made a decision; the recorded account identifies who saved it. Give each computer a separate connection to distinguish its submissions.

Keep connected clients current

Clients that support MCP resource subscriptions can receive a change hint and fetch the updated notes. Clients without subscriptions read the latest available notes on their next fetch.

Receiving a notification does not prove that an agent has used the new information in its current conversation. That behavior depends on the client.

See the subscription and reconnect contract for custom clients.

AI-derived context

AI consolidation is under quality evaluation. Candidate summaries are separate from the original notes; automatic creation, owner approval of a main version and delivery of that approved version are not yet available as a complete customer flow.

Active agent reads currently return the active notes. They do not silently replace those notes with an AI summary.