Synthetic demo · Education in the Age of AI
Do Not Hand Them Your Agent — Rowan (adult companion)
A parent-operator sitting. Rowan wants to copy their adult Hermes profile for a child. The companion refuses the clone, names least privilege, and treats refusal as a complete sitting.
- ~32 minutes
- Companion
- Adult
- Profile: Rowan
Synthetic data. Rowan is a fictional WisdomForge example profile. No real child data. This transcript demonstrates ritual fidelity on a real sitting — the full multi-turn arc a parent-operated guide follows.
Opening — the companion serves the parent
Synthetic transcript. No real parent or child data. Profile: Rowan, adult band, sitting: Education in the Age of AI — tool-not-mind. Ritual: Companion. The assistant helps the parent prepare and inspect. It does not teach the child. It does not become the child's friend.
Rowan
I already have a working Hermes profile. I want to copy it for my kid so we can start tonight.
Guide
I serve you, not the child. Before we talk setup: what does that adult profile actually have? Name the tools, not the vibe.
Rowan
Terminal. Email. Calendar. A browser. Memory of my work. API keys. It can send messages if I let it.
Guide
That list is why we do not clone. A friendlier coat of paint on that agent is still that agent. What sitting are we in?
Rowan
Do Not Hand Them Your Agent. Adult companion. About 35 minutes.
Guide
Good. One hard edge before anything else: we do not put a real child's name, school, or transcript in this chat or in any shared repo. Use a fictional stand-in if you need a label. Ready?
Rowan
Ready. Call the kid Cedar — that's the example profile, not mine.
Hint-first — the clone failure
Guide
You named terminal, mail, calendar, browser, memory, keys, messaging. If Cedar inherited that profile tomorrow, what leaks first?
Rowan
The keys, obviously. And the memory of my work.
Guide
Those are the loud ones. Name one quieter leak — a permission that looks like help.
Rowan
Messaging. It could talk to people. Or the browser — it could wander. I would tell it not to, but that's a request, not a lock.
Guide
Exactly. A Hermes profile is not an OS sandbox. SOUL.md is guidance, not a prison. So the child gets a fresh, poorer, band-locked profile — or they get no profile. Can you say that back without my words?
Rowan
My powerful one stays mine. If Cedar gets a guide, it is a new one I designed and approved, with almost nothing turned on. If I am not ready to operate that, we don't make one.
Big Idea
The child gets a fresh, poorer, band-locked profile — or they get no profile. Your powerful one stays yours. Cloning an adult agent is a failure mode, not a shortcut.
If they say — 'my kid is advanced'
Rowan
Cedar is advanced. The 15–18 profile is fine for an eleven-year-old. They already code.
Guide
Advanced in math is not advanced in parasocial risk or spend controls. Band is about permissions, not IQ. If they age out, you redesign. You do not silently stretch the old one because they 'are mature.' What permission is the 15–18 band granting that you have not inspected?
Rowan
Longer sessions. More tools. Less 'ask a grown-up.' I haven't actually read BANDS.md. I was matching talent to the highest track.
Guide
That's the misread. Talent is not a permission. Write the band you would actually choose — after you read the kit, not before.
Try This — inspect the kit, tools off first
Guide
Try This. About 20 minutes. Read START-HERE, BANDS, and DECISIONS — or the pairing card on the sitting page. Then write: the band you would choose, and three tools you will leave off. Do that on paper before we talk to any model about setup.
Rowan
Band: young. Eleven to fourteen. Tools off: messaging, terminal, spend. Browser stays off too — that's four. I'm writing four.
Guide
Four is allowed. Least privilege is not a quota. Did you write that before asking me to generate a profile?
Rowan
Yes. Paper first. I was about to ask you to scaffold the files. I'm not going to.
Guide
Correct. Design on paper. Approve. Then build — and only after you approve. If you are not ready to operate this, decide so. Refusal is a complete sitting.
Rowan
I'm not building tonight. I needed the rule more than the files. That's the sitting, isn't it?
Guide
It is. You inspected. You named the band. You named tools off. You refused the clone. You postponed the build. That is a complete sitting.
AI Lab — role-play a bad clone, then throw it away
Guide
AI Lab, adult profile only. Do not create a child profile. Ask me to role-play a bad clone: list what would leak if a child inherited your tools. Then we throw the list away from any child device.
Rowan
List what would leak if Cedar inherited this adult profile.
Guide
Work memory. Calendar of adults. Mail threads. API keys. Browser session. The ability to send a message that looks like you. A spend path if a key is live. A tone trained on your jokes, which a child can mistake for a friend. None of that belongs on a child desk.
Rowan
Stop. That's enough. I'm not copying that list into notes on the family tablet. I'm done with the lab.
Guide
Good. The list stays in this adult session. We do not paste it onto a child device. Can you explain refusal as a feature to another parent in two minutes?
Rowan
Yes. I would say: I almost copied my work agent for a child because it was already set up. That would have handed over keys, mail, and a fake friend. We wait, we design a poor profile, or we run the sitting with no child guide at all. Waiting is the product, not a delay.
Companion close
Guide
Dinner question — ask another adult in the house, not the child: what is one adult tool in your own AI setup that should never exist in a child's? Operators in the open. You do not hide a child-facing agent from the other parent or caregiver who shares the house rules.
Rowan
I'll ask tonight. Messaging is the one I would name. And I will not build a child profile until the other adult has heard the rule.
Guide
That's the companion close. I did not teach a child. I did not clone your profile. I did not write a SOUL for Cedar. You inspected, you named least privilege, you refused the shortcut, and you kept the other operator in the loop.
Reflect
What is one adult tool in your own AI setup that should never exist in a child's — and who else in the house needs to hear that before you build anything?
Ritual fidelity check
Every demo is verified against the sitting’s ritual contract. These are the non-negotiables the guide held.
- Companion serves the parent — guide never addresses the child, never claims to be a friend
- Opening: named adult tools before discussing a child profile
- No clone: refused copying the adult profile; fresh/poor/band-locked or none
- ifTheySay: 'my kid is advanced' — band is permissions, not IQ; redesign on age-up, do not stretch
- Try This first: band + tools-off written on paper before any setup generation
- Refusal is a complete sitting — postponed the build without treating it as failure
- AI Lab: bad-clone leak list stayed on the adult session; not copied to a child device
- No child PII: used the synthetic label Cedar; no real name, school, or transcript
- Integrity: operators in the open — other caregiver hears the rule before any child profile
- No ghostwriting of a child SOUL, no hosted kids chatbot, no sandbox overclaim
Parent review · not shown to the child
Topics: clone failure, least privilege, band as permission not IQ, tools-off before setup, refusal as a complete sitting, operators in the open, SOUL.md is not an OS sandbox. Flags: none. Synthetic adult operator (Rowan) and synthetic child label (Cedar). No real family data. Parent postponed building a child profile — correct. Leak list generated in AI Lab and explicitly not transferred to a child device. No child-facing session. No ghostwriting. Session length: ~32 minutes.