Repository navigation
FridayOS: a Six-Brain vault structure for separating sources, tasks and reusable methods #1771
Owen-Teng
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I’m Owen, a contributor to FridayOS. I’m sharing a vault-organization example for people exploring knowledge work with Claudian.
The problem we are working on is keeping an AI-assisted task connected to its sources without mixing raw records, current tasks and reusable knowledge into the same pile of notes.
Our “Six-Brain” structure gives six folders distinct responsibilities:
inbox/: incoming material and ideasexec/: goals, progress and next actionswiki/: reusable knowledge with sourcesskills/: repeatable methodsraw/: original evidencesystem/: explicit rules and authority boundariesA small workflow is: keep three source documents in the evidence area, define a brief in execution, link relevant knowledge, review the output, and only then record a reusable method. The folders provide context; they do not enforce permissions or automatically load instructions into a host.
The public repository includes an offline Markdown blueprint, bilingual guides, and a Chinese fictional Obsidian example vault with 11 practice prompts. Its tool-setup example uses Claudian. I’m sharing the structure and materials here, rather than reporting a fresh end-to-end validation against the latest Claudian release; model access and instruction loading need to be checked in your own setup.
FridayOS repository and example vault · Blueprint deployment guide
I’d value feedback from Claudian users on one specific question: when a task produces a useful new note, what helps you decide whether it belongs in a project’s working context or in shared long-term knowledge?
All reactions