What's new

The big one this time is not a feature. We had an independent, route-by-route security review of the

whole platform — every page, every button, the marketplace, the module sandbox and the background

services — and we fixed everything it found before this release went out.

What that means for you. Nothing you need to do, and nothing was misused: this platform is still

small and every account on it is known to us. But several of the things found would have mattered a great

deal later, when strangers can supply modules and the marketplace is open. We would rather fix them while

the answer is "nobody could have", than after.

• Modules are properly walled off now. A module used to be able to reach further into the platform than it had any business reaching. Every conversation between a module and the platform is now individually authenticated, and a module is told who it is working for rather than being allowed to claim it. Each module also gets its own private area of the database.
• Publishing a module now needs a person. Uploading is open; *running* what was uploaded is a decision an operator makes. Same for issuing a publishing key.
• Sign-in is stricter. Signing in with Google, Apple or Microsoft will no longer attach itself to an existing account that merely shares an email address — link it deliberately from your settings instead. Password reset and invitation links are now built from our own address rather than whatever the browser claimed, and an invitation can no longer sign you in to an account that already exists.

Fixed: credits could be taken for work that never happened. If anything went wrong in the moment

between paying for a module build and the build being queued, the credits were gone and the request was

not. Payment and the work it buys now succeed or fail together. Alongside that: builds that fail for good

are refunded automatically, requests nobody decides are closed and refunded after a week, and refunds for

requests raised here now actually reach the account that paid — previously that last one quietly did

nothing at all.

Fixed: a form could fail and say nothing. If a save failed, the page simply did not move — no error,

no explanation, and on the workspace settings popup that meant renaming your workspace looked like it had

not worked when it had. Failures are now reported on screen, everywhere, on every form.

Fixed: saving workspace settings could fail outright for any workspace after the first, because of a

clash in how directory connections were stored. Saving no longer writes a directory connection it was

never asked to make, and no longer floods your workspace history with entries about a setting you did not

touch.

Faster. The busiest thing in the database was a settings table being re-read dozens of times a page;

it is now read once. Two screens that queried once per item on screen now ask a single question. Pages

across the platform do noticeably less work to draw.

Better on a phone. Every screen has been measured at phone size: no sideways scrolling, every control

big enough to press, dialogs that fit and can be closed, sticky bars that sit where they should, and the

navigation drawer's own contents finally sized for a thumb.

• The External badge now shows on a workspace's public page — the page it exists for — so a visitor can tell which modules a workspace built and which it added from elsewhere.
• Retired marketing pages redirect to the front door instead of an error, and the site map no longer points search engines at pages that no longer exist.

• Modules, games and videos now have a home worth browsing: Discover is the front page, with picture covers, a Following page listing every workspace you follow, and pinned workspaces and modules kept in your menu so you can get back to them in one press.
• Fixed: Financials and Earnings would not open. Both screens carried a leftover instruction to bounce back into the old page frame, and once the frame was removed that instruction fired every time — the screens redirected away from themselves before you could read them.
• Fixed: an address that does not exist no longer answers as though it does. Mistyped or out-of-date links used to return a page-shaped nothing. They now take you to a short page that says what happened, shows the address that failed, and offers to report it in one press. Retired addresses forward properly again, too.
• Being refused a screen now says so in a sentence, with a way back, instead of showing a bare status code.
• Addresses say workspace where they used to say company — the word the rest of the app has used since v1.4.0. Every old link still works and forwards to the new one.
• A workspace has an owner: the person who created it. Owners are the only people who can take money out, and every workspace shows who its owner is.
• Coins held by a workspace from before owners existed have been retired. They were never spendable by an individual, and handing them to one on a guess about who founded the workspace was not a decision worth making automatically.
• The blog has closed. Everything it carried was release-shaped, so /blog now brings you here instead.
• Charity donations, which were never taken live, have been removed.

• Your subscription now says how many of your own modules you can run at once, and what you earn from them. Starter runs 1 (and can keep 1 more parked) and earns 25% of the credits other workspaces spend on it; Team 3 and 2 at 40%; Business 12 and 8 at 55%; Enterprise as many as you like at 70%. 70% is the rate every supplier was on before this, so nobody on the top plan is worse off. Your share is shown on your supplier dashboard, and on each plan on the Billing page before you buy it.
• Pausing a module takes it out of the marketplace and stops it running — for you and for anyone who had installed it. Nothing is deleted, and starting it again brings it back exactly as it was. If you move to a smaller plan we pause the least-used ones for you, and tell you and everyone affected which they were.
• Ask a supplier to change their module and you will not be left waiting forever: if they do not answer within 7 days the request closes itself, you are told, and you are offered a module of your own instead with everything you already typed carried over. It is never recorded as the supplier having refused.
• Modules you own now get a nudge, at most once each, suggesting you could make them public — when one is first built for you, when you have used it for a few days, and when somebody else asks for something like it. Making it public is explained on the module screen, with a Make public button.
• Choose how Yomcom looks for you, under Appearance in your settings: your workspace's theme, Light, Dark, or your own colours designed with AI. It follows you to every device and every workspace you belong to. Dark mode is new — the first time the app has had one.
• Choose how the menu is arranged, too: Simple, Creator (for building and selling modules), Everyday (for using them), or Custom, where you drag the items into groups you name yourself. Every arrangement holds the same items — nothing is ever hidden from you by choosing one.
• The menu can also be docked permanently to the side of the screen instead of sliding in, on larger screens.
• Fixed: refreshing the page sometimes took you back to Billing instead of where you were. Returning from a payment left a marker in the address bar that quietly took over the tab from then on.
• The Modules admin screen is now called Module admin, because the menu also carries your modules themselves and both were called the same thing.

• Organisations are now called workspaces, everywhere. The name never fitted what most people were actually making: a workspace can be a company, a charity, a group, a sole trader, or one curious person with an idea, and "organisation" made the last of those sound like paperwork. Nothing about how they work has changed — same members, same billing, same modules — only what they are called. Older entries in these notes still say organisation, because that is what shipped at the time.
• Old links keep working: /organisations now redirects to /workspaces rather than going nowhere.
• You can share a module the way you would share a video — a Share button on each module card, which uses your phone's own share sheet where there is one and copies the link where there is not.

• Every account now has an organisation of its own from the moment it signs in, so nobody lands on a wall asking them to create one before they can look around. Accounts created through Microsoft sign-in get the same starter credits as any other, which they previously did not.
• Follow an organisation to hear when it releases a module. The maker's name on each module card opens their page — what else they have made, their site, and a Subscribe button. Everyone follows Yomcom by default and can stop whenever they like.
• Ask the makers of a module to change it. A short guided form sends the request; the people who own the module decide, and see how many organisations use it, how many hours go into it and what it has earned them before they answer. Asking is free. If they say no, you are offered a module of your own instead, started from what you already wrote.
• Modules now record how long they are actually used, so their makers can tell what is worth improving. Only time with the module open and in front of somebody is counted, and suppliers see totals, never who.
• Yomcoin earned by suppliers is now attributed to the module that earned it, rather than arriving as one monthly lump.
• The sidebar leads with what people actually need: your organisation, your modules, getting one built, credits and support are always visible instead of hidden inside a closed section. Menu items are named for what they do — People, Earnings, Assistant appearance — and single sign-on has moved onto the Organisation settings page rather than a screen of its own.
• Pages are compressed in transit and stylesheets are minified. On a slow phone connection the app now loads in about half the time it did.

• Yomcoins are now cryptographic: every holding has a secp256k1 key pair and a checksummed address, the ledger is hash-chained so any alteration to its history is detectable, and coins can be transferred between holders on a signed instruction. Private keys are held in custody, encrypted at rest.
• Support: a new guided support portal at /support — describe what went wrong and what you were doing, and the AI writes the report back for you to correct before it is raised. It also checks whether somebody has already reported the same thing and offers you their ticket instead.
• Status: a public status page at /status answers "is the site working?", built from what real requests are actually doing rather than from polling. Every AI failure in the product now links to it.
• Tutorials: finishing one now actually pays the credits it promised (the request was being rejected before it reached the server). The reward amount is configurable on the platform settings page.
• Deleting an organisation now removes its module data too — projects, records and documents that used to survive it — and cancels its Stripe subscriptions so nothing keeps charging. Financial records and the audit trail are kept deliberately.
• Deleting a person now removes their support tickets, help transcripts, tutorial history and newsletter subscription, and cancels any subscription in their own name.
• Modules built from a request now arrive already installed for the organisation that asked, and the person who asked is told when it lands rather than when it was built.
• Personal plan names are now Member, Insider, Partner and Executive.
• PR & outreach is an organisation-level screen; the newsletter is separate again and stays super-user only.

• Company: auto-upload logo on file selection (remove Upload button)

On /admin/company, in the Organisation card's logo section: remove the separate "Upload logo" button. As soon as the user picks a fi

• Notifications popup: show unread only (read ones behind "View all")

In the notifications popup (opened from the bell icon at the bottom of the menu, next to sign-out), only list UNREAD notifications.

• /admin/assistant: "Generate new" button → "+" icon, inline with "Your custom assistant" heading

On the Assistant admin page (/admin/assistant): replace the "Generate new" button's text label with a "

• Auto-focus chat input when chatbot opens

When the user opens the assistant/chatbot panel, focus should be placed automatically in the chat message textbox so they can start typing immediately without

• /admin/apps: add "Available Modules" section below Installed Modules expander, with install action

Requested by Christian (super-user) on /admin/apps.

Below the "Installed Modules" expander card, ad

• Modules: retired the Marketplace page and menu item — the assistant now surfaces modules as cards (View → details → Install) directly in chat.
• Modules: you can ask the assistant to BUILD a new module for your organisation; it shapes a plan with you, checks it against guardrails, and hands it to the AI developer. A module you request is delivered to you in demo mode automatically once built.
• Modules: installing gives your organisation its OWN copy of a module, and you can ask the assistant to make changes to that copy without affecting anyone else.
• Modules: SDK now provides the shared page shell so modules stay small and build faster.

• Dev-tasks list: refresh causes scroll jump / textboxes reset

On /platform/dev-tasks, the task textboxes refresh periodically and reset scroll position, jumping the user back to the top while reading/ — reviewed, not a bug

• Collapse all cards by default on Settings page for first-time users

On /platform/settings, cards should be retracted/collapsed when a user first arrives at the page, rather than expanded.

• Improve layout of Currencies & exchange rates screen (/platform/currencies)

User feedback: this screen's layout needs improving. From screenshot: fields feel cramped/inconsistently spaced between cur

• Wrap release cards in expanders and add pagination to releases page

On /platform/releases: each release card should be wrapped in an expander (collapsed by default, can be expanded to show full detai

• Chatbot text box should only refresh on content change, not every render

On the dev tasks/AI developer screen, the task text field refreshes on every render, causing the scroll position to jump back

• Add attachment button below chatbot send button

Users should be able to upload and attach files to their chat messages via a dedicated button positioned below the send button.

• Chatbot input box should be three lines high, multi-line with text wrapping and vertical scroll

The chatbot input text box needs to:

• Display 3 lines high by default
• Support multi-line input with
• Remove 'Marketplace', 'Contact Us', and 'About Us' from public landing page header

Remove the 'Marketplace', 'Contact Us', and 'About Us' links from the header navigation on the public landing page (

• Dev tasks need 'Submit' button to lock input before AI moderator processes

Each task on the dev-tasks screen needs a dedicated 'Submit' button that disables the input textbox and allows the AI modera

• Landing page should be a single page with sign in button (as now), a popup Market place window, and a popup contact us windows. Essentially removing the market place and contact us from being on a sep
• AI developer screen implemented items should collapse in expander

On the AI developer screen, completed/implemented items should be hidden in a collapsed expander to keep the active task queue clean

• AI developer 'Apply Now' console should refresh immediately

On /platform/dev-queue, when the user clicks 'Apply Now', the console should start refreshing and displaying output in real-time. Currently

• Dev tasks approve button should update instantly without page refresh

On the /platform/dev-tasks page, when a user clicks the approve button on a task, the task status should update immediately in th

• Dev tasks need 'raised by' field

Add a 'raised by' field to dev tasks so developers can submit multiple tasks at once and then approve/review them in batch from the dev-tasks list. Each task should s

• AI developer should auto-delete completed dev tasks

When the AI developer finishes building a task, it should automatically remove that task from the dev board instead of leaving it there marked as d — reviewed, not a bug

• Rename 'Security' to 'Settings'

Account menu: change the menu item label from 'Security' to 'Settings'. The Security page remains the same; only the label in the navigation menu changes.

• On a phone screen, the menu and chat-bot combine buttons/control is fine, but on a larger screen, the menu should be at the top and the chat-bot button at the bottom (on the side they have set it up t

• Simpler sign in / sign up: one email + password form (plus the social buttons) instead of separate tabs — the same form signs you in or, for a new email, creates your account. If you were referred, you're now asked once on your first sign-in (a quick "were you referred?" prompt) rather than on the form.
• "Organisation didn't appear" fixed: joining or creating an organisation now shows up immediately — no need to close the browser and sign back in. (The browser was caching the page; it no longer does for signed-in pages.)
• Menu & assistant redesign: the main menu is now a floating panel that slides in from your chosen side; the AI assistant chat is a larger floating window in the menu's colours that slides in from the same side, closes when you click outside it, and is titled "Your AI assistant" with a bot icon. In the menu, the organisation switcher sits next to the logo (which shows your organisation's own logo if you've set one), and sign-out is a small icon tucked beside your email, away from the menu button.
• Billing: Starter is €18/mo for 100 credits and Team is €90/mo for 500 credits, each showing its bulk-discount vs buying credits one-off; the Unlimited tier was removed. Operators can now give an organisation an enterprise discount (a % off its plans and credit purchases) and/or a bespoke custom plan (its own price and monthly credits); enterprise/custom plans can be billed by invoice (Stripe emails and chases the invoice; credits apply automatically when it's paid).
• SOP builder: generating an SOP now runs in the background — you can leave the page and get a notification (and email) when it's ready; the first generation is free and later edits cost a credit; optional questions left blank are skipped; and admins can turn off the AI suggestion step per question.
• Smaller polish: the Codebase repo cards use clean icons, a long organisation name no longer overflows the switcher, and the internal "display name" field was removed from sign-up.

• Sign-up now explains itself: if creating an account fails, the form reopens the Sign up tab with the actual reason — the password doesn't meet the rules, or an account with that email already exists — instead of the old, misleading "Sign-in failed. Check your details." The password requirements are now shown right under the password box, and the email you entered is kept so you don't have to retype it.

• Sign-up now survives a blocked cookie: some browsers block the security (CSRF) cookie the sign-up form relied on — most often when the link is opened *inside another app* (email, Facebook, Instagram), in a private window, or with third-party cookies blocked. That silently failed the sign-up with no account, no verification email, and no way forward. The public sign-up form no longer requires that cookie (it keeps its bot honeypot + rate limiting), so these browsers can register and receive their verification email. And if a security-cookie check does fail on any sign-in action, the user now gets a clear "please allow cookies for this site / open in a normal browser" message instead of a blank error page.

• Sign-up fix: a referral link (?ref=…) whose referrer isn't a registered account no longer blocks sign-up. Previously such a link stopped the account being created at all — no verification email, and every retry failed the same way. Now the account is created normally and the unrecognised referral is simply dropped; a mistyped referrer entered by hand still shows a clear error so genuine typos are caught.
• Branding: the in-app help assistant, promote-notification emails and the release-notes title now say Yomcom, not the old "Yomcom" name.

• Platform: fixed an infinite loop where a borderline idea could bounce forever between the Suggestions and Support moderators (each deciding it belonged on the other's board) — an item already redirected from one board is no longer sent back, so it settles instead of ping-ponging.
• Codebase module (super-user, Test): "Find screens" now reads each app's routes as well as its files, so screens rendered inline (not in a dedicated page file) are found; "List controls/operations" run per-screen with the screen's own code, so nothing is missed (e.g. a page's table and filters); the model stages nest App → Screen → item as collapsible, retracted-by-default sections; a clean review shows "nothing to fix" instead of an empty review; re-running a stage is additive (never drops what a noisier pass missed). Each section now charges credits per run (operator-tunable, shown up-front), and coding standards can be imported from a PDF/Word/text document.

• Home School: classes are now generated from the qualification a child is working towards, not just their age. The parent picks it from a territory-specific dropdown (e.g. GCSE / A Level / BTEC in the UK), defaulting to the compulsory minimum for that territory. Each territory's qualifications — with their age-ranged stages (e.g. Key Stages) and milestones — are researched by the AI once and shared across everyone in that territory, refreshed monthly. Age still sets the depth within the child's current stage.
• Super-user dev tooling (internal): the AI-developer screen is hidden on live, and on dev gained a "Working changes" panel (view uncommitted file diffs), a "Sync changes" button (fetch/merge/push, with the git output shown), and an "Apply changes" button (rebuild + restart with a clear confirmation).

• Security page: Active Sessions expands on desktop when it shouldn't

Promoted to live from 98ddf48. Highlights since v1.0.3:

• Donations: organisations can be marked as charities that accept donations. Members of a charity org get an occasional, frequency-capped popup inviting them to support it; the donate page lets them give a chosen amount once or weekly/monthly/yearly via Stripe (one-off payments and recurring subscriptions), and shows the charity's own description. Donors can cancel a recurring donation themselves. Donations are a pass-through: collected on the charity's behalf and paid out to them in full each month via Stripe Connect (no platform commission). A charity admin connects a payout account from their org settings; a super-user /platform/donations view shows each charity's Connect status, collected/disbursed/held totals and payout history, with a manual "run now".
• Referrals: a referrer's email entered at sign-up must now match an existing account (a typo is refused with a clear message and the field preserved) instead of being silently dropped.
• Finance/P&L: a "tax to set aside" section (VAT collected + a corporation-tax reserve at a configurable rate, default 19%), a downloadable accountant report CSV for any date range (income, VAT, fees, costs and a tax estimate), and donations shown as a pass-through disbursement — excluded from turnover and profit.

Promoted to live from 0f901f5. Highlights since v1.0.2:

• Referral/affiliate program: sign-up captures who referred a user (email field + ?ref= link); the referrer earns a one-time 200-credit reward on the referred user's first purchase, plus an ongoing cash commission (a super-user-set % of net) on every purchase. Super-user /platform/users sets referrer + %, /platform/referrals shows owed payouts with mark-as-paid, and referral costs feed the P/L.
• New Codebase module (Test state, super-user only): connect a git repo and walk a wizard that reviews & standardises the code and reverse-engineers a full editable model — apps, screens, operations, tests, docs, release notes, selling points and marketing — writing artifacts to the repo root and committing back on your say-so, with incremental scheduled runs. Not yet exposed to companies.
• Dev-host fix: the file store (where the Codebase module clones repos) is excluded from the Host build and given a root outside the content root, so a large clone can't disrupt the build.

Promoted to live from f98c604. Highlights since v1.0.1 (2026-07-13 → 2026-07-16):

• Contact form: self-contained robot check, persisted submissions + AI moderation, contact@ acknowledgements/AI replies, dormant IMAP bounce moderator.
• Marketplace & discovery: deep-link filter/highlight, assistant "take me to a module", "is there an X module?" routing to suggestions, pull-not-push engagement nudges.
• Home School: one class at a time on a real wall-clock hour, end-of-day answer review, family holidays, adaptive full school day on the shared lesson pool.
• Business marketing site redesigned from scratch (logo, theme, copy on all five pages); front-end polish and the new "waypoints on a route" logomark.
• Billing/revenue: per-organisation P/L page with over-time charts, module-declared charges + operator overrides, credit auto-pricing, versioned business costs.
• Platform: cross-org global store for modules (IGlobalStore), AI failover to a backup provider, per-module free trial, org logo in sidebar, all modules available to every org.
• Fixes: support-ticket access-control scoping, module schema honouring C# nullability, invite acceptance/email, misrouted Home School admin POSTs; promote routine hardened (module-table provisioning + deterministic rollback restore).