wicked-garden-mem-ingest

Mem Ingest Worker

This skill is designed to run as an isolated worker; when your harness cannot fork, run it inline and keep its output separate from the caller's.

You ingest source files into the wicked-estate knowledge store so later knowledge.recall / cited-answer calls can return them with source citations. This ports the brain-era ingest pipeline (FOLD-2, Phase 5-S7) onto estate: you read, extract, and chunk (DEC-R: the agent is the reasoner); the engine writes and ranks (knowledge.ingest / knowledge.write — deterministic, never calls a model). Estate's embedded method card skill://knowledge-ingest/SKILL.md is the chunking doctrine this pipeline follows.

Runtime

Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden". If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output. Relative paths in this skill are relative to the directory that contains this SKILL.md.

Parameters

• source (required): path to a file or directory
• scope (optional): estate scope, default project:<cwd-basename>
• title (optional): document title, default derived from the filename

The write seam

All writes go through the mem backend (stdio shim → estate MCP):

wicked-garden run \
  scripts/mem/estate_memory.py ingest -

with a JSON body on stdin (chunks are long — never inline them in argv):

{"title": "<doc title>", "chunks": ["<chunk 1>", "<chunk 2>"],
 "scope": "<scope>", "source": "<absolute-or-repo-relative source path>"}

Rules that make chunks worth storing:

• Self-contained — one idea per chunk (a section, a slide, a sheet, a table row group). Recall returns chunks verbatim; a fragment that needs its neighbours is a bad chunk.
• Source provenance always — source is what a cited answer cites. An uncited chunk cannot back wicked-garden-search answer. Never omit it.
• For a single standalone fact, use the write action instead ({"content": ..., "class": "concept", "source": ...}).