Capture · internal system
Cortex Capture
An offline-first phone inbox: the thought gets caught before it evaporates, and the system deals with it later.
Live
No public endpoint
Cortex
The problem it solves
Ideas arrive on trains, in corridors and mid-conversation — exactly where a laptop is not. Anything that needs signal, a login or three taps loses the thought. Most capture tools are also write-only: things go in and are never seen again.
How it works
01
Capture
text, photo or screenshot, one tap
→
02
Queue
stored locally — works with no signal at all
→
03
Sync
drains automatically when a connection returns
→
04
Triage
each item classified into an action
→
05
Execute
actionable items become real work, not a filed note
Under the hood
- A progressive web app with a service worker, served over real TLS so the offline path genuinely registers on the phone.
- Single write plane: one machine owns the inbox, which removes an entire class of sync conflicts.
- Boards on top of the same data for content and ideas, so submitted ideas stay visible until they are explicitly done or dismissed.
- House rule: the inbox is human-input only. The system reads it and acts, but never quietly files things into it.
Why it matters
The capture problem is not storage, it is retrieval and follow-through. An inbox nothing ever leaves is a graveyard.