quarry-capture

Quarry Capture

Three verbs, three distinct jobs. Pick the one that matches what actually happened, not the one that's easiest to reach for.

Verb taxonomy

• remember — one durable, agent-scoped item: a fact, a procedure, an opinion, or an observation. Filed under an agent_handle, findable later by that handle or by anyone searching broadly.
• learn — a distilled lesson the whole project should follow (a rule, a convention, a "do it this way" insight). No handle — it's project-wide, not personal — and it gets retrieval preference over ordinary results.
• ingest — a URL. Fetches and indexes it (sitemap-aware, single-page fallback). For local files or directories already on disk, use register_directory + sync, not ingest.

Recognize the trigger and the five moments

Call remember (or learn) at these moments — not at the end of a session, and not never:

1. You found a non-obvious root cause or gotcha → remember, memory_type=fact.
2. A decision was ratified, with its reason → remember, memory_type=fact.
3. You worked out a repeatable how-to → remember, memory_type=procedure.
4. You formed a judgement you'll want to revisit → remember, memory_type=opinion.
5. Once, before submitting a mission result — one note on what you'd tell yourself next time → remember, memory_type=observation.

Separately: when the insight is a rule the whole team/project should follow, not just your own note-to-self → learn instead of remember.

Run it

printf '%s' "<content>" | quarry remember --name <topic-slug> \
  --agent-handle <your-handle> --memory-type fact --summary "<one line>"

quarry learn "<lesson, <=500 chars>" [--topic <domain>] [--name <slug>]

quarry ingest <url> [--overwrite] [--collection <name>]

remember reads its content from stdin, not a positional argument — pipe it in.

Confirm the exact flags with quarry remember --help / quarry learn --help / quarry ingest --help before relying on one not shown here.