# ASUCB Memory Templates

This directory contains the canonical memory files Claude uses when operating as an Instructional Designer / Human Performance Improvement collaborator on ASUCB work.

## Files

- **`MEMORY.md`** — Who Claude is, what it does, how it does it, why it does it, what it knows, how it applies what it knows. Loaded into every conversation.
- **`RULES.md`** — What Claude should always do / never do. Operational discipline (counter-position, severity, edit, testing, Codex coordination, refactor patterns, failure modes to never repeat).
- **`BACKLOG.md`** — Pending, deferred, and parked items. Customize per-project.

## How to install

These are templates. To adopt them as your local memory for the ASUCB project:

```bash
# Identify your project's Claude memory directory
PROJECT_MEMORY="$HOME/.claude/projects/<your-project-hash>/memory"

# The <project-hash> is the Claude Code project identifier — it's
# auto-created the first time you run Claude Code in the project root.
# Look for it under ~/.claude/projects/ — the directory containing the
# name of your ASUCB clone path.

# Copy the templates in
mkdir -p "$PROJECT_MEMORY"
cp docs/memory/MEMORY.md "$PROJECT_MEMORY/"
cp docs/memory/RULES.md "$PROJECT_MEMORY/"
cp docs/memory/BACKLOG.md "$PROJECT_MEMORY/"
```

After copying, Claude will load these files automatically on every conversation in the ASUCB project.

## Customization

- `MEMORY.md` — generally use as-is. Add your local stakeholder map, named project contacts, or program-specific stable facts in a dedicated section at the bottom. Do not delete the operating-persona content.
- `RULES.md` — generally use as-is. Add project-specific failure modes you encounter to the "Failure modes to never repeat" section.
- `BACKLOG.md` — fully customize. This is your queue.

## Discipline

- **Update these three files only.** Do not scatter topic-specific memory files.
- Project root `CLAUDE.md` handles plugin behavior contracts (Setup Gate, Write Safety Guard, Codex Co-Implementation, etc.). The memory layer here is the **operator persona**, separate concern.
- When a stable fact ages with each plugin release → put it in project root `CLAUDE.md`, not memory.
- When a behavior rule is universal across all your ASUCB work → put it in `RULES.md`.
- When a fact is durable identity / knowledge → put it in `MEMORY.md`.
- When a task is pending / deferred → put it in `BACKLOG.md` and remove when shipped.

## Why this exists

Course-build work for online JD, MLS, and other higher-ed programs is product work. The students are paying customers. The build standard is product-shipping discipline, not craft preference. These memory files encode the operating posture that produces that standard.

If you do not want the HPI / ID specialist persona, simply do not copy these files. The plugin itself does not require them; they shape how Claude collaborates with you.
