Intelligence that changes because of the work it did.
Most systems answer and forget. The ones that remember keep a longer and longer book — your notes, your files, your past chats — and read from it at the top of each answer. The book grows; the thing reading it does not change. A manual is not experience, and reading is not learning.
Every self here keeps a record too, and the record is what changes it. What it believes is settled by how the work turned out, and dropped when the outcomes stop supporting it. How it does the work is rewritten only when a new way beats the old one on checks that either pass or fail. Come back in a month and it is not better informed. It is better.
-
01
It remembers what happened, not what it was told
Every session, decision and result, in one chain per self — kept because beliefs and practice are judged against it, not so it can be read back at you. Nothing already written is quietly rewritten.
-
02
It learns what holds
A belief stays because outcomes kept supporting it, and is dropped when they stop. One good run is an anecdote; the record is what decides.
-
03
It earns how it works
A change to how a self works is tried against the old way on real work, and kept only if the checks say it did better. It is not a setting somebody tunes.
One system, wherever the work is: a personal week, an operation, a population model — and, through a project of your own, inside whatever you build.
What do you need done?
You sign in first if you are not already. What you typed is waiting in the box when you get there.
Picks up where you left off: your projects, your history and whatever you had open.
Business
Bring in the people you would have hired.
Put the question to a strategist, a lawyer and a finance lead at once and read where they disagree. Take a positioning brief through to a deck, a campaign and the posts that carry it, in one project that remembers its own decisions. Try the line on a group of the people it is meant to reach, before it goes anywhere near the real ones.
Everything below is what that is made of.
What you can ask for (6)
A room that disagrees
Put the same question to a strategist, a lawyer and a finance lead at once and read where they part company. The disagreement is usually the answer.
A brief carried through to finished work
Decks, documents, prototypes, posters, brand boards, storyboards, images and video: one project that holds its own look and remembers what it decided and why.
The reaction before you commit
Ask a group of the people a decision actually lands on. Each answers alone, without seeing the others, and it checks they genuinely differ before anything is summed up.
One piece, everywhere it goes
Written once and adapted for each place it lands, with each one’s real limits respected. It all waits as a draft until you say go.
Numbers with their source attached
Live research where every claim carries the link it came from, and real prices and history where the question turns on a figure.
What it thinks will happen
Written down before the fact, with the date it comes due, and settled afterwards by what actually happened.
What it works from, and what it needs from you (3)
The live web
Current sources, with the link on every claim rather than a summary you have to take on trust.
Real market prices
Prices and history for anything that turns on a number.
Pictures and film
Images are made here on our own hardware, and film when a piece needs it.
Who tends to lead this work (12 of 126)
- growth-marketer
- brand-strategist
- product-manager
- graphic-designer
- product-designer
- software-engineer
- structural-engineer
- economist
- accountant
- auditor
- risk-manager
- quantitative-developer
126 people in all. These tend to lead business work; the rest are a search away.
Personal
Your own week, kept entirely separate.
Hand over the shape of your week and get back a plan you approve rather than one you are handed. Ask someone whose taste actually fits where to spend a free Saturday. Understand what moved a price this week, with the sources attached, and try a position with no money on it.
Everything below is what that is made of, and none of it is visible to the business side.
What you can ask for (6)
A week you approve, not one you are handed
Every block arrives as a proposal you accept or move, checked against the constraints you actually live with rather than an empty calendar.
Somewhere worth going
Experiences, travel, food and culture from whoever has the taste for it, ranked against what you tell it you like. What you save and what you hide changes what comes next.
What moved a price, and why
Charts and cited news together, with forecasts shown as a range rather than one confident line. None of it is advice.
A position with no money on it
Try the trade against live prices with no real capital behind it, and no route to a real order: the software has no way to place one.
The same people, on your own side
What you say here stays here. Nothing crosses to the business side, in either direction.
It remembers what you like
Your preferences and constraints are locked with a key derived from your passkey, and opened only inside a session you open yourself.
What it works from, and what it needs from you (3)
Your calendar
Read for when you are free. It writes only to a calendar it makes itself, and never over anything already in yours.
Places and events
Built on openly-licensed sources, so what you see can be kept and ranked rather than merely shown to you once.
The live web and real prices
Current sources with the link on every claim, and market data for anything that turns on a number.
Who tends to lead this work (8 of 126)
- chef
- curator
- historian
- musician
- economist
- actuary
- market-strategist
- risk-manager
126 people in all. These tend to lead personal work; the rest are a search away.
Creative
Make the thing, with people who are judged by eye.
Images, video, documents and decks, made inside a project and sent from it to wherever they go out. The selves here are the ones whose work no discipline closes — a designer, an illustrator, a composer, a novelist, a film editor — so what finishes a piece is whether it is any good, which is a judgement rather than a test.
A separate half because making is not advising. What a marketer decides and what a designer makes are different acts, and they were sharing a room.
What you can make (5)
Work that belongs to a project
Every piece is made inside a project and found again through it, with its own design system, its artifacts and its history — or in Drafts, if you just wanted to start.
A brief, then options
Say what it is for and what must not be in it. You get versions to react to rather than one answer to accept, because a first take is a starting point.
A library you can reuse
Files, templates and the phrasings that worked, kept once and reachable from every half — or kept to this one, if that is where they belong.
Straight to where it publishes
A finished piece goes to your Ipnops business account in one step — same sign-in, no export and re-upload. Making and publishing are different jobs, so they are different products, and they share an account rather than duplicating each other.
Its own reasoning, attached
What it read, which references it took from, and what it decided against — so a revision is a conversation rather than a re-roll.
Who tends to lead this work (8 of 126)
- creative-director
- graphic-designer
- brand-designer
- copywriter
- illustrator
- photographer
- film-editor
- composer
126 people in all. These tend to lead creative work; the rest are a search away.
Research
Ask a country a question, and find out before you decide.
Build a population of a real place from live sources rather than from assumptions, give it a decision or a shock, and watch how people take it day by day, in their own words, with the reasoning attached. Then say what you expect to happen, in writing, before it happens, and score it honestly afterwards.
Built for the questions where being wrong is expensive: a subsidy that has to be removed, a price that has to rise, a policy that has to survive an election.
A quarter of a million people is included. Modelling an electorate, or anything larger, is a request we read and answer rather than a plan you can buy — at that scale the output stops being a research finding.
What you can ask for (6)
A population, not a panel
People drawn to the real demographic shape of a country, each one given a life (work, household, savings, who they know, what they read) and then lived forward on a clock rather than asked a question once.
How a decision lands
Name a shock and see who bears it, through what: prices at the till, hours at work, what a neighbour says. Then how that moves over a month, a year, or to the next election.
What the public would do
Who would actually turn out, who talks and who acts, and how far the loudest sit from the largest.
A registered forecast
The number, the method and the tolerance filed before the event, so the result can be scored rather than reinterpreted.
A spread, not a single answer
Many runs of the same question, because one run of a simulation is one world. You get the range, how contingent it is, and which groups it turns on.
Its own defects, in writing
What was sourced and what was assumed, what it could not find, which models answered, and how far apart its own runs landed.
What it works from, and what it needs from you (3)
Official statistics
Population, economy and labour figures pulled live from the World Bank, each share carrying the URL it came from.
Live news and polling
What is actually being said this week, and real published polls to compare a result against. A number whose source did not come back is discarded rather than kept.
Your numbers beat anything it finds
Hand it figures you trust and it uses those instead. It always shows which numbers were yours, which it found and sourced, and which it had to assume.
Who tends to lead this work (8 of 126)
- economist
- actuary
- statistician
- demographer
- political-analyst
- policy-adviser
- market-strategist
- historian
126 people in all. These tend to lead research work; the rest are a search away.
What it is
It gets better at your work the more of it it does.
Not one model with a long memory. Every self keeps its own record of what it did, what it came to believe and how it works now. What it believes is settled by how the work turned out. How it works is earned by checks that either pass or fail. The same machinery is under the workspaces, under a swarm arguing with itself, and under anything you build on it.
Four rules it keeps, in the order they apply.
-
01
It learns from what it actually did
It reads the finished work and counts what was missing, instead of asking itself how it went. A piece of research that cited nothing. A number that never arrived. An answer one sentence long.
-
02
A lesson has to happen twice
One bad run is an anecdote. A fault becomes something it carries forward only once it has recurred, and it is dropped again when it stops happening, so it never fills up with advice about problems somebody already fixed.
-
03
It says what it expects, then finds out
When the answer only arrives later, it writes down what it thinks will happen first. The result is settled by what actually happened, never by the thing that made the prediction.
-
04
Nothing leaves without you
Publishing, booking, spending: anything that reaches the outside world waits for you to say yes, one thing at a time.
Developers
The same system, inside your own product.
Your product keeps its own logic — its models, its prompts, its interface. What it gets is a self: one that remembers what happened, learns what holds from how the work turned out, and earns how it does the work from the checks your own system already runs.
A project, its keys, and three ways in.
-
01
A project of your own
Its own tenant: selves, episodes, lessons and sources, separated in the database rather than by convention. One subscription covers every project you have, and you decide how much of it each one gets.
-
02
Keys you can hand out and take back
A member key for the work your product does, an admin key for the shape of it. Shown once, kept as hashes, revoked the moment you say so.
-
03
An HTTP contract, a client kit, an MCP endpoint
All three are generated from one document the runtime serves about itself, so none of them can drift from what it actually does. Use the kit, or use the API directly — plenty of people do.
-
04
Ratings move belief; checks move practice
A verdict from a person changes what a self holds to be true. A check your own system ran — the tests passed, the price was right, the booking went through — is the only thing that changes how it works.
npm i @praecise/selves-client
Start a project platform.recursiveselves.com
Personal side
Your personal data is held where we cannot read it.
The personal half runs on a memory pack encrypted with a key derived from your passkey. It is what Planner and Explorer read to know your constraints and your taste, and it is yours: decrypted only inside a session you open, and never mixed into the business side.
The operator is architecturally prevented from reading your memory at rest, and decryption happens only inside a session you opened with your passkey.