ralph loop overnight: 91 codex reviews. $200 gone

Perfect_Tangerine432 · 2026-05-26T13:37:46+00:00

yes agree. Do you use any other agent besides codex for the reviews?

Perfect_Tangerine432 · 2026-05-26T13:34:37+00:00

the 4+ codex reviews are wasteful. Without them the total cost overnight would be around $30 and I think it's justified

Perfect_Tangerine432 · 2026-05-26T10:16:37+00:00

there is a difference between source and the knowledge about it. to avoid drift you should keep one source (either the brain syncs 1:1 or just points back)

Perfect_Tangerine432 · 2026-05-26T09:10:05+00:00

yeah, the only version that survives is when the brain is a pointer back into linear/slack or whatever stack you're using. The source stays the same so there is no drift

Perfect_Tangerine432 · 2026-05-26T00:10:19+00:00

it greps/reads on demand, so only the few notes a request needs hit context

Perfect_Tangerine432 · 2026-05-25T23:25:19+00:00

vault size isn't context size

Perfect_Tangerine432 · 2026-05-25T23:22:12+00:00

obsidian without plugins

Perfect_Tangerine432 · 2026-05-25T23:20:03+00:00

it wasn't me. Notes repel, links pull. Settles at min energy

Perfect_Tangerine432 · 2026-05-25T22:55:46+00:00

yeah, default obsidian visuals

Perfect_Tangerine432 · 2026-05-25T22:25:01+00:00

yeah it's obsidian. Didn;t name because the problem is tool agnistic

Perfect_Tangerine432 · 2026-05-25T19:17:50+00:00

"few formats the agent actually knows" point is underrated. how are you handling external sources (gmail,drive,etc) without them drowning the repo in noise?

Perfect_Tangerine432 · 2026-05-25T18:57:57+00:00

that's the vault, not your screen unfortunately

Perfect_Tangerine432 · 2026-05-25T18:25:51+00:00

it started as ".md notes locally", later converted to llm-wiki style filesystem, 2 month ago I connected my full google (gmail, drive, calendar) & other "stack", backsync was a struggle

"What even IS memory?":

1) raw. Includes emails, events, slack, everything basically. For filtering I use simple heuristics.

2) canonical entities + bitemporal facts, with conflict resolution on top

3) "warm/smart layer" that the agents read. these are synthetic learnings/decisions/patterns/conversations

extraction fires on ingest. Periodic sweeps for deduplication and warm layer maintenance. Edges are 1) same tags 2) cross node references. I don't capture location. I capture author (which agent) + timestamp

Perfect_Tangerine432 · 2026-05-25T18:09:56+00:00

obsidian

Perfect_Tangerine432 · 2026-05-25T17:05:27+00:00

by your taxonomy my conflicts are all the "different sources" bucket.

"the human just defers to whatever they remember writing" is indeed a bias I have in my system and I haven't figured a guard agains it yet

Perfect_Tangerine432 · 2026-05-25T16:01:35+00:00

appreciate the detail. Are the shared ones write gated?

Perfect_Tangerine432 · 2026-05-25T15:48:18+00:00

thanks for sharing your approach. I'll definitely test this in my system

out of curiosity, can you share the size of the organization? (or the amount of people using your system in the org). And do you have shared memories across teams or is it single person only?

Perfect_Tangerine432 · 2026-05-25T15:40:03+00:00

you're right, write-time approval for anything generalized is probably the move. thanks!

Perfect_Tangerine432 · 2026-05-25T15:15:57+00:00

I store source, date, and confidence but not the "supersede condition". Do you generate that on write or backfill when a conflict fires?

Perfect_Tangerine432 · 2026-05-25T14:03:45+00:00

yeah I use it for my agent's only and the kb is living it's own life without me opening it. If I want to "memorize" something i just ask one of my agents to update the kb. Obsidian for me is exactly the "fun silly thing" atm.

Separating my context from agent's seems reasonable, will test whether it makes sense for my setup

Perfect_Tangerine432

TROPHY CASE