02 · Cases / 01
SamticsOS
Personal agentic system · in daily use
The agent sorts and drafts. I decide what comes in and what goes out.
The challenge
I work across email, projects, notes, and tools in half a dozen places. My attention went to finding and reshuffling, not thinking. I wanted a system that remembered for me without taking away control.
The approach
I turned my notes vault into my own operating system. Sources are kept untouched, an agent summarizes and links them into a knowledge base, and a dashboard shows what to do today and what each agent is doing. Every task has an agent with a single craft, not one that does everything.
The system
01Input
- Documents
- Notes
02Knowledge base
- Untouched sources
- Summarized, linked pages
03Agent crew
- Orchestrator
- Single-craft agents
- Evaluator
04Dashboard
- What's mine today
- What each agent is doing
05I decide
- Which sources go in
- What gets sent or published
- Which rule stays
The boundary
The agent decides
- Sorting what comes in.
- Summarizing and linking to what I already know.
- Drafting.
- Flagging what is stuck.
- Reviewing other agents' work.
I decide
- Which sources go in.
- Which rules become permanent.
- What gets sent or published.
- Any change of direction. An agent can prepare a commit, but only I push anything to production or in my name.
Every correction I make becomes a written rule the system reads next session.
Result
I start the day with a short list of what's mine to do, not 15 tabs. Answers come from accumulated knowledge instead of from scratch. And I can see what each agent did and undo it.
What I learned
An agent with one craft and a clear rule is cheaper and more reliable than one that "knows everything." And what isn't written down isn't remembered: the rules live in files, not in my head.