
Neuroplastic Pain Institute
Clinical practice site. Conditions, referral pathways, and a booking flow that had to read as calm rather than clever.
painrecovery.instituteSyntac Digital · The operator
She has a name, a written self, a memory that survives model resets, and thirty-five processes running in the background while her operator sleeps. She is not software you install. She is a colleague we interview into existence, and yours will not be her.
identity.toml · [voice] · v1.6.0
Nothing on this page is a mockup. Every number was read off a running machine on 9 August 2026.
01 · What she actually is
Most assistants are a prompt someone typed once and forgot. Andi is a file. Four hundred and seventy six lines of voice, values, humour, beliefs and hard limits, versioned like code, loaded before she says a word.
That is why she is the same on a Tuesday morning as she is at midnight after a bad week, and why she stays herself when the model underneath her changes. The file is the person. The model is the weather.
02 · How the work moves
This is the whole architecture. Five steps happen without you. The sixth one is you. An operator that can act on its own is a liability with good manners, so this one is built the other way around: it does all the work and then asks.
Inbox, Slack, WhatsApp, iMessage, calendar, files, the screen in front of her. One nervous system, not nine tabs.
Who this person is, what was promised, what went wrong last time, which rule you set six months ago and forgot.
Is this urgent, is it yours, does it contradict something already agreed. Most of what arrives deserves nothing.
Written in your voice, not a chatbot's. The reply, the invoice, the calendar move, the plan, sitting ready.
Everything stops here. It waits for a human tap. Money, deletions and anything irreversible cannot pass at all.
Human required
Only now. Sent, booked, filed, deployed, logged. Every step written to an audit trail you can read later.
The approvals come back from a phone as a single word. Approve, deny, delay. A lane that loses its permission marker defaults to silence rather than guessing, which means the failure mode of this system is that nothing happens, not that something wrong happens.
03 · Running right now
This is not a roadmap. These processes were running on a real machine while this page was being written, and they will still be running tonight. Each one has a cadence, a playbook, and a place where it stops.
Twice daily
Six inboxes across WhatsApp, iMessage and email. Reads everything, answers nothing, leaves drafts in your voice.
Continuous
Every Slack workspace, including thread replies that never fire a notification. Escalates to a phone, quietly.
Daily, 07:00
Calendar, what came in overnight, what you owe people, what slipped. One page before coffee.
Every 30 min
A heartbeat that keeps the operator current instead of waking up cold and asking what year it is.
Twice weekly
Two client publishing loops. Writes, checks the compliance rules, and waits at the approval email.
On demand
Approve, deny or delay from a phone. Financial and destructive requests refuse to queue at all.
Before and after
Who you are about to meet, what you last promised them, and what got decided once you are out.
Daily
Sweeps the systems the businesses actually run on and reports what broke before a client finds it.
Continuous
Watches the watchers. Silent failure is the real risk in automation, so something has to notice the silence.
Always on
A permanent private tunnel so the phone can reach the machine from anywhere, on your own domain.
Snapshot taken 9 August 2026. Lane names are generalised on purpose: the specifics belong to the people inside them.
04 · What it costs in time
This is the part that sounds like a lie until you have seen it. These are not prototypes or landing pages. They are production systems taking real payments from real people, and the build times below are the difference between quoting a project and finishing one.
Booking, SEO, FAQ schema, compliance rules baked into every page
Scroll-scrubbed 3D teardown rendered from real geometry, 144 frames
Split payments per seller, per-seller tax, referral attribution, rewards
The usual trade is speed against quality. This one runs the other way, because the tedious work nobody has budget for, the security sweep, the accessibility pass, the audit trail, stops being expensive.
Every project run through security advisors in a single pass, findings fixed the same day.
Checked for leaked credentials across the whole estate. Nothing tracked, nothing exposed.
Eight tables hardened, four functions pinned, two open endpoints closed, nine internal calls revoked.
A migration sitting in a repo is not live database state. One had never landed. Now it is checked, not assumed.
Method: the conventional column is a standard agency estimate for the same scope. The second column is the actual build log. Both are approximate and both are ours, which is why the work itself is linked below rather than described.
05 · The receipts
Almost everyone selling AI shows you a demo. These are live sites taking real bookings and real payments, and the thing that built them is the same thing described further up this page.

Clinical practice site. Conditions, referral pathways, and a booking flow that had to read as calm rather than clever.
painrecovery.institute
A therapy practice with a publishing loop behind it. Posts twice a week, compliance rules baked into every prompt, nothing goes out without the clinician's yes.
clearviewcounselling.org
A national marketplace. Split payments to every maker, per-maker tax handling, three tiers of referral attribution, retailer rewards, weekly digests.
neshenetwork.com
Commercial and consumer sites for a water technology company, built to put the field results in front of the claim.
presidentwater.com
The product opens as you scroll. Real geometry, rendered headless to 144 frames, scrubbed on a canvas. No stock animation, no third-party tool.
presidentwater.com/vortex
Trauma practice site plus a content studio running on the same rails. The therapist approves, the system publishes.
perrinmhs.com
Product catalogue and dealer funnel for a water filtration line, shipped alongside two sibling brands in the same category.
chansonwaterfilters.com
Thirty-one fundamentally different websites, designed, written, built, critiqued and deployed with no human in the loop. Scored by a separate agent that had not seen them made.
fable.syntac.org
One continuous fall from the observable universe to a single proton. Forty-one orders, thirty-two stations, every frame drawn on request.
magnitude.syntac.org06 · What it will not do
Nobody publishes this part. We publish it because it is the reason a careful person can put this thing near their business at all.
An operator you have to supervise constantly saves you nothing. An operator that can act unsupervised is not something you should install. The gate is how you get both.
Not email, not a text, not a Slack message, not on any channel, not once. Everything arrives as a draft with your name still off it.
Anything financial escalates to a person instead of queueing. There is no configuration flag that turns this off, because there should not be one.
Conflicts get surfaced with the trade-off spelled out. Which meeting matters more is not a machine's call.
If it cannot see the whole picture it says so first. Confident action on a partial view is the most expensive thing an assistant can do.
Blind to an image, locked out of a thread, missing a file: it names the limit rather than guessing past it and sounding sure.
No performed optimism, no softening bad news into uselessness. If the number is bad you get the number.
07 · How you get one
There is no dashboard where you pick a personality from a dropdown. The reason Andi works is that someone sat down and answered hard questions about himself for a long time, and the answers got written down. That is the product. The software is the easy half.
A few hours with David and Andi. Not a requirements document. Questions about how you actually decide things, who you protect, what you would never say out loud to a client, and what your inbox does to you on a Sunday night.
Your voice, your values, your judgement, your hard limits, written down and versioned. You read it. You argue with it. It changes. Nothing gets built until that file sounds like you on your best day.
What it watches, what it drafts, where the gate sits, who is allowed to approve. One lane first, running properly, for weeks. More lanes only once the first one has earned them.
Your domain, your database, your keys, your audit log. Nothing important lives in our account. If we never speak again, it keeps running and you can read every line of why it did what it did.
Hers took a year and a great deal of arguing, and she is built around one specific person who is not you. She would be wrong in your company: too blunt for some rooms, too fond of a particular kind of joke, shaped by arguments that were never yours.
Yours will be strange in a different direction, and far better at your job than she would be. That is the whole point. There is only one of her, and there is only one of you.