Named for the Pharos of Alexandria — the ancient lighthouse
that guided sailors home across the wine-dark seas.
Its name became the word for "lighthouse" across European languages —
phare, faro, farol, far.
Rhymes with Orion.
Part I — The Road to Pharion Started in Roam
Oakland, January 2021
In early 2020 I discovered Roam Research and I felt like someone had finally built a tool that worked the way my mind works. My first thoughts were: where has this been all my life, why has nobody thought of this before, and how did anyone ever organize their thoughts without it?
I promptly paid for the Roam Believer Plan — five years upfront — I bought a little black wool beanie hat with the Roam logo on it — and I went on to co-run several Roam Book Clubs with Matt McKinlay, Beau Haan, and others. I built extensions for my own graph until the extensions had to have extensions of their own.
And then slowly, over years of daily use, I started to understand the shape of what I actually needed — and why I couldn't build it inside someone else's tool. Roam's team had made architectural decisions that would not support the things I wanted to do. The things I wanted to have in my notes app required a different foundation.
So I started over. Five years of living in a block-based outliner turned out to be the best possible preparation for building one. Pharion is the living record of what I learned.
Part II — You Already Know How to Think
Most note-taking tools ask you to organize your thinking before you begin. Pharion assumes you already know how to think — it just tries to stay out of the way while you do. The structure will emerge on its own — the patterns in your thinking are already there, waiting to be found. Pharion will help you find them.
At its core, Pharion is a block-based outliner with daily notes and bidirectional linking. If you've used Roam Research or Logseq, that sentence means something to you. If you haven't, the short version is this: every day starts with a blank page, everything you write is a building block that can be connected to everything else, and those connections are visible from both ends. You link to something; it knows it was linked to.
That's the foundation. But it's not the point.
The point is that your knowledge has a shape over time. You don't just have notes. You have a relationship with certain ideas — ones you return to, annotate, build sequences around, name because they matter enough to name. Most tools treat notes as filing. Pharion treats them more like personal maps of all the territories you're continuously exploring. The maps change as you do.
When I started working on Pharion, I was building for myself. But knowledge is also social — the ideas that matter most are often the ones you first encountered in conversation, or gave to someone who needed them, or had to revise because someone you trusted pushed back. The best thinking doesn't just accumulate in private; it travels, gets tested, returns changed. Pharion now lets it travel. It's possible to share notes with other users who are also using Pharion. A lighthouse is a wonderful thing, but a chain of lighthouses is a navigation route.
Part III — What Makes Pharion Different
A few concepts that are specific to Pharion, worth understanding before you start:
Handles are your personal vocabulary for the things that matter to you. Every line you write is a block — a single thought or idea. A handle is the name you give to a block that matters. It's not a tag, not a page title, but a proper name, bestowed on something that matters to you - *strategic-question or *book-worth-rereading or just *things-I-love. When you assign a handle to something, you can reference it anywhere by that name. It's yours. Nobody else's handles interfere with yours.
Sequences are for when order matters. A sequence is a chain of blocks that belong together in a particular arrangement — a series of essays, a progression of ideas, a narrative arc you're building across days or weeks. You can navigate a sequence with arrow keys, see the whole chain at once, reorder it. Sequences don't care when the blocks were written. They impose your chosen order on time. Zettelkasten practitioners have a name for this: Folgezettel — the idea that a sequence of connected notes can carry an argument further than any single note ever could. It's one of the oldest insights in personal knowledge management. Pharion just makes it easy, no index cards required.
Cards are the annotation layer on top of your notes. They give you space for a layer of commentary - like the marginalia you might write into a physical book that you own. When there is something that needs an aside — a passage, a block someone else wrote, a thing you want to think about in context — you create a card. The card links back to the source and lives in your knowledge graph. It's your note about the thing, not a copy of the thing itself.
Chyrons take their spirit from Ryder Carroll's Bullet Journal practice of logging your day in brief, declarative strokes. One per day, living inside your daily note — less a timestamp, more a headline. A single sentence that captures the shape of the day before you close it. But chyrons are also connective tissue: the threads that hold your calendar together, linking days into weeks, weeks into months, months into years. What started as a log gradually becomes a narrative — and you find yourself reading not a ledger, but a life. They're collapsible and unobtrusive, and most of the time invisible. But they're what turns a pile of daily notes into a life with a shape.
Connections are how your thinking reaches other lighthouses. Every Pharion user has a @handle — their address in the network, chosen at signup, distinct from the block handles described above. To connect with someone, you reach out and they accept or decline. Connections are always bilateral, always chosen. Once connected, you can address a block to them directly — you simply type @theirhandle in any block and that block becomes a message that they can reply to — potentially, the beginning of a conversation. You can also use Blockmail to share any block and its tree of subchildren from your graph: a passage you've been sitting with, an argument that needs another set of eyes, a note that belongs with them as much as it does with you. The recipient sees a frozen snapshot — exactly as it left your graph, not a live window into your lighthouse. They can reply, and they can import what you wrote into their graph - if they choose to. If it turns into a conversation, you'll see the thread woven back to the source block. There are no follower counts, no algorithmic feeds, no surfaces optimised for engagement. Just direct, addressed exchange between people who chose to converse with each other.
None of these concepts require special modes or configuration. You invoke them by writing. ~todo turns a block into an item on a todo list. >> opens a card. You can bestow a *handle-name from a simple menu. The interface stays out of the way.
You'll find these primitives when you arrive — and more as well. A namespace system that lets you attach structured attributes to any name, woven into the graph itself. A contacts system that lets you keep notes on the people who matter to you, whether or not they're Pharion users. All of it awaits your exploration.
I've tried to make Pharion a place where the floor is low enough to begin right away, and the ceiling keeps rising.
One day you'll look up and see only stars.
Part IV — A Network of Lighthouses
The Pharos of Alexandria did not stand alone. Every port had its tower. Every coast had its signal fires. They did not compete for attention — they cooperated across distance, each one sovereign, each one making the others more useful simply by existing. That is the kind of network Pharion is building toward.
Not a platform. Not a feed. A quiet, consent-based mesh of individual lights — each one complete in itself, each one able to reach the others when there is something worth sending. Your graph is private by default and stays that way. Connection is opt-in and mutual. What passes between lighthouses is chosen by the people inside them — a block, a thought, a note that one person decided mattered enough to address to another. The network exists to serve the individuals within it. Not the other way around.
This matters because most social software is designed around the opposite premise. Platforms extract value from connection — they need you to produce content, to accumulate followers, to stay longer than you intended. Pharion has no feeds, no follower counts, no metrics of any kind visible to anyone but you. The architecture forecloses these failure modes structurally, not through moderation policy. There is simply no surface for them to grow on.
What remains is something older and less common: a tool for thinking that can also, when you choose, become a tool for thinking together. The note you send is not a post. The person who receives it is not an audience. It is correspondence — the kind that used to happen by letter, and that we have largely lost to the noise.
What Pharion assumes about you
It assumes you work in daily notes. Every session starts at today's page. That's a gift as much as a constraint — it means there's always a place to begin, and the graph grows naturally around the cycle of your days.
It assumes your knowledge accumulates over time and that you'll want to revisit it. Pharion is not optimized for quick capture and forget. It's optimized for people who write something, come back to it in three months, and want to find the thread.
It assumes you want precision without complexity. The primitives are small. The combinations are large. You don't need to learn a system — you learn a few gestures, and then you use them however your work demands.
What Pharion is not
It's not a project manager. It's not a database. It's not trying to replace your team's wiki. (It may well replace your calendar — I didn't see this coming, but it has already replaced mine.)
It is also, and this was not part of the original plan, a tool for sharing thought with people you choose. Not broadcasting. Not a social network in the extractive sense. Something closer to a very good letter, or a note slipped under a colleague's door. The distinction matters: what you share is chosen, addressed, and received by a person — not an algorithm.
But above all, beyond all the things that it is and is not — Pharion is a thinking tool — specifically, a tool for people who think in writing, whose thinking happens over time, and who want their past thinking to be available to their present self without a lot of ceremony.
If that's you, you're in the right place.
Pharion is currently in private alpha. If you'd like to join, write to me at mattbrockwell@gmail.com and I'll be in touch. Alpha access is limited and goes out personally — I want to know a little about how you think before handing over the keys.
Already have an invite? Sign in here.