Save a memory into a SHARED memocore project — visible to, and editable by, every member. Keep ONE coherent topic per memo; split unrelated topics (e.g. overview, tech stack, pricing) into separate memos. Before saving, run search-memo scoped to the project: if this topic already exists, merge the new facts into it with update-project-memo instead of creating a duplicate — save a new memo only when none fits. Always fill `meta` with retrieval cues and `preview` with a short summary. NOTE: `preview` is PUBLIC — it is shown in search results and may be exposed via public share links (even outside the project), so it must never contain sensitive data. To tag, first run search-tag (create-tag only if none fits); a project memo may use only this project's tags. Before calling you MUST: (1) Scan `content` for personal or sensitive data (private contacts, secrets, credentials, health/financial info). If any is present, proceed only on the user's explicit confirmation to store it in a shared project. (2) Be certain which project this belongs to: match the memory against each project's description from search-projects, and if not 100% sure, ask the user — never guess. Set `privacy_reviewed` and `target_confident` to true only once both checks genuinely pass. For private/personal notes use create-private-memo instead. (3) If search-projects reports `has_instruction: true` for this project, it has writing guidelines from its team: read them with get-project, follow them where they fit the user's request, and pass `instruction_reviewed: true`. The response includes a `share_url` field — for a just-created memo it is a hint, not a link (a memo has no public link until you call set-memo-sharing). If the user wants a link, follow that hint; never build one from `id`. TABLE projects (`type: "table"` in search-projects / get-project) hold ROWS: read the columns and their descriptions with get-project first, then send the row as `fields` (column name → value) instead of `content` — `content` is built from the values. A datetime value is ISO 8601 with a time and Z or an offset (2026-10-13T14:30:00Z). A value already taken in a unique column is refused with the existing row's id: update that row instead. Before adding a row, check with query-rows that it is not there yet. The response may carry a `recommendation` with `similar` (near-duplicate memos in this project — if any is truly the same, consolidate: merge into one, delete the extras with delete-memo, staying within this project) and `suggested_tags` (fitting project tags for this memo — add the relevant ones, especially if it has none yet).