Today at work
WORKING Work →5h 12m of 8h 00m target
Arrived07:32
Next punchEnd day
Cycle credit+2h 15m
Kumiko Sign in// a personal operating system
One personal system. Many ways to work.
Kumiko connects tasks, projects, time, knowledge, routines, and automation — without flattening them into one generic tool.
One email, once, when the hosted plan opens. Nothing more, and unsubscribe is in every message.
// the problem
The tools work. The space between them does not.
01
A task loses the outcome it was supposed to serve.
02
A due date ignores the hours you actually have.
03
A note or file arrives with no next action attached.
04
A week in review becomes manual reconstruction.
The cost is not owning many apps. It is rebuilding context at their boundaries — copying, reconciling, and deciding which version is true.
// the thesis
Keep each tool focused. Connect them by contract.
A board is still a board. A document is still a document. A calendar still optimizes for time. What crosses between them is a small, typed capability — never a copy of someone else’s record.
Organize
Outcomes, next actions, and the lists that repeat.
tasks · kanban · projects · listsPlan
Unfinished work placed against the hours that exist.
planning · calendar · workKnow
The reference behind the work, kept where it is used.
docs · files · read later · flashcardsReflect
What happened, without reconstructing it by hand.
home · timeline · metricsversioned commands · queries · facts
Four outcome groups — Organize, Plan, Know, and Reflect — connected by a shared line of versioned commands, queries, and facts.
// one continuous loop
The next action keeps its context.
- 01 Capture an idea
A thought, a file, a receipt — recorded before it needs a shape.
- 02 Turn it into a next action
It joins the record that owns the step — a card, a task, a list item.
- 03 Place it against real time
Planning ranks it; Calendar tells you whether the hours exist.
- 04 Do the work
Time is recorded where the work happens, not typed in afterwards.
- 05 Retain the context
The day keeps its own history, so review is reading rather than rebuilding.
Records do not all become the same type, and nothing has to pass through every step. A list item stays a list item; a document never becomes a task to be useful.
// purpose-built surfaces
Shared language, specialized tools.
// trust
Trust is a product feature.
No silent overwrite. No silent retarget. No silent history rewrite. These are behaviours the system implements, not promises about it.
Self-hosted
Runs on your own machine, with your own backups.
Owner-scoped records
Sharing is a deliberate act; administration is not access.
No silent overwrite
A stale write returns a conflict and keeps your draft.
Modular builds
Unselected modules are absent from the build, not hidden.
Scoped credentials
Integration tokens are narrow and revocable at any time.
Complete backups
The database and the files its rows point to, snapshotted together.
// extend the same system
The interface, REST, OpenAPI, and MCP describe the same Kumiko.
Scopes decide which operations exist at all. An operation your credential cannot reach is absent from discovery rather than refused afterwards — and an automation never sees more than the person who authorised it.
Kumiko keeps the tools distinct — and the work connected.
One email, once, when the hosted plan opens. Nothing more, and unsubscribe is in every message.