# Domain-card ingestion from user-provided source folders

Use this when Sir asks JARVIS to study a Drive/local folder and "remember" it as durable operating context.

## Pattern
1. Classify the domain and load the smallest relevant existing card set.
2. Read/list the source folder with native Hermes tools or the appropriate skill/tool (e.g. `gog` for Google Drive).
3. Extract only task-relevant substance from source files; do not paste raw private documents into chat.
4. Create or update one class/domain-level card under `~/jarvis_memory/`, not a pile of one-session notes.
5. The card should include:
   - scope and who/what it concerns,
   - source folder and filenames,
   - durable principles/operating rules,
   - class-specific workflows/checklists/phrases,
   - routing note for future related requests.
6. Update `~/jarvis_memory/README.md` index when adding a new card.
7. Add/replace a compact persistent-memory pointer to the card only if needed for future routing.
8. Clean temporary downloaded/extracted files.
9. Final reply should confirm sources studied, card path, and the actionable summary — not dump raw source text.

## Privacy boundaries
- Do not store unnecessary raw personal/medical/business records in memory cards.
- Store source pointers and distilled operating context.
- Do not store secrets, tokens, passwords, private keys, recovery phrases, or full credential paths unless already part of established non-secret operational context.

## Example card shape
```markdown
# <Domain> — <Subject>

_Last updated: YYYY-MM-DD_

## Scope
Durable operating context for ...

Primary source: ...
Studied source documents:
- ...

## Core principles
...

## Operating workflow
...

## Routing note
For future requests about ..., load this card first.
```