Your agent shouldn’t have to guess what “Status” means.
SignalFlow OS is a Notion workspace with a written contract for AI agents — read order, write rules, and a receipts ledger. Every field documents itself, so your agent reads the description instead of your mind.
One-click duplicate. Base: 10 databases, 1 dashboard, 37 demo rows. PRO: 18 databases, 2 dashboards, 59 demo rows. Operating in about 15 minutes.
Not on sale yet. The Founding Circle gets it first, at the founding price.
The problem
Most workspaces were built for one kind of operator.
You now work with two. You, and a handful of agents that can read, write, and act — but only if they can tell a decision from a draft, and a task from a thought.
Hand an agent a normal Notion workspace and it guesses. It writes into the wrong database, invents a status that does not exist, and edits the one page you had verified. You find out later.
The fix is not a better prompt. It is a workspace that states its own rules.
What it is
A contract, a confidence state, and a rhythm.
-
A written contract for agents
Every database has a read order, a write target, and rules about what an agent may change without asking. The Inbox is the default write target, so nothing lands anywhere it should not. The Agent Log is a receipts ledger: what ran, what changed, why.
-
Draft → Reviewed → Locked
Every piece of knowledge carries a confidence state. Draft is thinking. Reviewed has been read by a human. Locked is verified true — and agents never edit Locked without approval. You always know which parts of your own workspace you can trust.
-
A rhythm that compounds
Daily triage, a weekly scorecard, quarterly Rocks. The EOS operating cadence, pre-wired to the task layer so the review actually has something to review.
What’s inside
10 databases in Base. 18 in PRO. Nothing arrives empty.
-
🟢 Base — the personal and knowledge OS
Tasks · Projects · Areas · Domains · Orgs · Habits · Inbox · Collected · Created · Agent Log, under one Command Center.
-
💠 PRO — the business OS on top
Vision & Traction · Rocks · Scorecard · Opportunities · Products · Revenue · Decisions ledger · Validation lab · Agent Roster, under a Business Command Center.
Every database ships with worked example rows, so you can see the shape before you trust it with your own work. Delete them in one pass when you are ready.
Areas, Domains and Orgs are three fields, not one.
- Areas are trust boundaries
- Personal, Family, Work. They decide who can see a thing and where it goes.
- Domains are subjects
- Finance, Health, Learning. They decide how things group.
- Orgs sit under Work
- Which employer or client a thing belongs to.
Most systems collapse these into one “category” field, then wonder why a private note about an employer ends up in the employer’s workspace. Keeping them separate is the whole point.
Upgrade without disruption
Buy Base now. Add PRO later. Nothing moves.
The database core is stable by design: every database keeps its name, its fields, and its address across versions — so your data, and your agents’ integrations, do not break.
Dashboards and guides are replaceable skins around that core. Adding PRO drops a section in beside your existing data: Rocks relate into the Projects you already have, Revenue rolls up into new Products, and nothing you built moves. Deleting PRO from a Base workspace breaks nothing either — the dependency runs strictly PRO → Base, never the other way.
Founding Circle
Something else is being built.
SignalFlow OS is the system. The next piece is the front door: a capture app that takes what you said, shows you how it was classified, and sends it where it belongs — with a receipt for every destination.
It is not finished, it does not have a name yet, and there is no date. The Founding Circle gets the build notes as it ships, founding pricing when it does, and the occasional question about what to build next.
Questions
-
Do I need to know EOS or Traction to use this?
No. The Base tier has no EOS machinery in it at all — it is a personal and knowledge OS. PRO adds Rocks and the Scorecard if you want that cadence, and the Start Here guide explains it in a page.
-
Which AI agents does this work with?
Any agent that can read and write Notion — Claude, ChatGPT, Notion's own AI, or something you wired yourself. The contract is written into the workspace as field descriptions and guide pages, not as code, so nothing depends on a particular vendor.
-
What happens when SignalFlow OS updates?
Database names, fields and addresses stay stable, so updates replace the guide and dashboard pages rather than your data. You choose whether to take them.
-
Is my data locked in?
It is a Notion workspace. Export it, duplicate it, or walk away with it whenever you like.
-
Base or PRO?
Base if you are organising your own work and knowledge. PRO if you are running a business with goals, revenue and decisions you need to see in one place. You can start at Base — adding PRO later moves nothing.
SignalFlow OS is built by Janbery, a one-person studio in Los Angeles. The build notes live on the blog.