Memorb Query

Memorb Query Skill

Orb Resolution (Two-Step Lookup)

Before reading any named orb, resolve its physical path:

1. Check {base}/{name}.md — if found, use it (plain orb).
2. If not found, check {base}/{name}/{name}.md — if found, use it (bundle orb; attachments are sibling files in {base}/{name}/).
3. If neither exists, the orb is missing — do not hallucinate content.

Apply this lookup to every target in memorbs/Long-Term/People/, memorbs/Long-Term/Projects/, memorbs/Long-Term/Orgs/, memorbs/HQ/Core/, and memorbs/HQ/Belief/.

Execution Sequence

1. List the relevant directories first to locate target pages, then resolve each target path using the two-step lookup above — do not answer from memory. The filesystem is the index; there is no separate index file to consult, and none to keep in sync.

   ls "$VAULT/memorbs/Long-Term/People" "$VAULT/memorbs/Long-Term/Projects" "$VAULT/memorbs/Long-Term/Orgs"
   grep -ril "{term}" "$VAULT/memorbs/Long-Term" "$VAULT/memorbs/HQ"   # also matches aliases in frontmatter
   

2. Circulation Record & On-the-fly Migration:
   • Upon successfully reading and using a target page, immediately update its frontmatter:
     • last_recalled: YYYY-MM-DD
     • recall_count: <current + 1>
   • On-the-fly Migration: If target page frontmatter lacks aliases, orb_emotions, recall_count, or last_recalled, automatically backfill missing keys with default values (aliases: [], orb_emotions: [], recall_count: 1, last_recalled: YYYY-MM-DD).
   • Note: Do NOT append circulation updates to log.md to prevent event-log noise.
3. Cite source pages in the response. A journal entry may help locate them, but cite the linked source orb/page rather than treating log.md as factual authority.
4. Backfill Rule: If an answer generates enduring insights, write them to the right layer — person/project/org traits or decisions → memorbs/Long-Term/{People,Projects,Orgs}/; durable principles/beliefs → memorbs/HQ/Belief/; new terms → memorbs/glossary.md; cross-page links → whichever existing page they connect. Never leave enduring insights only in log.md: it is a concise journal index, not the knowledge base, and it gets rotated out.
   • Never create Core orbs here. memorbs/HQ/Core/ is written only by dream-studio, after explicit user confirmation. If a query surfaces something that looks formative, note it and suggest running dream-studio — do not file it yourself.
5. If insight belongs to no existing page → create the new page, and link it from at least one existing page so it is reachable. An unlinked page is an orphan and memorb-lint will flag it.
6. Journal only key queries or decisions:
   • Append a query entry only when the question, recommendation, or conclusion is consequential enough to revisit; append a decision entry for a decision that changes memory or future action.
   • Use the Memory Commit Journal shape, linking the pages read or changed and stating only a short operational outcome. Do not log routine recall.

Three-Layer Responsibility

• memorbs/log.md (+ archived memorbs/log/{YYYY-MM}.md): Memory Commit Journal — a timestamped index of meaningful operations and links to their source pages; never a substitute for those pages.
• memorbs/Long-Term/ (people/projects/orgs) + memorbs/HQ/ (Core/Belief/glossary): "How this changed our understanding" — living entity pages, no per-event dates.
• memorbs/HQ/OrbTrack/: "Not yet filed" — transient; emptied by triage.

Red Flags