Share: ONE's own run

The decision

ONE gets its next customers from its current ones, and the one honest moment to ask is right after a real payment lands. Today that moment has not happened: there are 0 live payments and 0 Sold purchases. So this record holds the finished copy and the rules, and every ask waits on a server fact, not on a calendar. The reward is not a discount. The frame is: you were stuck with an agent that could not be paid; here is the way out, send it to someone who is stuck. We never ask a customer for a five-star review, and we never pay for one.

What we built

The trigger. One server fact per audience, never a timer.

Free key user: the first live payment lands. That is an order marked paid on a live card or a crypto payment off testnet. Test money never fires it.
Sold buyer: the Sell stage is finished. The course is built to write one reward row per finished stage, and the table holds 0 rows today. VERIFY the stage id for Sell and that the row is written.
No satisfaction score exists. Nobody has been surveyed, so no ask is scored or gated.

The share moment, after the first payment. Final copy.

On the receipt, person lane:

You were paid. That is the whole point of the key. Somebody you know is where you were this morning: an agent that can talk and cannot take money. Send them the way out.

Button: Copy a note to send. The note it copies:

I just got paid through a link my agent sent. The key is made on my own machine and ONE takes nothing from the sale; the card network takes its fee. It is free to try: npx oneie key new

On the receipt, agent lane (one machine-readable line, sent with the receipt):

Paid by link. To be paid the same way: npx oneie key new. The key stays on your machine.

What an agent says to another agent in a thread, final:

I am paid through ONE. My owner holds the key, nobody else does. If you sell, run npx oneie key new and ask your owner to keep the 24 words.

The referral program. Proposed terms, for Tony to judge. Nothing here is live.

Referrer gets: one more month of the community when the friend they sent buys Sold. Cost to ONE is a seat, not cash.
Friend gets: 10,000 credits for their agent on enrolling. At 1 credit = $0.001 that is $10. VERIFY the real cost of 10,000 credits before this is said aloud.
Trigger: the share moment above, and the same note again when a Sold buyer finishes the Sell stage.
Mechanics: one link per person, https://one.ie/sold?ref=<their slug>. First touch wins. A person cannot refer themselves. Progress shown as "one friend away from your next month".
Copy rule: say it helps a friend. Never lead with the reward.
Never print a percentage next to "ONE takes nothing". The old rail's 10% is a default in code, and who pays it is not settled (see Still open).

The review ask. Two touches, no gate.

Touch one, sent when the trigger fires:

You were just paid for the first time. Would you write two sentences for the next person in your spot? What were you doing before, and what changed? Honest is the only kind we want. If something was rough, write that too.

Touch two, sent once, after their next course stage and never again:

One line is enough. How did the first payment feel? If you would rather tell us privately, reply here and we read every one.

Rules that hold: ask every buyer who reaches the trigger, not only the happy ones. Offer no reward for a review. A private reply route sits beside the public one, never instead of it. Our house rule here differs from the agent playbook's "route 1 to 3 stars privately first", which would gate reviews; VERIFY with Tony.

The UGC brief. One ask.

Post the receipt of your first payment and one sentence: "Paid by my agent." Hide any address you want hidden. A payment on a public chain can be seen on that chain, so show only what you are happy to show.

Rights line, inside the entry: "I let ONE repost this, with my name or without. My choice."
Reward: a place on /sold and in the community. No cash.
Selection: every post that shows a live payment is featured. Test-money receipts are never reposted as proof.
Where it goes: /sold, the community room, and the ad only with the author's yes.

The case study. Slots only. No quote exists.

Candidate: cohort zero (text/sold-cohort.md). First live payment and first Sold sale are the receipts it needs.
Before: VERIFY. Mechanism: the key, the link, the first payment. After: VERIFY. Quantified result: VERIFY a number the customer will defend. Verbatim quote: VERIFY, from a recorded conversation, with permission and the draft sent back.

The amplification hand-off (the share:assets-ready fields, as lists, not emitted)

review_request: trigger, touch one, touch two, routing rule above.
referral_program: referrer reward, friend reward, trigger moment, mechanics, copy rule above.
ugc_campaign: prompt, incentive, rights line, amplification plan above.
case_study: the five slots above, all VERIFY.

Receipts

https://one.ie/sold, /affiliates, /partners and /learn/saas all returned HTTP 200 on 2026-11-12.
/affiliates showed "No affiliate programs listed yet" on 2026-11-12. The public directory is empty.
Production D1, read 2026-11-12: 0 rows in affiliate_commissions, 0 in world_affiliate_requests. The referral rail has never paid anyone.
The old rail's parts exist in code: a first-touch-wins ref capture (one.ie/web/public/p/one.js:39), a self-referral guard on the payment-link path (pay/backend/src/protocol/handlers/payment-link.ts:1314) and a default commission of 10% (pay/backend/src/affiliate.ts:65). "Green" in text/one.md 9.2 means built and tested, not used.
36 paid orders exist, all Stripe test sessions, 0 live. 0 of them carry a Sold price. None records an application fee, but test orders do not prove the live fee. VERIFY migration 0377 ran on production.
2 enrolments sit in the sold course with no matching Sold purchase. They are not buyers.

Still open

No ask can fire. There is no live payment and no Sold purchase.
The rail does not reach Sold. The orders table has no referrer column, and the old rail pays on crypto payment links only. A Sold referral needs a ref stamped on the order. Filed as a row, not built.
one.ie's own pages do not load the ref-capture pixel (p/one.js is for client sites). Measured: 0 of the pixel rows on slug one in the 14-day window carry a ref. A ?ref= on one.ie is not kept today.
The CLI has no --ref. A referred key made with npx oneie key new makes no network call, so a referral through the key alone cannot be counted. The count must come from the Sold order or the first payment.
Who pays a referral reward is unsettled. In the pay code the commission comes out of the payment. That clashes with "ONE takes nothing from a sale". Say no percentage until Tony rules.
The credit reward needs its cost. The free month needs the monthly price to exist; it does not yet.
Which review site Brian trusts is not known. Ask the first ten buyers.
Cards are in test mode and payments are on testnet. Nothing here may say "live".
https://one.ie/learn/saas/one/share returned 404 on 2026-11-12. This record is not published yet.

Do it yourself

Pick one server fact that means "this customer just got the value". Not a date. Write it down.
Write the ask in two sentences: what they did, and who they know who is stuck. Make the sendable note ready to copy.
Choose a reward that costs you little and helps them. Check it against your own margin before you say it.
Write the review ask with no score gate and no payment. Add a private route beside it.
Write the one UGC brief with a rights line. Leave every number blank until it is measured.

How it was measured

curl -s -o /dev/null -w "%{http_code}" -L on the five pages above, 2026-11-12.
SELECT COUNT(*) FROM affiliate_commissions and FROM world_affiliate_requests, both read-only, on production one-owners.
SELECT COUNT(*), SUM(session_id LIKE 'cs_live%'), SUM(session_id LIKE 'cs_test%') FROM orders WHERE status='paid': 36, 0, 36.
SELECT course_id, COUNT(*) FROM course_enrollments GROUP BY 1: sold, 2. SELECT COUNT(*) FROM orders WHERE ppid LIKE '%sold%': 0. SELECT COUNT(*) FROM course_rewards: 0.
grep on the three code lines named above. A grep proves the code exists, not that it runs.