The people, what it costs, and the figures. Every row is a join across four kits that no kit may make: the host queries, and console.ts derives. Nothing on this page is an approval, and it cannot grow one by accident — a phase yields a note and never an action, so the only two verbs here are about a code nobody has used.
Everything administration needs is on this page: the people, the waiting list, what the research did, what it costs, and the figures at the bottom. What asks something of you sits with the person it’s about.
A conversation stops when something a person wrote needs somebody here to look at it, or when our safety check couldn’t run twice in a row. While it’s stopped the assistant doesn’t answer, and nothing starts it again except somebody on this page.
What they wrote may be an emergency happening now.
Stopped 16 Sept 2026, 08:47Our safety check couldn’t run on two messages in a row. Nothing is known about what they wrote.
Stopped 16 Sept 2026, 07:14A member asked for a copy of what we keep about them, or for their account to be erased. Nothing here happens by itself: a copy waits for you to prepare it, and an erasure waits thirty days after the mail that tells them the date, and stops if they sign in.
We don’t know whether the reminder to delete circle tomasCircle15 for good was made. Look for it in the workspace; if it isn’t there, delete that circle for good from the Deleted list yourself.
Logins still to remove · 1
What every research did that day, and anything that moved outside expectation. The daily report in your inbox is written from these same figures and says these same sentences: if the message ever differs from this section, the message is the one that’s wrong. Nothing here is worked out a second time.
5 things moved outside expectation yesterday. 6 of 6 researches were running.
Yesterday US$7.36 of US$240.00 in daily budgets was used, across 6 researches.
Somebody asked to buy research credit. Nothing takes their payment for them yet, so this is the one place where a person is waiting on the team rather than on themselves: you arrange the transfer, and you write the credit once it has arrived. When a payment provider is wired this list stops filling by itself.
4 people are waiting on a transfer.
First the money, then the button. Add the credit once the transfer has arrived, not before. Nothing here checks a bank, and nothing here charges anybody.
They pay€100.00
They pay in EUR and research is counted in USD. We hold no exchange rate, so nothing here works the credit out for you: type what you settled the payment for.
It stays with the request. The person sees what you write.
They pay€25.00
They pay in EUR and research is counted in USD. We hold no exchange rate, so nothing here works the credit out for you: type what you settled the payment for.
It stays with the request. The person sees what you write.
This id isn’t in the people table, most likely an account that closed after the request was made. The money is still theirs; find out where it went before you add anything.
They pay€50.00
They pay in EUR and research is counted in USD. We hold no exchange rate, so nothing here works the credit out for you: type what you settled the payment for.
It stays with the request. The person sees what you write.
They pay€75.00
The parts of this charge can’t be worked out from what was stored. The request still stands, and the credit you add is the figure you settled the payment for.
They pay in EUR and research is counted in USD. We hold no exchange rate, so nothing here works the credit out for you: type what you settled the payment for.
It stays with the request. The person sees what you write.
No credit is written and the request closes. Your note is what the person reads, so say what happened to their money.
Per person what today and this month cost, and what on. The daily budget follows that person’s own day: it counts again half an hour before their day starts, it’s theirs to spend during it, and what’s left over is used outside their day for work on the library. You set the total when you make the code; you top it up here, per person, once the transfer has arrived.
What a reviewer asked for is counted in these figures and can’t be shown separately: nothing on a spend row records which reviewer asked. It isn’t zero: it isn’t recorded.
Per person what their research may spend and where it stands. It runs by itself: it rests when there is nothing to do and wakes when they do something. Their research amount is monthly and yours to set; its share of a day is that amount over the month’s days.
Booked today (UTC): US$8.62 · the members’ own budgets allow US$51.00; anything above that is a fault, and you get one mail that day.
Your daily override US$10.00; the members’ budgets need at least US$51.00. Below what the members’ budgets admit: somebody’s research or conversations will be refused before their own limit.
No override set, so the members’ own budgets are the bound (US$1,581.00 today).
Research never takes the last US$1.00 of anybody’s day: that part is kept for their conversations.
Every research team also carries a fixed ceiling of US$50.00 a day, the same for everyone. It only catches a runaway; it can’t be changed here.
Places are made ahead in batches, and the software gives one to each person once they agree their first summary. This says when to make more, and who has waited more than an hour.
2 spare · 4 in use · 1 retired
One place’s key expires within 60 days, or has none yet.
Everything else on this page is about one person. This is the switch that reaches all of them: while it’s on, nobody’s research and nobody’s library can spend anything. It is here because it’s the only place it could be, not because it’s a thing to use.
One switch for everybody at once. While it’s on, no research and nothing in the app can reach a model, for every person and not only the one you were looking at.
Running
Calls are admitted. What stops any one person is their own ceiling and their own credit.
Whoever finds this stopped tomorrow won’t be you. Say enough that they know whether it’s safe to start it again.
The other end of the data requests above: a member asks for a copy, downloads it once the team has prepared it, and asks for their account to be erased. Asking to be erased asks first, and then signs them out on every device, because a sign-in is what stops the erasure.
Your account
A person adds their own key for a supplier, and their conversations run on it. The key is checked once and kept locked away; the panel says which are set and never shows a value. Removing asks first. Taking back a consent asks first too, and names what goes with it: taking back keeping your own AI keys deletes them.
From the code spent to the summary agreed a member is framed by no shell, so the settings tab is out of their reach. The arriving frame links here instead: the page’s title, the card without its own heading, and the way back to where they were.
Nothing yet. Every verb above lands here.