wordspaceHow it works, step by step
Two apps, one loop: the phone captures, the Mac thinks.
There is nothing to configure. What follows is the whole loop, from a sentence caught standing in the street to the wiki that hands it back to you six months later.
The phone captures
Write or dictate a note and put the phone away. It doesn't ask which folder, it doesn't ask for a title: that question comes later, when you have time. The note waits there and heads for the Mac.
On the Mac everything stops in the Inbox
What comes from the phone, the notes you jot down here and the prompts you take from the wiki all stop in the same place. They don't enter the wiki: they wait for you to look at them.
Three decisions, none automatic
For each arrival you decide: make it a note, archive it, or throw it away. Only what you take on enters the wiki — that's the rule that keeps the wiki clean, and nothing bypasses it for you.
You write in Markdown, in blocks
Every paragraph is a block with its own pill: heading, text, list, table, quote. You write Markdown and see formatted text. With the cursor in a paragraph, ⌘1–⌘4 ask the intelligence to correct, rewrite, expand or shorten — and the correction appears INSIDE the text, word by word. You accept it, not it.
The wiki writes itself
As you write, a model running on your Mac rereads your notes and reorganises them by themes and people: your #tags and @names, and the ones it finds on its own. Every page cites the notes it came from: one click and you're on the original.
Searching, and being found
⌘F searches the open note, all the others and the wiki. On the phone the Search tab does the same over what the Mac sent: words, #tags and @people.
And back to the phone
The wiki and the notes written on the Mac come back to the phone to read, even offline. Over there you read and capture; writing and thinking stay on the Mac.
What runs, and where
The intelligence is a model that lives on your Mac: your text never leaves the computer, there is no account and no server. You don't pick a model per task — you pick a profile, a configuration tested as a whole, with the measured numbers in front of you.
The loop in one line
Capture without deciding, decide when you have time, write calmly, and the map of what you wrote builds itself.