# Memory Review Workflow

## Purpose

This workflow prevents accidental installation of personal memory. It keeps the archive, candidate layer, and approved memory layer distinct.

## Files

Review packets live in:

```text
review/barely-but-here-memory-candidates.md
review/bert-identity-voice-memory-candidates.md
review/ai-systems-assessment-memory-candidates.md
```

Architecture/governance docs live in:

```text
docs/memory-scope-and-review-governance.md
docs/openbrain-bert-memory-architecture.md
docs/archive-parsing-reaudit-openbrain.md
docs/openbrain-bert-supabase-extension.sql
```

## Review decisions

Each candidate starts as:

```text
Review decision: PENDING
```

Bert can change this to one of:

```text
APPROVE
EDIT
REJECT
SOURCE_ONLY
```

### APPROVE

Use this if the candidate should become durable memory.

### EDIT

Use this if the idea is right but the wording should change before approval.

### REJECT

Use this if the candidate is not important enough for long-term memory.

### SOURCE_ONLY

Use this for important drafts, passages, or references that must remain findable but should not become installed memory.

This is especially important for Barely, But Here drafts: all drafts are must-preserve source material, but not every paragraph should become durable memory.

## Current first-install domains

Only these are in scope:

1. Barely, But Here and all article drafts across backups
2. Bert identity / professional positioning / writing voice
3. AI Systems Assessment campaign for urgently needed income

## Suggested review process

1. Start with `bert-identity-voice-memory-candidates.md` because it shapes AI collaboration.
2. Review `ai-systems-assessment-memory-candidates.md` next because it is income-critical.
3. Review `barely-but-here-memory-candidates.md` third because it is larger and should distinguish source preservation from installed memory.

## After review

Once Bert marks decisions, run or ask Hermes to run an approved-memory export. The export should produce:

```text
approved-memory/approved-memories.jsonl
approved-memory/source-only-index.jsonl
approved-memory/rejected-memory-log.jsonl
```

Approved memories can then be inserted into Open Brain/Supabase with the Bert-specific metadata from:

```text
docs/openbrain-bert-supabase-extension.sql
```

## Restart/loading rule

After MCP/Open Brain configuration changes, Hermes should start a new session or reload MCP so new tools are visible.

But the archive itself should not be stuffed into the prompt. Hermes should use:

```text
small approved memory profile
+
Open Brain memory search
+
archive source retrieval
```

Hermes should use the same approved-memory/Open Brain layer across WebUI, Telegram, and any future gateway surfaces. Channel-specific session context may differ, but durable memory should remain shared, reviewed, and provenance-backed.

This is the harnessed partnership model.