# Memory Asset Audit Checklist

Use this checklist during a real audit. Keep the timing tight: the goal is to convert passive notes into operational memory assets in 30 minutes.

```md
# Memory Asset Audit

Date:
Source audited:
Notes reviewed:

## Step 1. Inventory (5 minutes)

- Total notes reviewed:
- Date range:
- Source URL or path:

## Step 2. Classification (5 minutes)

- asset-ready: 
- reference: 
- ephemeral: 
- hidden asset: 

## Step 3. Promoted assets (5 minutes)

- asset name -> target file
- asset name -> target file
- asset name -> target file
- asset name -> target file

## Step 4. New reusable rules (5 minutes)

- Rule: [behavior] because [reason] in [situation]
- Rule: [behavior] because [reason] in [situation]
- Rule: [behavior] because [reason] in [situation]

## Step 5. New file types (5 minutes)

- file name -> one-line purpose -> what belongs -> what does not
- file name -> one-line purpose -> what belongs -> what does not

## Step 6. System updates (5 minutes)

- Start Here updated: yes / no
- Operating standards updated: yes / no
- File structure updated: yes / no
- Operating log note added: yes / no
```

## Definitions

- **Asset-ready note** — already contains a decision, rule, standard, or judgment that can be reused.
- **Reference note** — useful background, but not a reusable rule. Stays as a note.
- **Ephemeral note** — status update, log, or working memory. Archives or deletes.
- **Hidden asset** — a long note that contains a reusable insight buried inside prose. Extract it.

## Reusable rule format

A reusable rule has three parts:

1. a clear behavior
2. a reason it matters
3. the situation where it applies

If a rule has only behavior, it is brittle. If it has only reason, it is ungrounded. The situation is what makes the rule operational.

## Anti-patterns

- Auditing everything at once.
- Producing a list of notes without classification.
- Writing long memory assets.
- Skipping rule extraction.
- Skipping the system update.