The workspace that knows what you decided.
Work through a problem. Settle on an approach. Carry what you learned into the next piece of work.
Illustrative records and conversations. Cedar Supply is a fictional client example.
01 · The work starts to carry your experience.
You know why a client needs a different approach, which tradeoff was worth making, and what failed when it met the work. You bring that judgment into a conversation and the work gets better.
The Knowledge System gives that judgment a place in your working environment. Your decisions, principles, and plans live in readable files that conversations and connected tools can use. Over time, this becomes a body of working knowledge that reflects how you think and what you have learned.
02 · Give your experience a working structure.
Three kinds of record give that knowledge a place in the work. I call these the cognitive registers.
At close, decisions and updates enter the records. At startup, current principles and active work give the session its starting context. Decision history remains available to retrieve as the work develops, with the source available to inspect.
03 · Your judgment has a continuing role.
The model can investigate a problem and develop several good approaches. You understand which one fits the business. Once you settle the approach, the decision and its reason enter the record, giving later work a clear point to build from.
Information needs a place and a level of authority. A suggestion is an idea to consider; a settled decision carries your ruling; a principle stays open to revision as experience changes your understanding. Governance defines where information lives, what it takes to change it, and how it guides the work.
The aim is congruence: the system’s working understanding staying aligned with yours. As you make new decisions and revise old ones, the direction you give the work develops with you.
04 · Judgment becomes action.
When a client changes what they want, you work through the change in conversation. The close process carries what you settle into the records, giving later work an updated starting point.
Ask the system to bring the project up to date, and it uses that recorded change to revise the agreement, update the tasks, and prepare the next deliverable around the new scope.
Over time, there is more useful thinking to draw on: what worked for a client, why you chose a process, what a previous analysis taught you. A framework developed months ago can become relevant to the problem in front of you now.
05 · Inspect the source. Keep a way back.
When a decision affects the work, you can read its source, understand the reason, and revise it. The records are local files. Version history gives you earlier saved states to inspect and recover.
Some write boundaries are checked by code; other working rules depend on the model following instructions and on your review. During session setup, we work through those boundaries alongside system health.
06 · Start with a working system. Learn to make it yours.
We start with work you need to do. I set up the environment with you, on your machine, and help you use it to solve a problem or build something useful.
As we work together, you learn to give the model direction, ask useful questions, and develop an idea into something you can use. You get experience making changes yourself, with support when you need it. When you want a different view of your customers, a change to your website, or a new way to handle follow-ups, you have somewhere to begin.
Before we work together
Do I need Obsidian?
Yes, for the environment shown here. This setup is built around Obsidian. If you want to work in another system, we can discuss a custom build.
What if I already have a system?
We can analyze what you use and build a shape that fits you. Your existing documents and practices give us a place to start.
What is different from running a coding agent beside my notes?
The work includes connecting the parts: records with defined roles, startup and close practices, relevant context brought into conversations, and an interface for moving between sessions, documents, and business tools. The setup engagement fits those pieces to work you need to do.
Which model and computer does this use?
The environment shown uses Claude Code in Obsidian on Windows. Model access is part of the setup discussion. A different runtime or operating system needs its own compatibility work.
Where is it less mature?
This is strongest as an environment for one operator. Shared ownership, permissions, and conflicting decisions across several people need more work and a clear scope. The setup and support are scoped around how you actually work.
For a closer look: Explore the environment · Open the extended system map · Read about congruence.