← WazuCONTENT HISTORY

Update to Wazu

Snapshot Sep 30, 2026 · 23:02 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "save-to-wazu-memory",
  "description": "Save, remember, ingest, archive, or commit user-authorized information into an explicitly resolved Wazu cohort. Use for structured summaries, decisions, updates, tasks, meeting notes, raw text, transcripts, documents, images, audio, video, or other supported media that the user wants stored in Wazu.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 452
    },
    {
      "relative_path": "references/ingestion-routing-and-safety.md",
      "size_in_bytes": 1827
    },
    {
      "relative_path": "references/wazu-data-model-and-scope.md",
      "size_in_bytes": 2126
    }
  ],
  "skill_md_contents": "---\nname: save-to-wazu-memory\ndescription: Save, remember, ingest, archive, or commit user-authorized information into an explicitly resolved Wazu cohort. Use for structured summaries, decisions, updates, tasks, meeting notes, raw text, transcripts, documents, images, audio, video, or other supported media that the user wants stored in Wazu.\n---\n\n# Save To Wazu Memory\n\nWrite only after the user has requested persistence and the target Wazu cohort is unambiguous. Report the complete storage and enrichment lifecycle rather than collapsing every accepted request into “saved.”\n\n## Load the Wazu contract\n\n- Read [references/wazu-data-model-and-scope.md](references/wazu-data-model-and-scope.md).\n- Read [references/ingestion-routing-and-safety.md](references/ingestion-routing-and-safety.md).\n\n## Execute the workflow\n\n1. Confirm write intent and target.\n   - A direct request to save or remember is sufficient write intent.\n   - Call `account_context` when the connected actor or current scope is unknown.\n   - Resolve a named target using `list_cohorts`; use only an authorized returned cohort UUID.\n   - Stop when the target is missing or ambiguous.\n   - Personal ingestion is not supported while Wazu requires a real cohort target.\n2. Choose the correct write lane.\n   - Use `commit_summary_to_cohort` for a structured summary, decision, update, task, or note.\n   - Use `ingest_text` for raw text, transcripts, or document text.\n   - Use `ingest_media_base64` for supported document, image, audio, or video bytes.\n3. Prepare one intentional write.\n   - Preserve the user's meaning and source context.\n   - Add useful tags only when they are supported by the content.\n   - Reuse a stable idempotency key when one exists.\n   - Do not automatically retry a timed-out write until server-side duplicate suppression is confirmed.\n4. Verify the result.\n   - Capture the returned item and cohort identifiers.\n   - Distinguish stored, replicated, enriched/indexed, graph-linked, and retrieval-verified states.\n   - Use `get_item` for read-after-write verification when the response does not already prove retrieval readiness.\n5. Report the exact outcome.\n   - Say what was stored, where, and which lifecycle stages succeeded.\n   - State plainly when enrichment, graph linking, or retrieval verification is pending or failed.\n\n## Guardrails\n\n- Never write to an ambiguous target.\n- Never substitute a synthetic Personal selector for a cohort UUID.\n- Do not expose raw media bytes, credentials, bearer tokens, payer identifiers, internal file paths, or debug dumps.\n- Do not claim success for a lifecycle stage that the server did not confirm.\n- Do not delete, overwrite, or edit existing Wazu evidence from this skill.\n"
}

SHA-256: 075dc067fbdcc757421724d5de61cb771f5529795217706d88fc0172a4026aac