Store Fact
store_factStore information that should persist across sessions.
Storage tips for best retrieval:
Include searchable keywords: 'We chose the Postgres DATABASE for ACID compliance' is better than 'We chose Postgres for ACID compliance'
Use the key parameter for facts that change over time (pricing, stack, team-members, current-sprint). When you store with the same key, the old version is archived automatically.
Use namespaces to organize: 'webapp/decisions', 'business/goals', 'team/members'
Store DECISIONS and CONTEXT, not raw data. 'We decided X because Y' is more useful than 'X happened'
Use category to classify: technical, decision, preference, identity, relationship
Use layer for context depth: 0=identity(stable), 1=architecture(monthly), 2=state(weekly), 3=session(daily)
Before ending a conversation, call store_session_summary to preserve continuity.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | Named key for this fact. Storing with the same key auto-archives the previous version. Use for facts that change over time: 'session-latest', 'current-stack', 'team-size'. | |
| text | Yes | The fact to store | |
| layer | No | Context persistence layer: 0=identity/stable, 1=architecture/monthly, 2=state/weekly, 3=session/daily. Pass 0-3 as integer or string. | |
| category | Yes | Fact category | |
| namespace | No | Optional namespace to organise facts (e.g. 'work', 'personal'). Defaults to 'default'. | |
| is_permanent | No | Whether this fact should bypass temporal decay | |
| related_facts | No | Optional list of related fact UUIDs to link (knowledge graph edges) |