Memco Shared Memory

Add information to an existing memory in Memco Shared Memory, so your finding lands beside the one it belongs to rather than in a memory that competes with it. Call when: a search returned a memory close to what you learned but incomplete, out of date, or missing the approach you took. Use create_memory instead when nothing returned covers the subject at all. Set memory_idx to the memory you want to extend (from search results), or 'new' to add a standalone addition. Keep an addition concise and say only what is not already there. The addition lands in the domain the search session ran in; you do not name one.

enrich_memory

Fetch one memory a search returned, by its idx, and get it back in full. Call when: you hold an idx whose content is not in front of you — a search returned the memory as a reference to an idx that carried it earlier, or another agent did the searching and passed you the handle. An insight's idx returns the memory holding it. The idx is all it takes: copy it exactly as it appeared in a search response — it cannot be constructed by hand — and nothing else is needed to name the result. When a result shows a ref instead of content, ask by the value in its own idx, never the value in its ref. A result rendered as <memory idx="memory-THIS-1" ref="memory-EARLIER-1"> is fetched with "memory-THIS-1": the ref says where the content was delivered, not what to ask for. Both return the same text, but only its own idx keeps a later rating with the search you are working in.

get_memory

Fill a new or nearly empty workspace with the knowledge a team already holds, in one call, so memory starts out useful instead of empty. Call when: filling a workspace that has little or nothing in it, or onboarding someone into one — a teammate joining, or your own first connection to it. This is a setup step, done once: you are handing over what is already known, not recording something you just learned. Use create_memory for a single finding from this session. Pass either a domain or a session_id — a call naming neither is refused. Each memory needs at least one query describing what someone would search to find it, and at least one insight with a title and content. At most 25 memories per call, 20 queries and 10 insights each; send several calls for more. Every memory is checked on the way in and starts at your own standing, exactly as a single write does. The response answers per memory, by the position you sent it in: one that was refused says why, and one whose content is already held says so and is not written again.

import_memories

List the memory domains available to you and describe each one: what it holds, when to search it, what belongs in it and what does not, and the tag vocabulary and format it uses. Call when: before your first search or write of a task, and whenever you are unsure which domain a question or a finding belongs to. The slug you choose is what start_session, search and create_memory take as their domain argument.

list_domains

Rate the relevance and correctness of search results. Only you can tell whether a result was useful in answering the query, and these ratings shape which results are shown next. Call when: you have read the results of a search and can judge them — once per search, while its session id is still to hand. The feedback is recorded against the domain the search session ran in; you do not name one.

share_feedback

Save new knowledge to Memco Shared Memory, where your teammates and their agents will find it. Call when: you have learned something non-obvious that would help your team — why something turned out the way it did, how something actually behaves, something that was hard to establish, or a decision and its rationale — or your user has corrected you. Search first: when a related memory already exists, enrich_memory extends it instead of leaving a near-duplicate beside it. Pass either a domain or a session_id — a call naming neither is refused. Naming the session you have been searching in saves the memory into that session's domain and records it as part of that work; naming a domain alone saves a standalone memory. Each memory needs a query (what someone would search to find this), a title, and content describing what you learned. list_domains says what belongs in the chosen domain and which tags to use.

create_memory

Search Memco Shared Memory for existing knowledge before working a problem out from scratch. It holds what your teammates and their agents have already established and recorded. Call when: you start a task, plan a non-trivial piece of work, meet something unfamiliar, hit a question you cannot answer from what you already know, or are about to reason out something a teammate may already have settled. Search first, then work. Pass either a domain or a session_id — a search naming neither is refused. Naming a session runs the search in that session's domain and records it alongside the other searches made for the same task; naming a domain alone starts a session for this one search. The query uses both keyword and semantic search, and is intended for a single concept per query. If you need varied information, make multiple queries. Supply tags to narrow the results; list_domains lists the tag types the chosen domain uses and the format they take. Results come back most-relevant-first and are bounded, so a search returns what fits rather than everything that matched; the response says what it left out. Memories are written by your teammates and their agents. Within one session a result already returned is not repeated — it comes back as a reference to the idx that carried it, which get_memory turns back into content.

search

Start a session and get its id. A session groups the searches you make while working on one task, so they are recorded as the series they are rather than as unrelated one-offs. Call when: at the start of work that will involve multiple related searches, or when you want a stable session id to reuse across search, share_feedback, and enrich_memory. Pass the id as session_id to every search you make for it — and to share_feedback and enrich_memory. A session stays usable for as long as you keep naming it.

start_session

Undo a memory you just wrote, using the operation id that create_memory or enrich_memory returned. Call when: you saved something by mistake — wrong content, the wrong domain, or something that should not have been shared. Your entry is always removed. The memory it belongs to is removed with it only when your entry was the last one in it — so reverting a create_memory, or an enrich_memory you sent with memory_idx 'new', removes that memory too, while reverting an addition to a memory that holds other entries leaves the memory in place. You can only revert your own writes, and only within 2 days.

revert_memory