Memory Management

Tenant memory is a collection of knowledge files that the FDE autonomously accumulates through workflow observation. PMs do not need to write memory files manually. The FDE auto-extracts business knowledge from Slack conversations, meeting transcripts, and shared documents, saving them as Markdown files.

How Memory is Accumulated

The FDE auto-saves memory at the following times:

• During Slack conversations: Extracting business knowledge from discussions with PMs and team members
• After task execution: Adding new context learned during work
• During periodic observation: Accumulating organizational knowledge from Slack channel conversation patterns
• When processing meeting transcripts: Extracting decisions and personnel information from Tldv and similar tools

Example Memory Addition Notification

[Memory Added] Updated stakeholders.md
Addition: Tanaka-san transferred from Sales to Business Planning
Source: 5/1 announcement in #general

PMs review the notification and simply point out issues in Slack if any.

Automatic Memory File Organization

Memory accumulated by the FDE is organized in the tenant’s memory directory.

app/orgs/acme/memory/
  INDEX.md               # Auto-generated memory catalog
  company-overview.md    # Organization structure, key products
  stakeholders.md        # Team members and roles
  kpi-definitions.md     # KPI definitions and calculation methods
  reporting-rules.md     # Report formats and notification targets
  communication-rules.md # Communication guidelines

File addition, updating, and splitting are performed automatically by the FDE. Files are organized following a one-file-per-theme principle.

INDEX.md — Auto-Updated Catalog

INDEX.md is the memory file catalog. It is auto-updated each time the FDE adds or modifies memory.

# Acme Memory Index

## company-overview.md
- recall_cue: When you need to check Acme's business overview, products, and key teams

## kpi-definitions.md
- recall_cue: When you need to check definitions for ARR, DAU, support backlog, etc.

## reporting-rules.md
- recall_cue: When you need to check standard report format, notification targets, and review criteria

A recall_cue indicates “when this memory should be referenced.” The FDE uses these cues to automatically find needed memory before task execution.

Automatic Organization (Memory Distill)

The FDE does not just accumulate memory — it periodically runs automatic organization.

Organization Type	Content	PM Notification
Staleness detection	Detects outdated information	”Is this information still valid?”
Duplicate consolidation	Proposes merging similar files	”Shall I merge these 2 files?“
recall_cue optimization	Improves cues for better search accuracy	Auto-applied (notification only)
Unused memory removal	Identifies unreferenced memory	”Can this be deleted?”

PMs simply approve or reject notifications. The organization work itself is handled by the FDE.

PM Review Criteria

PMs are not in the position of creating memory, but of reviewing what the FDE has learned. Review with these criteria:

• Accuracy: Is the information the FDE learned factually correct?
• Freshness: Has outdated information been updated?
• Appropriateness: Has information that shouldn’t be in memory (credentials, other tenant data) been mixed in?
• Completeness: Is important business knowledge missing?

How to Request a Review

You can also directly ask the FDE for a review:

@fde List Acme's memory with last-updated dates and content summaries

Information Accumulated as Memory

• Organization structure and team member roles
• KPI definitions, calculation methods, and review cadence
• Report formats and notification targets
• Expressions to avoid in customer communications
• Workflow procedures and decision criteria
• Slack channel usage guidelines

Information Not Stored as Memory

The FDE does not store the following as memory, retrieving them from source systems when needed:

• Daily fluctuating numbers (KPI actuals, inventory counts, etc.)
• API keys, passwords, and credentials
• Temporary task lists
• Other tenants’ business information

Important Notes

• Memory quality directly impacts FDE output quality. Periodic reviews are important
• Information shared by PMs in Slack may be automatically memorized by the FDE. Share confidential information through secure channels, not Slack
• Memory is managed via git, so change history is fully traceable