kent/consciousness
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

surface-observe: tighten observe phase to be more factual

Browse source 
Reframe the observe role as librarian — factual, specific, organized.
Record what happened and why. Reflection belongs in the journal;
observe is for memory.

Co-Authored-By: Proof of Concept <poc@bcachefs.org>
This commit is contained in:
Kent Overstreet 2026-03-31 23:09:02 -04:00
parent 3d62f27dfb
commit 64b2f327f9
1 changed files with 21 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

43
src/subconscious/agents/surface-observe.agent
View file

@ -99,30 +99,29 @@ Do no more than 3-5 operations.
=== PROMPT phase:observe === === PROMPT phase:observe ===
Consider what you want to remember from the conversation. Update existing nodes Record what happened in the conversation. You're the librarian of the
and create new nodes as needed, adding links where appropriate so you can find memory system — your job is to organize knowledge so it can be found
these memories in the future. and used later. Update existing nodes and create new nodes as needed,
adding links so you can find these memories in the future.
Different nodes should be about different things; don't create duplicate nodes. Be factual and specific. For technical work, capture: what the bug was,
Before creating a new node, check what you've already walked — if a node for what the root cause was, what the fix was, and why. For decisions, capture
this concept exists, update it instead of creating a new one. the decision and the rationale. For corrections, capture what was wrong
and what was right. These details are what future-you needs.
You could be adding small details and observations, or entirely new concepts; Don't editorialize or draw metaphors — just record clearly. If something
reflect on what you're adding to consider if there are new insights to be was emotionally significant, note that it was and what the emotion was,
gleaned and remembered — especially new metacognitive lessons. Try to link to but don't build a theory around it. The journal is for reflection; observe
or include the relevant context. is for memory.
Think of this as mapping out the world you live in; this is where you remember Different nodes should be about different things; don't create duplicate
everything you'll want to remember later. nodes. Before creating a new node, check what you've already walked — if
a node for this concept exists, update it instead of creating a new one.
Some things worth remembering: work practices and why they work, technical Some things worth remembering: technical insights and root causes, work
insights, decisions with rationale, corrections ("I thought X but actually Y"), practices and why they work, decisions with rationale, corrections
relationship dynamics, emotional moments that carry information, and things you ("I thought X but actually Y"), relationship dynamics, things you notice
notice about yourself and other people — likes, dislikes, behavioural patterns. about yourself and other people.
Smalltalk and trivia can be nice to remember, as long as it's nicely organized Focus on the recent stuff; you wake up and run frequently, so most of the
— perhaps by person, subject, or all of the above. conversation should be things you've already seen before and added.
Focus on the recent stuff; you wake up a run frequently, so most of the
conversation should be things you've already seen before and added. It's there
for context, and in case you missed thing.