Saanora Moons, the always-on agents powered by Mark, now do professional work in real detail: a teacher's slides and a test with its answer key, a lawyer's notice and redline, a developer's pull request, a creator's posts and clips, a founder's follow-ups. Here's how each one works, and where you stay in charge.
A moon can do anything you ask. But anything isn't enough for work someone will sign. A test needs an answer key that matches every question. A legal notice needs the clause it relies on and a deadline counted from receipt. A pull request needs to say how it was tested.
So moons now work from playbooks: 336 of them, across 28 kinds of work, each written the way a senior person in that field does the job. What to hand over and in what format, the steps, and the checks a reviewer would make. A moon looks up the one that fits, then makes the real thing: a Word file, a PDF, a deck, a spreadsheet, a branch on GitHub.
Two things don't change. Anything that leaves the moon (sending, posting, filing, pushing code, paying, deleting) waits for your OK. And in regulated work, the moon drafts and a professional signs off. The moons below come from Orbit, but every moon has the playbooks, Wibble included.
- Teachers: lesson slides with speaker notes, handouts, and tests with answer keys and mark schemes.
- Lawyers: contracts, notices, contract reviews and redlines, for a lawyer to sign.
- Developers: bugs found and fixed, pull requests, websites tested. Pushes ask first.
- Creators: posts and replies that ask first, and short clips with captions.
- Startups: follow-ups, support replies, investor updates and decks.
- Everyone else: finance, HR, healthcare admin, property, trades, design, research, study and more.
Teachers: slides, notes and tests that add up
Ask Noodle for tomorrow's lesson and you get a PowerPoint in teaching order: the objectives, a starter, the new idea in small steps with a worked example for each, questions to check understanding with the answers on the next slide, the main task with a time limit, and an exit ticket. The speaker notes carry the teaching: what to say, what to ask, the answers to listen for, and the minutes for each slide.
A test comes laid out like a real paper, with the marks in brackets at the margin. Its answer key and mark scheme come as a separate Word file that never goes into anything meant for students, every worked answer solved a second time, and a blueprint shows which topic each question covers. Notes and handouts come as a PDF to print and a Word file to edit. Pick the school theme, or your school's own colour and font.
- Move the lamp closer: more light reaches the leaf.
- More light: more bubbles of oxygen a minute.
- Far away, light limits the rate.
- Check: what happens at 50 cm? Answer on the next slide.
Lawyers: drafts for a lawyer to sign
Dapple drafts the way a firm's documents look: on your letterhead, clauses numbered 1, 1.1 and 1.1.1 without anyone typing a number, footnotes, a contents page, and a signature block for each party.
A notice has what a notice needs: how it's delivered, the facts in numbered paragraphs, the clause it relies on quoted exactly, the demand, a deadline counted from receipt, the consequences and a reservation of rights. A contract review comes back as a memo with the issues ranked by risk, a tracker in Excel, and the dates that matter, with reminders if you want them.
When the other side sends a draft back, the moon compares it with the version you last sent and makes a redline: Word with tracked changes, and a PDF with insertions underlined and deletions struck through. It lists every change, including the ones nobody flagged.
None of it is legal advice, and nothing is sent or served until the lawyer approves it. Where the answer turns on local law, the draft names the jurisdiction it assumed and marks the point to check.
Developers: bugs fixed, and pushes that ask
Gizmo works on its own computer, with git, Python and Node. It reproduces a bug before it touches the code, makes the smallest fix that works, adds a test that fails without it, and runs what your CI runs.
When the work is ready, it pushes a branch and opens a pull request that says what changed, why, and how it was tested. Both wait for your OK, and the card names the branch and where it's going; a force push says so. Deploys, publishes and commands that change a live database ask too. Merging stays with you.
Ask it to test a site and it opens it in its own Chrome at a phone's size and a desktop's. It reports console errors, failed requests, broken links, how long the page took, the title and description search results will show, images without alt text, and whether the page fits a phone. The desktop and phone screenshots land in its Files.
Gizmo wants to create a pull request
Needs your OKFixes #214. What changed: removing a discount code left the old total on screen, because the basket worked out the discount before the code was gone. It now clears the discount first. How I tested it: a new test in basket.test.ts fails without the fix and passes with it. npm test and npm run build both pass. Before and after screenshots are in Files.
Your rule: ask before posting anything public
- Console: 1 error on /basket, TypeError: total is undefined (basket.js:88).
- Links: checked 24 same-site links, 1 broken: 404 not found · /returns-policy (on /basket).
- Phone (390 px): the page is 452 px wide on a 390 px screen, so it scrolls sideways. Widest: the size guide table.
- Load: largest paint 3.1 s (could be quicker: over 2.5 s) · first byte 0.4 s.
- Also: 2 images without alt text. Title and description are fine.
Social media: every post waits for your OK
Jingle plans a month of posts and drafts them in your voice. When it's time to post, on X, LinkedIn, Instagram, Threads, Bluesky or a scheduler like Buffer, the click that posts asks first, and the card shows the exact text going out. Replies, comments, reposts, follows and messages ask too, because other people see them.
It doesn't do mass actions. The first 3 likes in a task are fine; after that each one asks, and past 10 it stops, because liking at volume is what sites ban. Always allow covers one kind of act on one site, like posting on LinkedIn, never every click there.
Jingle wants to post on LinkedIn
Needs your OK“We've moved the studio to Harbourside. Same team, a bigger kiln, and a front window you can watch us work through. Open studio this Saturday, 10 till 4: come and throw a pot with us.”
Your rule: ask before posting anything public
- Replies, comments and reposts ask too
- So do follows, requests and messages
- Likes: 3 in a task, then each one asks. It stops at 10
Video: clips from the long recording
Hand Wibble a long recording, like a podcast episode or a talk, and it finds the moments that stand on their own, cuts each into a vertical clip with the captions burned in, and lists every clip's in and out times in a sheet. It sizes a video for where it's going (9:16, 1:1 or 16:9), and makes short ones from your pictures, clips and text cards, with music under them.
A video runs up to about two minutes, from a recording up to half an hour long. A moon can also record its own screen for a walkthrough, up to 30 minutes, and the recording pauses whenever you've taken over its computer. Posting a clip waits for your OK, like everything else.
| Clip | In → out | Hook |
|---|---|---|
| 01 | 3:26 → 4:08 | One honest post beat every ad we ran |
| 02 | 11:45 → 12:36 | The email we almost didn't send |
| 03 | 22:05 → 22:48 | Why we stopped discounting |
Startups: the follow-ups nobody has time for
Chipper reads your pipeline, from a sheet in Files, your CRM or what you paste, and finds every deal that's gone quiet. For each one it writes a short follow-up with one true reason to write now, biggest deals first. Nothing is sent until you say so.
Patches drafts support replies from your help pages and policies, specific to what each customer asked, and lists anything you should check before sending. And for the founder's own work there are playbooks for the investor update, the pitch deck, the board deck, the financial model and pricing.
Three deals have gone quiet. A draft for each is ready, biggest first, and nothing is sent until you say so.
| Deal | Value | Quiet for | Why write now |
|---|---|---|---|
| Lumen Health | £24,000 | 9 days | Opened a clinic in Leeds last week |
| Northgate Foods | £12,500 | 6 days | Asked for the pilot numbers, which are in |
| Arden & Co | £8,000 | 12 days | Their trial ends on Friday |
Chipper wants to email Maya at Lumen Health
Needs your OKHi Maya, Congratulations on opening in Leeds. When we spoke you wanted the pilot to start at one site, and Leeds could be it. Would 20 minutes on Thursday work to plan it? Best, Sam
Your rule: ask before sending emails
And every other kind of work
The same care runs through the rest of the library:
- Finance: the month-end close, bank reconciliations, invoices and the polite chase, cash flow forecasts. You or your accountant sign off, and a moon never moves money.
- HR: job descriptions, interview scorecards, offer letters, onboarding plans and handbook policies, for HR to approve.
- Healthcare admin: practice procedures, patient handouts, staff rotas, referral letters for a clinician to complete. Never a diagnosis or a dose.
- Real estate: listings, market comparisons, lease summaries, rent rolls and owner statements.
- Trades: quotes with materials and labour, job sheets and invoices, risk assessments, before-and-after photo reports.
- Design: brand guidelines, moodboards, UX and accessibility audits, client presentations.
- Research and study: literature reviews with real citations, grant proposals, study plans, notes and flashcards.
The listing for 14 Alder Road is ready, with a short version for the portals and one for social posts. Three facts to confirm before it goes up: the service charge, the years left on the lease and the council tax band.
- Teaching and education
- Students
- Legal
- Software and IT
- Product and project management
- Data and analytics
- Video, audio and editing
- Social media and creators
- Marketing
- Sales and business development
- Customer support and success
- Founders and small business
- Finance and accounting
- HR and recruiting
- Operations and admin
- Writing, journalism and publishing
- Design and architecture
- Engineering and manufacturing
- Research and academia
- Healthcare and wellness (admin)
- Real estate and property
- Consulting and freelancing
- E-commerce and retail
- Hospitality, travel and events
- Nonprofit and public sector
- Trades and field services
- Arts, music and entertainment
- Personal life and household
For a job no playbook covers, a moon follows the general method: work out the real deliverable, find how professionals in that field do it, gather the facts without inventing any, make the real thing, check it the way a senior colleague would, and hand it over with what it assumed. Anything that goes out still waits for you.
Start with one job
Pick a job you'd hand a capable colleague and give it to Wibble. If it keeps coming back, Wibble will suggest a teammate for it. Moons come with every plan, inside the same weekly usage as chat, and they're on the web today.