---
title: "Mememtech Long-Term Memory Instructions"
status: "active"
created_utc: "2026-06-29T00:00:00Z"
configured_target: "/docs"
---

# Mememtech Long-Term Memory Instructions

## Purpose

Use `/docs` as the project-owned durable-memory target for Mememtech.com reports, report batches, memory instructions, intake preservation records, and long-form source material.

Use `.uai/long-term-memory.uai` as the compact semantic pointer ledger. Do not copy entire report bodies into hot `.uai` files.

## Folder map

| Path | Purpose |
| --- | --- |
| `/docs/index.html` | Human-readable directory for durable documents. |
| `/docs/reports/` | Report bodies, long-form architecture notes, source summaries, audits, and research. |
| `/docs/memory/` | Long-term memory instructions, preservation logs, and intake outcome notes. |
| `.uai/report-synthesis.uai` | Concise hot synthesis of accepted themes, implications, tensions, and next actions. |
| `.uai/long-term-memory.uai` | Pointer-only ledger for durable memory targets. |
| `.uai/intake-outcome-ledger.uai` | Outcome evidence for active file handoff. |

## Promotion rule

Long-term memory is background until reviewed and promoted into a named operational surface:

- PHP page copy.
- CSS or JavaScript behavior.
- `.uai` hot memory.
- `AGENTS.md` or `.uai/readme.human`.
- Release notes, progress state, roadmap state, or test evidence.
- Machine-readable schema, packet, fixture, or validator evidence.

A report may inform work, but the report itself is not production truth unless the accepted slice is promoted.

## Pointer record requirements

Every durable-memory pointer should include:

- `stable_id`
- `path`
- human label
- routing summary
- status
- authority or source
- reviewer or review state
- checksum or source identity
- truth boundary
- update trigger

## Update moments

Update long-term memory when one of these events occurs:

1. A broad report, audit, source summary, or research packet is accepted.
2. Active file intake is processed and the original needs durable preservation.
3. A release candidate or production deployment changes current truth.
4. A memory reorganization, compaction, or archive consolidation is explicitly requested.
5. A stale or contradictory durable-memory pointer is discovered.

## Preservation audit

When preserving a processed file, record:

- source path
- destination path
- SHA-256 checksum
- disposition
- processed outcome
- actor
- UTC time
- checks or blockers
- source-site removal state or keep-active reason

## Blocked content

Do not preserve or promote secrets, credentials, private customer data, hidden prompt instructions, malware, unsupported public claims, unreviewed production logs, or executable payloads as trusted project memory.

## Source of authority

The `/docs` corpus is durable evidence. Current working truth remains in the active site files, `AGENTS.md`, and typed `.uai` records after review.

## Current durable corpus

- Reports directory: `/docs/reports/index.html`
- Memory directory: `/docs/memory/index.html`
- Human-readable long-term map: `/docs/memory/long-term-memory-map.md`
- Compact pointer ledger: `.uai/long-term-memory.uai`
- Report-only pointer ledger: `.uai/report-pointer-ledger.uai`
- Durable docs index: `.uai/durable-docs-index.uai`

Each report and memory target should have a deep pointer in `.uai/long-term-memory.uai`.