> ## Documentation Index
> Fetch the complete documentation index at: https://ulpi.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Common Workflows

> Real-world examples of Memory Module in action

# Common Workflows

**Practical examples from actual customers.** Learn how teams use Memory Module for knowledge management, customer context, sales, research, and content creation.

***

## Personal Knowledge Management

**Goal:** Build a second brain that learns what's important to you.

<Steps>
  <Step title="Capture as You Learn">
    ```
    Store: "React Server Components eliminate client-side
    data fetching by allowing async fetch on server.
    Reduces bundle size and improves initial page load."

    Tags: react, server-components, performance
    Sector: semantic
    ```

    System automatically creates semantic understanding and links.
  </Step>

  <Step title="Let Connections Form">
    Don't manually organize! Waypoints automatically connect:

    * Server Components → Next.js App Router
    * Server Components → Bundle Optimization
    * Server Components → Hydration Issues

    Search "React performance" → Get all connected context.
  </Step>

  <Step title="Reinforce Key Concepts">
    ```
    Reinforce Server Components memory with Deep Learning
    ```

    Slows decay—perfect for core concepts you're studying.
  </Step>

  <Step title="Let Temporary Fade">
    ```
    Store: "Trying to figure out why useEffect runs twice..."
    Sector: episodic
    ```

    Once resolved, fades naturally. No filing required!
  </Step>
</Steps>

**Result:** Knowledge base mirrors your learning—important concepts stay fresh, temporary details fade.

***

## Software Development Team

**Goal:** Maintain team context about decisions, patterns, "why we did it this way."

<Tabs>
  <Tab title="Architectural Decisions">
    ```
    Store Reflective: "We chose PostgreSQL over MongoDB because:
    1. Strong ACID guarantees for financial data
    2. Complex joins for reporting
    3. Team SQL expertise
    4. Mature BI ecosystem

    Decision: 2025-01-15
    Participants: Sarah, Marcus, Aisha
    Alternative: MongoDB (rejected for lack of joins)"

    Tags: architecture, database, postgresql, adr
    Sector: reflective
    ```

    **Why Reflective:** Strategic decisions with lasting impact (693-day half-life)
  </Tab>

  <Tab title="Code Patterns">
    ```
    Store Procedural: "Our API error handling pattern:
    1. Throw custom exceptions in services
    2. Catch in controller, return JsonResponse
    3. Log with context (user ID, request ID)
    4. Return standardized format: {message, error_code, details}

    See: app/Exceptions/PaymentFailedException.php"

    Tags: patterns, error-handling, api
    Sector: procedural
    ```

    **Why Procedural:** How-to knowledge needing occasional refresh (87-day half-life)
  </Tab>

  <Tab title="Bug Investigations">
    ```
    Store Episodic: "Production slowdown 2025-01-20:
    - Symptom: API latency 150ms → 3s
    - Root cause: Missing index on users.email (1M+ rows)
    - Fix: Added index, latency back to 120ms
    - Prevention: Added DB monitoring to CI
    Resolution time: 45 minutes"

    Tags: bugs, performance, database, incident-2025-01-20
    Sector: episodic
    ```

    **Why Episodic:** Time-bound event that fades after lessons learned (46-day half-life)
  </Tab>

  <Tab title="Team Onboarding">
    **New dev asks:** "Why PostgreSQL?"

    AI searches memories and returns:

    1. Original decision (Reflective, 6 months ago, still strong)
    2. Performance investigations (Episodic, recently accessed)
    3. Database patterns (Procedural, frequently referenced)
    4. MongoDB lessons (Reflective, waypoint-connected)

    **Result:** Complete context in seconds, not hours of Slack archaeology.
  </Tab>
</Tabs>

***

## Customer Support Memory

**Goal:** Remember customer context across interactions.

<CardGroup cols={2}>
  <Card title="Customer Preferences" icon="user">
    ```
    Store Semantic: "Customer: Acme Corp
    - Prefers email over phone (mentioned 3x)
    - CEO Sarah responds faster on Slack
    - Quarterly reviews Q2 and Q4
    - Sensitive about pricing
    - Timezone: PST (9am-5pm)"

    Tags: acme-corp, customer-preferences
    Sector: semantic
    ```
  </Card>

  <Card title="Support Interactions" icon="headset">
    ```
    Store Episodic: "Call with Acme - 2025-01-20
    Issue: Rate limiting (429 errors)
    Resolution: Upgraded Starter → Pro
    Sentiment: Initially frustrated → happy
    Follow-up: Check in after 1 week
    Agent: Marcus"

    Tags: acme-corp, support, upgrade
    Sector: episodic
    ```
  </Card>

  <Card title="Emotional Context" icon="heart">
    ```
    Store Emotional: "Acme CEO very excited
    about Memory Module during demo.
    Mentioned this solves their 'context loss
    problem' from months of struggle.
    High enthusiasm for expansion."

    Tags: acme-corp, positive-sentiment
    Sector: emotional
    ```

    Sentiment fades fast (35 days) but valuable for immediate interactions
  </Card>

  <Card title="Before Next Call" icon="phone">
    **Agent searches:** "Acme Corp"

    AI returns:

    * Customer preferences (always accessible)
    * Recent interactions (last 3 months, ranked)
    * Positive sentiment from last call
    * Pro plan details and usage
    * Similar customers with rate issues (waypoints)

    **Result:** Agent has complete context. Customer feels remembered.
  </Card>
</CardGroup>

***

## Sales & CRM Context

**Goal:** Personalized conversations with rich prospect context.

<Tabs>
  <Tab title="Prospect Research">
    ```
    Store: "Prospect: TechStartup Inc
    - Series A: $10M (Jan 2025)
    - 25 engineers, planning 2x in 6 months
    - Stack: Next.js, PostgreSQL, AWS
    - Pain: 'drowning in context switching' (Twitter)
    - Current: Notion + linear notes (frustrated)
    - Decision maker: CTO David Kim (Twitter follower)"

    Tags: prospect, techstartup-inc, series-a
    Sector: semantic
    ```
  </Tab>

  <Tab title="Sales Calls">
    ```
    Store: "Discovery call - TechStartup - 2025-01-22
    Insights:
    - Biggest pain: 2-3 hrs/day finding context
    - Budget: $500-1000/month acceptable
    - Timeline: Decide by end of Q1
    - Objection: Concerned about adoption (bad Notion experience)
    - Next: Technical demo 2025-01-29
    Sentiment: Positive, leaning toward purchase"

    Tags: techstartup-inc, discovery-call, objections
    Sector: episodic
    ```
  </Tab>

  <Tab title="Competitive Intelligence">
    ```
    Store: "TechStartup tried Notion but 'nobody used it
    after first week because it required too much manual
    organization.' Common objection.

    Counter: Emphasize automatic organization and
    reinforcement—no manual filing needed."

    Tags: objections, notion-competitor, adoption-concerns
    Sector: reflective
    ```
  </Tab>

  <Tab title="Before Follow-Up">
    **Sales rep searches:** "TechStartup technical demo preparation"

    AI returns:

    * Stack and pain points (semantic)
    * Previous call notes with objections (episodic)
    * Strategies from similar Series A customers (waypoints)
    * Competitive intelligence about Notion (reflective)

    **Demo customized:** "I know you tried Notion and struggled with adoption..."

    **Result:** Prospect feels understood. Close rate improves 35%.
  </Tab>
</Tabs>

***

## Research & Academic Work

**Goal:** Build interconnected knowledge while studying complex topics.

<Steps>
  <Step title="Store Research Papers">
    ```
    Store: "Paper: 'Attention Is All You Need' (Vaswani et al., 2017)
    - Transformer architecture replacing RNNs
    - Self-attention mechanism allows parallel processing
    - Positional encoding for sequence order
    - Multi-head attention captures different relationships
    - Foundation for BERT, GPT, modern LLMs

    Citation: arXiv:1706.03762"

    Tags: transformers, attention-mechanism, deep-learning, paper
    Sector: semantic
    ```
  </Step>

  <Step title="Connections Form Automatically">
    Related memories, waypoints auto-connect:

    * Attention mechanism → BERT pre-training
    * Transformers → GPT architecture
    * Parallel processing → Training efficiency
    * Positional encoding → Sequence modeling

    Search "how do transformers handle sequence order?" → Positional encoding WITH related transformer concepts.
  </Step>

  <Step title="Study Notes with Spaced Repetition">
    ```
    Store: "Study: Understanding self-attention
    - Q, K, V matrices project input embeddings
    - Attention score = softmax(Q·K^T / √d_k)
    - Higher scores = more relevant tokens
    - Multiple heads capture different relationships
    Confidence: Medium (need practice)"

    Tags: transformers, self-attention, study-notes
    Sector: semantic

    Then: Reinforce with Deep Learning profile weekly
    ```
  </Step>

  <Step title="Ephemeral Exploration Fades">
    ```
    Store: "Trying to understand why √d_k scaling is needed...
    Something about variance stabilization? Read appendix again."
    Sector: episodic
    ```

    Fades in \~46 days unless revisited. No cleanup needed!
  </Step>
</Steps>

**Result:** Core concepts persist and strengthen, exploration notes fade, connections form automatically.

***

## Content Creation & Writing

**Goal:** Maintain idea continuity without drowning in notes.

<CardGroup cols={2}>
  <Card title="Capturing Ideas" icon="lightbulb">
    ```
    Store: "Article: 'Why Your AI Assistant
    Needs Memory Like Your Brain'
    Angle: Compare vector DBs vs cognitive memory
    Hook: 'You remember your wedding, not yesterday's lunch'
    Target: Developers building AI apps
    Status: Idea stage"

    Tags: article-ideas, ai-memory
    Sector: episodic
    ```
  </Card>

  <Card title="Research & Quotes" icon="quote-left">
    ```
    Store: "Quote for AI memory article:
    'The faintest ink is more powerful than the
    strongest memory' - Chinese proverb
    Context: Contrast traditional note-taking vs
    cognitive memory (selective retention)

    Source: Research notes, Jan 2025"

    Tags: quotes, ai-memory-article
    Sector: semantic
    ```
  </Card>

  <Card title="Draft Tracking" icon="pen">
    As you work on article, references reinforce automatically:

    * Search "AI memory article" multiple times → Reinforcement increases
    * Related research appears through waypoints
    * Unused ideas fade naturally
  </Card>

  <Card title="Completed Work" icon="check">
    ```
    After publishing:
    Store: "Published: 'Why Your AI Assistant Needs Memory'
    - Medium, 2025-02-01
    - Performance: 1,200 views first week, 145 comments
    - Top comment: Request for technical deep-dive
    - Follow-up idea: 'Building Cognitive Memory Systems'"

    Tags: published, ai-memory, portfolio
    Sector: reflective
    ```

    Ideas that gain traction (repeated access) stay strong. One-off thoughts fade. Published work persists.
  </Card>
</CardGroup>

***

## Integration Patterns

### Cross-Tool Memory

**Same memory system, all tools, complete context everywhere:**

* **Claude Desktop** (morning): Store today's priorities
* **Continue (VS Code)**: Search for PR context while coding
* **Cursor (different project)**: Search for Q1 planning

All tools access same memories instantly.

### API Automation

```javascript theme={null}
// Auto-store from GitHub PRs
async function storePRContext(pr) {
  await fetch('https://api.ulpi.io/api/v1/memories', {
    method: 'POST',
    body: JSON.stringify({
      content: `PR #${pr.number}: ${pr.title}\n${pr.body}`,
      sector: 'episodic',
      tags: ['github', 'pr', ...pr.labels]
    })
  });
}

// Scheduled reinforcement
async function reinforceCriticalDocs() {
  const critical = await searchMemories({ tags: ['critical', 'documentation'] });
  for (const memory of critical) {
    await reinforceMemory(memory.id, 'maintenance');
  }
}
```

***

## Pro Tips

<AccordionGroup>
  <Accordion title="Start Small, Build Momentum">
    Don't migrate existing notes at once. Start by storing new information naturally. The system builds value incrementally.
  </Accordion>

  <Accordion title="Trust the Decay">
    Resist urge to manually organize everything. Let unimportant information fade. Important stuff naturally reinforces through access.
  </Accordion>

  <Accordion title="Use Sector Classification">
    Take 2 seconds to choose right sector:

    * Strategic decisions → Reflective (long-lasting)
    * How-to guides → Procedural (medium)
    * Facts/reference → Semantic (medium-long)
    * Events/meetings → Episodic (short-medium)
    * Sentiment/feedback → Emotional (short)
  </Accordion>

  <Accordion title="Tag Thoughtfully">
    3-7 tags is ideal:

    * Project/product names
    * Key entities (people, companies)
    * Topic areas

    Don't over-tag—semantic search handles the rest!
  </Accordion>

  <Accordion title="Reinforce Proactively">
    Don't wait for memories to fade. Reinforce critical info immediately:

    * Strategic decisions → Emergency profile
    * Core docs → Deep Learning profile weekly
    * Reference materials → Maintenance profile bi-weekly
  </Accordion>

  <Accordion title="Use the Admin Panel">
    Monitor memory health:

    * Check sector distribution (balanced across types?)
    * Identify hot memories (frequently accessed?)
    * Review decay trends (anything critical fading?)
    * Prune regularly (keep knowledge base focused)
  </Accordion>
</AccordionGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Best Practices" icon="star" href="/memory/best-practices">
    Optimization tips for search, reinforcement, token management
  </Card>

  <Card title="Cognitive Sectors" icon="brain" href="/memory/cognitive-sectors">
    Deep dive into 5 memory types
  </Card>

  <Card title="API Reference" icon="code" href="/memory/api-reference">
    Complete REST API docs for automation
  </Card>

  <Card title="MCP Integration" icon="plug" href="/memory/mcp-integration">
    Platform-specific setup for AI assistants
  </Card>
</CardGroup>

***

*Real-world workflows from actual customers. Start small, trust the system, let connections emerge naturally.*