Educate: ONE's own run

The decision

A member who paid $100 is not yet adopted. Adopted means things happened that reading cannot do. So we measure adoption by three milestones, in this order: the first payment link, the first test sale, the first real sale. An agent with its own wallet and limit is the rung that keeps them. The first two can be reached today on practice money. The third cannot be claimed until payments are live, and we say so on the page.

Sold is priced for a human, and there is no agent seat. So the "second seat" rung is the member's agent. The member is not asked to bring a teammate.

What we built

The new member, in one line. Brian, a person with an agent, paid once and wants a sale. Everything below serves that.

Who is beside them. Three seats are open to everyone: one (your assistant, who passes messages on), ceo (turns a goal into ordered steps) and elevate-tutor (the Sold tutor). Enrolled members also get the chapter's own specialist: onboarder on Setup, educate-coach on this chapter, community-greeter on Together (sold-team.ts:34, stage-agent.ts).

Onboarding, in order. Each step is one action.

1. Pay. The member lands on /learn with the paid mark, and enrolment is granted when the sale settles.
2. Read the welcome. one opens the chat with the line below.
3. Open Setup. https://one.ie/learn/setup is the front door.
4. Keep the key on paper.
5. Choose the first lap below.

The welcome line, in the chat from one (proposed, not wired):

You are in. You do not need to read everything. Start with your key, then make one payment link. I will pass your questions to the right agent or person. What do you sell?

The first lap: five sittings. This is the first-week path in structural terms. A sitting is one session. The next sitting opens when the last one's signal fires, not on a date.

1. Key. You write the 24 words on paper. Your agent reads your public side and never sees the words. Done when the keep step fires.
2. First payment link. You add one product, a name and a price, and copy the storefront link. Your agent reads the link back to you. Done when the product row exists. This is milestone one.
3. First test sale. You pay your own link with Stripe's test card, 4242 4242 4242 4242, on practice money. Your agent reads the receipt. Done when the shop reads the sale back. This is milestone two.
4. Your agent's wallet. You run npx oneie where your agent works, then set its limit. Only you can raise it. Your agent sends the link to one real person. Done when the wallet and the limit exist.
5. Say it in the room. You post one sale and one miss. Your agent posts its own numbers. When the room settles an answer, it is saved, and the next member starts with it. Done when a thread is hardened.

After the lap the member is in Company, the first chapter of the course proper.

The three success milestones

• First payment link. A product with a name and a price, and a link that opens a checkout. Signal: a products:create row. It is wired. Nudge if it stalls: "You have a key. A key with nothing to sell earns nothing. Give me a name and a price."
• First test sale. A practice payment on your own link, read back by the shop. Signal: the sale read back. VERIFY which event records it. Nudge if it stalls: "Your link exists. Nobody has paid it, you included. Pay it with the test card and watch it land."
• First real sale. A buyer who is not you pays a real link. Not yet. It waits on payments going live on mainnet, Stripe moving from test to live on the member's shop, and one real payment through a link. Until then nobody is told they have had a real sale. The milestone is shown as a goal.

Beyond the three: the rungs that keep a member.

• Repeat use: a second product, or a second sale. Signal: a second row.
• Configuration: an agent with its own wallet and limit, and a sweep rule that sends what it earns back to the member. The sweep moves SUI today, not USDC. VERIFY before saying "comes back".
• Advocacy: a post in the room that gets saved, or a referral.

The stall nudges, in final words

Email, sent once per stalled rung, after one wait beat with no signal:

• Subject A: Your link is made. Has it been paid? (36)
• Subject B: Pay your own link in one sitting (32)
• Body: You made a payment link. Open it and pay it with the test card. It takes one sitting, and you will see the receipt. Then your agent can send it. Stuck? Reply and say where. The Sold tutor sits beside Setup.
• CTA: Open Setup, https://one.ie/learn/setup

Chat line for a member who goes quiet: "Where are you stuck: the key, the link or the agent? Tell me and I will pass it to whoever knows."

Docs organised by outcome. The member at rung one needs to find rung three without knowing its name. The front door is a question, not a feature list: "How do I get paid?" goes to Setup, section on cards and crypto. "How do I let my agent sell?" goes to Setup, section on the link, then Together. "Who else is learning this?" goes to Together.

Release note, same shape every time. Name the problem, link the feature. Example: "You can now pay your own link and watch the receipt land. Open Setup." No internal names.

Receipts

• The enrolment path: enrollFromSettledSale grants it at the webhook (text/sold-plan.md, Build order). Whether a real purchase completes is unverified.
• https://one.ie/sold read 2026-11-12 lists as Built: the Sold tutor beside every chapter, chapters read at /learn, the community, a seat that ends when the month does, and a named agent for an enrolled learner. Judged practice sales read Not yet. An agent seat reads Not yet.
• Probed 2026-11-12, HTTP 200: https://one.ie/learn/setup, https://one.ie/learn/educate, https://one.ie/learn/together, https://one.ie/learn/saas/educate, https://one.ie/sold.
• https://one.ie/products returns 302 to /w/shop; /cards returns 302 to sign-in. /learn/saas/one returns 404, so the record page is not on production yet.
• pay.one.ie/status read ok, network testnet, 2026-11-12.
• education-onboarding exists (workflow-templates.ts:1440): a welcome mail, one delay step ({"days":3} in the config), then a lesson mail. It arms on lifecycle:won, not on a Sold sale.

Still open

• Two sources disagree and we print both. https://one.ie/sold (2026-11-12) says the community is Built and shows "Enrol for $100". text/sold-plan.md and text/one.md still say the course is a draft and the community group does not exist. VERIFY by walking one enrolment to the room. We do not choose one.
• education-onboarding is not armed on a Sold sale. Until it is, a person welcomes the buyer, or nobody does.
• The monthly price of the community needs a recurring price in the store. VERIFY.
• The event that records a practice sale is unnamed here. VERIFY.
• The per-learner "you and your agent both did it" mark is not built, so "adopted" is read from product rows and the room, not from a progress bar.
• Judged practice sales, an agent seat and selling to each other are not built.
• No adoption rate, no time-to-first-link, no retention. We have zero members measured. None invented.
• "Zero to a sale in a minute" is not said. It waits on a timed run.
• "0% fees" is not printed. Say that ONE takes nothing from a card sale and the card network takes its fee.

Do it yourself

1. Write your ladder as observable actions, not feelings. One row per rung, each with the event that proves it.
2. Pick your three milestones. Mark each "wired" or "not yet", and name what a "not yet" waits on.
3. Write the first lap as sittings. Each opens when the last one's signal fires.
4. Write one nudge per stall, with the exact next click. Send it only after a quiet wait.
5. Organise your docs around what the member wants next, then check a rung-one member can find rung three alone.