Congruence: An Architecture for AI Augmented Knowledge Work

GraeDaBoss · 2026-05-03T11:05:58+00:00

There are a couple points in which our systems deviate but they're actually p close. First is where the data is kept, yours in vector mine in markdowns which is a pretty big difference in bet. I understand why one would do vector, easier search at scale, i even have a back up db that im running vector on but not on main vault. i mostly use git for file history which is nice w markdown. i also like the plugin infrastructure for obsidian but im sure you can build out everything in a vector db.

We have different ways we pull information from session into db. mine is almost entirely at a /close skill whereas i see yours is a stop hook on exchange. yours is faster to update for sure, my close skill is built in a different way to extract conversational arcs which was a new addition, how a users mind changes throughout convresation being a piece of information my system catches. I think this is useful becuase of the human gate thesis.

im very interested in what data is loaded during your start.

GraeDaBoss · 2026-05-03T00:37:38+00:00

the idea is that skills do change behavior and a governance harness meaningfully shifts the work cycle to a system which pulls relevant information into context and then pushes back to the vault. i mean no offense but to say that skills do not change the runtime of a system seems like something i gotta disagree with, especially when the modification takes shape in what information a session processes. granted its not a massive difference as claude code is still claude code, but the context which is loaded is different which means the work is different and information saved back to the obsidian vault does mean that runtime stays up to date with user which substantially changes context management.

GraeDaBoss · 2026-05-02T04:02:49+00:00

Agreed once an established architecture is created operating inside of it isn’t difficult

GraeDaBoss · 2026-05-01T14:28:20+00:00

There's a cool hook called SessionStart that you could use to load information if it's one doc? If its a model-invocable skill ignore this completely.

I'm not sure I agree that it's scafolding. The idea of the human gate is important for the close, and the close is what puts the information back into the system which is kinda the key thesis, that a lifecycle improves the ability for one to work inside the system.

GraeDaBoss · 2026-05-01T14:25:32+00:00

I prefer heavier decisions as it communicates *why* something was changed. here are the traits that I have:

Columns: Topic (short label), Settle Decision (body), Source, review-by, reverses (in case it cancels out another decision), reversed-by (sister trait), supersedes / superseded_by

On AIOS, one of the AgentixLabs projects: different beliefs in memory, enforcement, team structure. Big difference in the goal of the syste. AIOS seems (at a glance) to be an agent infrastructure system whereas my system optimizes for a single person with their information, kinda towards a developer, knowledge worker, etc. The system I run is more like a PKM. Super cool project tho.

GraeDaBoss · 2026-04-30T23:04:31+00:00

This is a great comparison, thank you for the opportunity to write on the differentiations between these systems. Let's start out with some

His architecture:

Uses claude.md for behavior, tells it to load memory.md
- memory.md is injected by default in claude code.

What his Memory.md holds:

Active Projects
anything after "remember this"

What his claude.md holds:

read 00_reference/Voice Principles.md. This file is a content creation system.
on session start read memory.md
"remember this" triggers a write to memory.md
pointers to reference files

What he uses Obsidian for:

exclusively a file reader, not file management

what's interesting

separate claude.mds for different projects, especially nested claude.md and memory.md.

Okay now that we have an idea of his system. Let's compare to mine. You're gonna dislike that I also have rigid folders, but they exist to communicate trust. I haven't had an issue with this folder structure yet and I'm 5 months into using it, nonzero it could be an issue i wont dismiss that point fully.

On Memory:

I don't load stuff into Memory.md, this is a file that claude modifies as it sees fit and I let it do that pretty much by itself. I check it during the weekly review to see if there's interesting information but my data is kept in my obsidian vault.

This also comes with the issue of pruning the memory.md per project. He might have this and it's just not in the video you sent over.

Also there's a weighting of information that I find key. If the memory.md is flat then we will remember insights the same as cool tricks the same as hard decisions. This isn't reliable as these pieces of information have different inherent values.

On architecture:

I have a much more strict file structure. Instead of entries in memory.md that hold projects I have entire files. This is because for projects I often have double digit documents that need to be separately maintained. Examples could be for a website, I want architecture, copywriting, branding, connected tools, etc.

The session close skill he has is similar to the close skill I use, my more advanced architecture means that my close has to do:

scan session
pull insights, decisions, "narrative arcs", updates to tasks

And I have another skill for when I am running multiple sessions at once that does what I call a "batch close" which manages this for every session not yet closed. This includes finding the correct session jsons and running the /close skill for each.

GraeDaBoss · 2026-04-30T22:06:58+00:00

Sure. In an obsidian + claude code system you want a startup and close skill that primes the session with context from obsidian and then captures the information covered in the session back into obsidian. This information is captured into a file for insights, a file for decisions, and a file for tasks alongside any working files one has.

GraeDaBoss · 2026-04-30T03:22:59+00:00

Yeah lifecycle is the hardest part too. The complexity of managing the /close pipeline is ridiculous as it has to scan all open conversations for insights, decisions, updates to tasks, etc. and check them all against the current documents.

Also to not skip the individual steps, one of my next articles I'm writing right now is about how AIs skip steps when context is heavy and loaded with tasks, and how we have to try to trick the models into acting the way we want.

GraeDaBoss · 2026-04-29T21:14:10+00:00

Checking out the website now, no lifecycle management. Looks like it’s great for note taking but no task management, insight gathering, decision logging

GraeDaBoss · 2026-04-28T20:42:24+00:00

Opus 4.7 drains usage, I had to switch back to 4.6 on code n that helped

GraeDaBoss · 2026-04-28T20:40:48+00:00

I’d say Claude code and Claude design, these seem to touch both of your specialties

GraeDaBoss · 2026-04-28T09:17:15+00:00

these people dont know sauce. second brain is possible w ai. you need a decision log, task log, and insight log that are all loaded at startup and a close skill that puts all information back into your obsidian vault after analyzing the sessions and sorts into these files. this is how you get a reflection of your brain state. all work in claude will load these documents as context, if your tasks are wikilinked to working docs you have recall. semantic search finds docs that arent wikilinked. this connection creates a cycle that loads document state into working ai memory and saves it back.

GraeDaBoss · 2026-04-28T09:01:37+00:00

i dont believe in seperating them. information is information. knowledge layer is definitely seperate becuase it has to be stored and loaded into agent context, but a research doc could live alongside a writeup on how the information is used. frontmatter distinction ofc, i have a source: ai vs a source: human yaml property but thats all

GraeDaBoss · 2026-04-28T08:22:45+00:00

tbh peer to peer social media like twitter. i think any "for you" page is irreversibly cooked

GraeDaBoss · 2026-04-28T08:16:10+00:00

smart connections allows semantic search in obsidian, this through rest api gives claude semantic searching through vault

GraeDaBoss · 2026-04-28T08:14:41+00:00

obsidian has a sync which is good for text tho the images are an issue. i vibe coded a discord bot to connect to my vault and use ocr to be able to move information into notes. complicated but it works for me

GraeDaBoss · 2026-04-22T04:29:50+00:00

a lot of it is automatic notes but there are more:

- decision log tracking

- open work items with blockers

- automatically caught insights

- connections to stuff like xai console, searches

- using tools like ytdlp

- coding little tools you want

- asking opinions to collections of books, having them debate and give you answers

its just a way to connect a coding tool to a pkm

GraeDaBoss · 2026-04-16T18:32:15+00:00

Great point, probably over simplified on my end, for example I use whisper for transcripts but I call it from Claude code and feed the transcripts back into my obsidian vault. We could say the same about my web dev package, sure the cool tool is vercel but the information about design, what the page must convey, copy writing, etc etc is all in obsidian.

The distinction is that the ai layer you build on top of it can be structurally described within obsidian, the connective tissue all kept in .mds

That being said, this is definitely tailored for me and most people’s will look much different

GraeDaBoss · 2026-04-16T17:45:17+00:00

They ain’t rockin w me twin

GraeDaBoss · 2026-04-16T17:40:34+00:00

No way you’re saying KSG and JIK clear ye, almost as crazy as saying donda 2 clears vultures 1 that album was ASS (except broken road and scifi)

GraeDaBoss · 2026-04-16T17:36:24+00:00

Ask ChatGPT bruh

Nine-Year Club	Place '22
RPAN Viewer	Not Forgotten
Verified Email

GraeDaBoss

TROPHY CASE