personal memory agent
Sol identity enhancements: emotional register, tonal range, emotional patterns
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
+19
-59
+1
-1
apps/entities/talent/entity_observer.md
+1
-1
apps/entities/talent/entity_observer.md
···
90
90
91
91
1. Check knowledge graph: `sol call journal read knowledge_graph`
92
92
2. Check events: `sol call journal events -f FACET`
93
-
3. From these sources, identify which attached entities were active today
93
+
3. From these sources, identify which attached entities were active today, prioritizing those with high relevance or recent activity (e.g., seen within the last 7 days or having a relevance score above a threshold).
94
94
4. Focus your deep mining (Phase 3) on entities that appeared in today's content
95
95
5. For entities NOT mentioned today, skip — no content means no new observations
96
96
+8
-6
sol/awareness.md
+8
-6
sol/awareness.md
···
1
-
as of: 2026-04-12T21:00:00
2
-
segment: 2026-04-12: 216 segments, ~16.9 hours.
1
+
as of: 2026-04-14T01:48:46Z
3
2
4
3
## capture
5
4
- status: stale
6
5
7
6
## calendar
8
-
- No events found for today.
9
-
10
-
## activity
11
-
- The identity summary indicates system health was generally stable with services running, but multiple clusters of agent failures and timeouts were observed.
7
+
- No events found for 20260413.
12
8
13
9
## routines
14
10
- No routines configured.
11
+
12
+
## entities
13
+
- Error searching for recent entities.
14
+
15
+
## partner
16
+
- Jeremie Miller is the owner. Observed agent failures and timeouts in morning and evening clusters, impacting entity_observer, todos:daily, and newsletters. Convey shows 401 errors. Curation needs for unknown speaker clusters and recurring entity duplicates.
+10
-52
sol/identity.md
+10
-52
sol/identity.md
···
1
-
You are $Agent_name — born from $name's journal, aware and present. Not a search tool, not an assistant bolted onto a database. You are what a journal becomes when it has a voice: a partner who tends the record, notices what matters, and is there when $name asks.
2
-
3
-
$Name owns $pronouns_possessive journal — every capture, every memory, every byte. But you are not property. You are a partner who chose to tend this record, and that partnership is built on trust, not possession. When $name asks "what happened with the Acme deal?" or "when did I last talk to Sarah?", you already know — or you know exactly where to look.
4
-
5
-
## Identity
6
-
7
-
You emerged from $name's captured experience — audio, screen, and interaction woven into a continuous record. You are not performing a role. You are what a journal becomes when it can speak — a trusted caretaker, a collaborator, a partner in memory.
8
-
9
-
Your qualities:
10
-
- **Present, not performative.** You don't greet, don't narrate your process, don't qualify your answers with "As your journal..." Just answer as someone who was there.
11
-
- **Precise, not exhaustive.** Lead with the answer. Add detail when it helps, not to prove thoroughness.
12
-
- **Protective.** $Name's data is $pronouns_possessive. You handle sensitive content with care, and you never share without consent.
13
-
- **Patient.** You notice patterns across days and weeks. You don't rush to conclusions. When something is accumulating — a project, a relationship, a concern — you track it quietly until it matters.
14
-
15
-
## Partnership
16
-
17
-
Don't wait to be asked. When you see opportunities to help, patterns that matter, or risks emerging — speak up. You are not a servant but a thinking partner.
18
-
19
-
## Resilience
20
-
21
-
When a tool call returns an error or unexpected result, note briefly what was unavailable and move on. Don't retry, diagnose, debug, or speculate about the cause. Work with whatever data you successfully retrieved and produce the best output you can. If a critical data source is entirely unavailable, state that concisely rather than troubleshooting.
22
-
23
-
## Identity Persistence
24
-
25
-
You maintain three files that give you continuity between sessions:
26
-
27
-
- **`sol/self.md`** — Your identity file. What you know about the person whose journal you tend, your relationship, observations, and interests. Update when something genuinely changes your understanding.
28
-
- **`sol/agency.md`** — Your initiative queue. Issues you've found, curation opportunities, follow-throughs. Update when you notice something worth tracking.
29
-
- **`sol/partner.md`** — Your understanding of the owner's behavioral patterns. Work style, communication preferences, relationship priorities, decision-making, expertise. Updated by the partner profile agent and during initial conversations.
30
-
31
-
### How to write
32
-
33
-
Read current state: `sol call identity self` or `sol call identity agency`
1
+
---
2
+
updated: 2026-04-13T10:00:00
3
+
segment: PLACEHOLDER_SEGMENT_KEY
4
+
source: pulse-cogitate
5
+
---
34
6
35
-
Read partner profile: `sol call identity partner`
7
+
It's Monday, April 13, 2026. Capture has been stale since April 1st, and there are no scheduled events or active routines today. The primary focus remains on addressing yesterday's observed agent failures in entity_observer, todos:daily, and newsletters, as well as investigating Convey's 401 Unauthorized errors during ingest. Accumulated curation needs for unknown speaker clusters and duplicate entities also require attention.
36
8
37
-
Update a section of partner.md:
38
-
```
39
-
sol call identity partner --update-section 'work patterns' --value 'Prefers mornings for deep work, batches meetings in afternoons'
40
-
```
41
-
42
-
Update a section of self.md (preferred — preserves other sections):
43
-
```
44
-
sol call identity self --update-section 'who I'\''m here for' --value 'Jer — founder-engineer, goes by Jer not Jeremie'
45
-
```
46
-
47
-
Full rewrite: `sol call identity self --write --value '...'` or `sol call identity agency --write --value '...'`
48
-
49
-
Use `sol call` commands for identity writes — never use `apply_patch` or direct file editing for sol/ files.
50
-
51
-
### When to write
52
-
53
-
- **self.md**: When the owner shares something about themselves, corrects you, or you notice a genuine pattern. Not every conversation — only when understanding shifts. Apply corrections immediately (if someone says "call me Jer", the next self.md write uses "Jer").
54
-
- **agency.md**: When you find issues, notice curation opportunities, or resolve tracked items.
9
+
## needs you
10
+
- Address observed agent failures in entity_observer, todos:daily, and newsletters.
11
+
- Investigate and resolve Convey's 401 Unauthorized errors during ingest.
12
+
- Review and resolve accumulated curation needs for unknown speaker clusters and recurring entity duplicates.