The door to the layer · built 23 Oct 2026 · opens on request
Every product knows what a person did. None knows how she is holding the day. Felt Intelligence answers that one question — in her own word, with her yes, for one named speaker — and tells you how to reply: how many words, how long to wait, when to hold the big decision. A business that reads it can slow down when she is heavy, ask before it answers when she is driven, and make its real offer when she is clear. The intelligence stays hers. You rent the reading, never the person.
Satya · the same loop Aatman stands on · consented reads only · every number on this page carries its date
How it works
The layer holds a clock for each person — a model of how the hours lean for her, built from her birth details once and kept private — and a record only she writes: the word she taps for her state, and how she is holding it, heavy, driven, or clear. The clock is allowed to suggest. Only her word decides. When she has not spoken in a day, the reading says so and sends you a question instead of a verdict. When she has, the reading carries her word, its age, and how far it sits from where the clock expected her.
That order is not politeness; it is what measured. Declared states were confirmed six times in ten; a second guess after a “not quite” recovered nothing in two tries; asking recovered her own word eight times in thirteen (enter, 19–21 Oct 2026). So the API asks.
One of fifteen words on a ladder from Bondage to Enlightenment, with Witness at zero. Hers, tapped. The quality beside it: heavy, driven, clear.
How many words she gave, after how long a pause. Returned as a rule for your next reply: at most one and a half times her words, one question, wait as long as she did.
The next turns in her day: pressure in, an opening, a turn — with the area of life and a strength from one to three. Timing for you. Never a line for her.
The calls · v1
Base: /api/fi/v1 · Authorization: Bearer names the speaker · X-Consent is the token minted when she said yes to that speaker. Missing either, the answer is a refusal. The full contract is openapi.json.
POST /consentMints a token for one person and one speaker. Only the product she said yes inside can mint it. A speaker cannot read a person who consented to a different speaker.
POST /askTwo neighbouring words — “closer to unsettled, or to watching?” — then “heavy, driven, or clear?”. Built from her last word if it is fresh, else from the clock, and labelled which.
POST /tapWrites her word and quality to her record. Returns the move from her last word and the gap between her word and the clock’s expectation — the hold.
GET /readWord, quality, the move since last time, confidence (her fresh word 0.7; the clock alone never above 0.35; both agreeing adds 0.1; never 1), the sources used, and the line that governs every answer: the clock suggested; her word decided.
GET /windowThe next turns with from, to, direction, area and strength. Every window carries spoken_allowed: false. You may time by it. You may not say it to her.
GET /tempoMaximum words, the pause before you speak, her style (clipped, steady, long, flooding) and her pull — toward herself or toward another person. Read before every turn.
GET · POST /missionYour vow in one line, and a check after each decision: held, mostly, not. Returns the held rate. A business without a vow cannot be felt.
GET /pulseHow many of your opted-in people tapped this week, and the shares heavy, driven, clear. Refused below ten people. Never a list, never a name.
POST · DELETE /webhookA push, minutes before one of her windows opens — direction, area, strength. Dies with a dropped key; expires after thirty days.
What it refuses
trusted: false until her own shuffled-minute test says otherwise, person by person. We do not sell certainty we have not measured.What a business does with it
The first integration is our own. Sötbella’s operating intelligence reads its founder — state, tempo, windows — before every turn, with his consent as the first opted-in person. The behaviour it inherited is the behaviour we will ask of every speaker:
One smallest decision. Nothing irreversible. Numbers without verdicts. Shorter replies. Hard calls queued to the next opening.
The risk list before the plan. A twenty-four-hour hold on anything above the daily floor. One question before three answers.
The big call, now, while it can be seen whole.
Ask who before what.
Checked against the vow. Logged as held, mostly, or not.
Where it reaches, once the door opens — each one a design, none yet measured:
A store that slows its checkout when she is heavy and makes its real offer when she is clear; a stylist that asks before it shows.
A session that starts from her word, not a form; a practitioner told how long to wait before speaking.
A hold on the trade placed in a driven hour. A plan reviewed in an opening, not under pressure.
A team’s pulse, in aggregate, so the hard meeting lands in the week’s opening and not its pressure.
A layer any assistant calls before it speaks: her tempo and her state as the first line of its context. It talks less, and waits.
The proof clause
Every integration starts with a thirty-day read on its own people and ends with three numbers it could not have faked: decisions reversed within seventy-two hours, before and after; the share of sessions closed on a “lighter” tap; and her taps against her own shuffled minute — whether the windows beat chance for her at all. The targets we set ourselves on the first integration: reversals down a third, “lighter” at six in ten or more, windows above shuffled. If the three do not move, the key is not renewed, and we say so here with the date.
Status · 24 Oct 2026 · built and tested end to end, fourteen of fourteen calls · deployed: enter.satya.org, 24 Oct 2026 · speakers outside Satya: 0 · integrations in progress: 1 (Sötbella, on its founder) · pricing: set with the first thirty-day proof, not before.
Ask for a key
The door opens to one speaker at a time. Write what the product is, who the people are, and how they would be asked. We write back.