Procedural Memory

Procedural Memory stores "how to do things" - workflows, preferences, patterns, and skills. Unlike factual memories that record what happened, procedural memories capture processes and behaviors that can be executed or followed.

What is Procedural Memory?

Procedural memories represent:

Type	Description	Example
Workflow	Multi-step process	"How to onboard a new customer"
Preference	Behavioral pattern	"Always format dates as YYYY-MM-DD"
Pattern	Observed behavior	"User typically asks follow-up questions"
Skill	Learned capability	"Can generate SQL queries"
Habit	Repeated action	"Reviews PRs every morning"

Procedure Structure

Each procedure contains:

Field	Description
ID	Unique identifier
Goal	What the procedure achieves
Steps	Ordered list of actions
Trigger	What initiates the procedure
Outcome	Expected result
Confidence	How certain we are this works
Execution Count	Times this has been followed

Step Structure

Each step in a procedure includes:

• Action - What to do
• Description - How to do it
• Required - Whether step is mandatory
• Conditions - When to execute this step

Using Procedures in the Visualizer

Viewing Procedures

Navigate to Procedures in the sidebar to see all defined workflows and skills. The grid view shows:

• Procedure title and type
• Success rate indicator
• Step count
• Last updated date
• Execution count

Creating Procedures

Click New Procedure to define a workflow:

1. Set the goal/title
2. Add ordered steps
3. Define trigger conditions
4. Specify required skills

Procedure Details

Click any procedure card to see:

• Full step-by-step breakdown
• Execution history
• Success metrics
• Related memories

API Usage

List Procedures

GET /api/v1/procedures/?limit=20
Headers:
  x-tenant-id: your-tenant-id

Create Procedure

POST /api/v1/procedures/
Headers:
  x-tenant-id: your-tenant-id
Content-Type: application/json

{
  "id": "proc_onboarding_001",
  "goal": "Onboard new customer",
  "steps": [
    {
      "action": "Send welcome email",
      "description": "Use template WEL-001",
      "required": true
    },
    {
      "action": "Schedule kickoff call",
      "description": "Within 48 hours of signup",
      "required": true
    }
  ],
  "skills_required": []
}

Integration Tips

1. Learn from patterns - Extract procedures from repeated user behaviors
2. Track success - Monitor execution outcomes to refine procedures
3. Link to memories - Connect procedures to related factual memories
4. Version procedures - Update steps as processes evolve