What's new

MAD-Blog: setting the agenda for Africa's AI transformation

• The blog is MAD-Blog, with 'Setting the agenda for Africa's AI transformation' as its headline.
• Share cards carry the article's title, its summary, MAD's reverse logo and the agenda line; X shows each article's own card.
• Three authors: Zuko Leonard Rabotapi; Dimpho Rabotapi, owner of Dimple's Joy and lead of Curio Earth and My Family Tree, on the legacy of humankind and earth projects; and Letlotlo Rabotapi, owner of TLOTLO and lead of ORC Clinic, on health and savings culture in Africa. Both are MAD-Executive Trainee Associates.
• 20 articles: new are Dimple's Joy: making the day about family; Stokvels, burial societies and every rand; and TLOTLO rewritten around shoppers sharing where prices are lower.

The MAD blog at blog.myafricandream.net

• The MAD blog, on its own address: 18 articles, led by a vision for Africa in the AI era: taking back control from foreign dependence, on the spirit of our work, from Curio Earth, the clinic, TLOTLO and the family tree to the books, Valkey, UNDERDOG, AI in every part of the operation, hands-on leadership and business strategy in the AI era.
• Each article is dated no earlier than the work it describes, and carries its author, tags, a share row and its own share image. The blog has an author page, an RSS feed, a sitemap and installs as its own app.
• www.myafricandream.net/blog moves to the blog's own address.

UNDERDOG in Central Command

• UNDERDOG, MAD's own AI desk (underdog.myafricandream.net), is on the Websites page, in Versions and release notes, and at the top of AI Modules, with a link to open it.
• UNDERDOG answers approved devices only, so its health on the Websites page means its own certificate answers; Central Command itself can't open its pages, by design.

The website's help: a drawer with a handle on the right

• The website's own help works like the apps' now: the round chat button is a slim Help handle on the right edge, half-way down, opening the help as a drawer from the right, the full height of the window; the handle closes it again. Never printed.

Help in the apps: a drawer with a handle on the right

• The help inside MAD's apps no longer sits over the page: a slim Help handle on the right edge opens it as a drawer from the right, the full height of the window, and the handle closes it again.
• It is never printed, so a saved PDF (such as the family tree book) is clean.

Central Command's menu, in a logical order

• The menu follows the business: Insights; Service Desk; People and Comms; the money coming in (Subscribers, Billing, MAD-Shop); Accounting & Tax; HR & Payroll; Legal; Websites & apps; Brand and AI; then Systems, Security and Developer.
• Each page is in one place only: Directory under People, Consent under Legal, Paystack account and Concessions under Billing, EMP201 under Accounting & Tax (HR & Payroll keeps staff, leave, case files, pay runs, the uFiling file and the EMP501).
• Security has its own section (sign-ins, fraud and attacks, the security policy reports), apart from Systems.

HR & Payroll: amounts stay on one line

• On the HR & Payroll pages (staff, pay runs, uFiling file, EMP501) an amount no longer breaks between the R and the figure, and "No e-mail" stays on one line.

API keys move to a Developer menu

• Central Command has a Developer menu: API keys, and the API reference (the MAD API's endpoints and the scope each needs). API keys left HR & Payroll.

The MAD API for HR, payroll and tax

• The MAD API (step 5 of 5): MAD's other apps and the automations can read staff, leave balances and the register, pay runs, the EMP201, the EMP501 and IRP5 figures and each VAT period's working paper, and post leave requests and pay periods. Everything it lists is at /api/v1.
• Keys are made in Central Command > HR & Payroll > API keys, each with only the scopes it needs (hr:read, hr:write, payroll:read, payroll:write, accounting:read), shown once and kept only as a hash, revoked at once when needed. Every call is logged and shown there.
• It works the figures out with the same code as Central Command, so the API and the pages always agree. It never gives out ID numbers, cell numbers, bank details or payslip PDFs, and nothing is filed with SARS or Labour through it.
• Leave asked for through the API waits in Central Command to be approved, like any other request; pay periods may not overlap, and closed pay runs never change.

VAT from Billing: Matshoba's working paper for every VAT period

• VAT 201 now works each period out as Matshoba's working paper. Invoice basis: output VAT comes from Billing by invoice date (Paystack card sales less refunds, billing invoices less credit notes); the bank's money in for those sales is listed at 0%, so nothing is counted twice; rent stays exempt.
• Input VAT from every bank statement line at Matshoba's rates, plus Paystack's fees: Paystack keeps them before paying out, so they never show on the statement and their VAT was not being claimed. They are flagged to confirm until Paystack's monthly tax invoice is filed.
• Download each period as an .xlsx in Matshoba's own layout (VAT Summary with the VAT201 fields, Income, Payments, RECON) with live formulas; lines to check are yellow, and the RECON leaves out what is not bank money, so the bank still reconciles to the cent.
• Each period shows its due date (the last business day of the month after), how many lines need confirming, and whether the bank reconciles. Money in with no invoice behind it is flagged: if it was a sale, rate it 15%.
• Nothing is sent to SARS: download, check, keep it in MAD Repo (SARS-Taxation/MAD-SARS/VAT201), file on eFiling.

HR & Payroll into Accounting: the EMP201 from pay runs, the uFiling file, the EMP501

• The EMP201 now takes a month's figures from its closed pay run (the payslips' own PAYE and UIF), so the return is exactly what was paid; months without a closed run still work out from the staff pay periods. Marking a month filed keeps those figures.
• uFiling file: each closed pay run as the UIF declaration file for uFiling's Bulk Upload, in the Fund's E03 layout (Simple Comma Delimited: creator, employees, employer with the totals). Everyone employed in the month is declared, as the Fund asks; the contribution is exactly 2%, the leaving date and its uFiling status code only when the person has left, and the UIF reference is checked with the Fund's check-digit formula. Warnings that would keep a person off the Fund's main database are listed before the download. Download TEST first, then LIVE.
• EMP501 & IRP5: a tax year's reconciliation from the closed pay runs, full year or interim (March to August): each person's IRP5 figures with SARS's source codes (3601, 3698, 3699, 4102, 4141, 4149), and each month's run against the EMP201 filed, with the difference. For entering on SARS's e@syFile Employer.
• SARS and Labour have no public API: Central Command prepares the figures and the file; Leonard submits.

HR & Payroll: case files and leave

• Case files: every labour matter with a person (CCMA and bargaining council disputes, the Labour Court, internal disciplinary and incapacity hearings, grievances and warnings), each with its forum and reference, status and outcome, the next date and what is due then, a dated history, and where its papers are in MAD Repo. Open cases and their next dates come first. For the owner only.
• A case shows the Labour Relations Act's time to refer it (30 days for a dismissal, 90 for an unfair labour practice, 6 months for discrimination) and how late a referral was.
• Leave (PTO): each person has their own signed link to see their balances and ask for leave; the request comes to Leonard by e-mail and waits in Central Command > HR & Payroll > Leave to be approved or declined, and the person is told by e-mail from hello@.
• Balances by the Basic Conditions of Employment Act: annual 15 working days a year (1.25 a month), sick 30 days per 3 years, family responsibility 3 days a year, parental 10 days; maternity 4 months from UIF. Only working days count: weekends and public holidays (Easter, and a Sunday holiday moved to the Monday) are left out.
• Leave taken or agreed in person can be recorded straight onto the register. Each person's page shows their leave balances and case files.

HR & Payroll: pay runs and payslips

• Pay runs (HR & Payroll, step 2 of 5): each month's pay worked out from the staff and their pay periods, with the EMP201's own PAYE and UIF maths, so the payslip and the return cannot disagree.
• A run starts as a draft that can be worked out again; closing it makes its payslips final (a correction goes into the pay periods and the next run).
• Each payslip is a PDF with what the Basic Conditions of Employment Act asks for: employer, employee and job, the period, hours, basic pay and overtime, PAYE and UIF, and the net amount paid; MAD's own UIF share shown for information.
• Send yourself a preview first, then send: each person gets their own payslip from hello@ with the PDF attached, one blind copy to Leonard. People without an e-mail address are listed, and every payslip can be downloaded.
• Checked against Matshoba's payroll schedule for September 2024: net pay R5 692.50 and R4 702.50, R210 to SARS.

HR & Payroll: staff, with pay by period

• A new HR & Payroll section in Central Command (step 1 of 5): everyone MAD employs or employed, with what uFiling and SARS need (ID number, position, hours, first and last day, the reason for leaving from uFiling's own list) and what is still missing from each record.
• Pay is kept by period (basic plus overtime), so overtime, a raise or a cut is a new period and past months keep what was paid. Periods may not overlap.
• The EMP201 now takes each month's pay from HR & Payroll, so the return, uFiling and (from step 2) the payslip agree. September 2024 works out at R10 500 and UIF R210.00, as filed.
• ID numbers are checked (13 digits, a real birth date, the check digit) and shown with the date of birth only. Bank account numbers are still not kept here.
• Coming next, in order: pay runs and payslips, then the uFiling file and EMP501, then VAT from Billing, then the API.

MAD's menus in one place, and cross-selling

• One list of MAD's platforms and every app's bottom bar (lib/estate/mad-menu.ts, served at /api/mad-menu): each app's own main item in the middle, the other MAD platforms beside it. Change a platform's words or a bar there and every app follows.
• The books pages show the bar: My Family Tree | MAD-BOOKS | TLOTLO, each with what it is for.
• The help bot stays closed until asked for, has a close button in its header, and closes by itself if it is not used within 5 seconds of opening; once someone taps, types or scrolls in it, it stays open until they close it.

The help panel shows its answers on iPhone

• The help bot's answers area has a fixed most-height instead of a flexible one: iPhone Safari still squeezed the flexible one to nothing, so the panel looked empty.

The family's reading e-mail: every age, and our own shelf

• The Saturday reading e-mail caters for every age: each free book says who it is for (children, young readers or adults).
• It also brings three books already on the family's own Family Library shelf, a different three each week, so it comes every Saturday even in a week without new free books.

Family gatherings: organisers and gifts sign in without Central Command

• Signing in with MAD-ID to a family gathering's organiser page or gifts page now opens that page: it was asking for Central Command, which is only for its owner. The page itself still checks its own list (the organisers, or the person's registration).

The family's weekly reading e-mail

• Saturdays at 08:00: the week's new free books in the Family Library, the top five with their summaries and reading level, by e-mail to everyone in the Family Library, to encourage reading. One e-mail each, from hello@, with a one-click stop that affects only this e-mail (migration 040).
• Nothing new in a week: nothing is sent; a week is never sent twice.

Family gatherings: entrance fee wording and the weekly RSVP report

• The registration form and the confirmation e-mail say Entrance fee (venue) on the day: the entrance pays for the venue.
• A weekly RSVP report by e-mail, Mondays at 08:00, for every open gathering still to come: registrations and the new ones this week, people by entrance fee, guests, relatives named for the tree, entrance fees expected, e-mails not yet confirmed, and each house, with the link to the full list. It goes to the gathering's report list, else its organisers, else Central Command's owners (the organisers asked for this instead of checking daily).
• A gathering keeps its report list apart from its organisers (migration 039): getting the report does not open the RSVP list.

Service Desk: settings, e-mail history, saved views and custom fields, as Heita

• Service Desk > Settings (Heita priorities, SLA plans, help topics, e-mail templates): response times per priority, the check-ins to a waiting customer, help topics with their priority, and the words of every Service Desk e-mail, all editable by the owner. Every change is kept with who and when. Until something is changed, everything works exactly as before.
• Help topics on the support form: each gives the new ticket its priority; staff can change a ticket's topic.
• Custom fields (Heita custom-fields): extra details on every ticket (text, a list, a date or a number), each change written on the ticket history; a field is switched off, never deleted.
• My e-mails (Heita notification preferences): each staff member chooses which Service Desk e-mails they get; the owner sees everyone's choices.
• Filters and saved views on the queue (Heita ticket-filters): platform, priority and help topic, saved for yourself or the team.
• E-mail history (Heita comms-history): every Service Desk e-mail with who it went to, which ticket, and whether the mail server took it (and why not); also from each ticket.
• The support form asks for an optional cell.

Service Desk: files on replies, and bulk actions

• Files with a reply or note (Heita upload_ticket_attachment): staff attach screenshots and documents in Central Command, 25 MB together; on a note they stay with staff. The customer is told a file is waiting on their ticket page.
• The customer can add files on their ticket page too, with or without words.
• Staff can remove a file (Heita delete_ticket_attachment); the ticket history says who removed what.
• Bulk actions on the queue (Heita bulk_ticket_action): tick tickets, then set their status, assign or unassign them, or (the owner only, with I am sure) delete them.

Service Desk: Heita's e-mail handling in full

• support@ is read every minute (Heita's sweep), so a sender gets their ticket number within a minute.
• Files sent with an e-mail (screenshots, invoices) are kept on the ticket, 25 MB each, for staff in Central Command and for the customer on their ticket page.
• Blocked senders (Service Desk > Blocked senders): an address or a whole @domain gets no ticket, no reply and no auto-response.
• A reply carrying a ticket number from someone who is not that ticket's customer or a collaborator becomes a new ticket, as in Heita; a collaborator writing in is recorded as themselves.
• Delivery reports are left out, and the mailbox is closed before signing out so GoDaddy keeps every message read: no e-mail is filed twice.
• Staff e-mails as Heita: every new ticket to the team; a customer reply to whoever has the ticket (the team while nobody has it); an assignment to the person assigned. They come from noreply@ and are answered in Central Command.
• Collaborators are copied one by one, each with a one-click unsubscribe from that ticket; every e-mail sent is written on the ticket's history.
• The help bots (website and every app) send the whole conversation with a ticket, with the person's name, e-mail, cell (optional) and the page they were on.

Book prices in rand and dollars

• Every book price shows rand and its dollar guide (R99 · about $10, on the R99 = $10 rule), charged in rand; each book page says so. The books in My Family Tree's Read tab show the same.

The help bot sits under each app's own menus

• The help bot's button and panel sit under an app's own menus and tab bar, so they no longer clash with them.
• On iPhone the help panel showed empty (Safari shrank its answers to nothing): fixed.
• An app with its own Help (My Family Tree's Help tab) can load the bot with no floating button; a tap outside the panel closes it.

Service Desk in its own menu, and help inside every app

• Central Command: Service Desk is its own section of the menu, with Open tickets, Overdue, Answered, My tickets, Closed, All tickets, New ticket, Reports and Canned responses; the tabs on its pages stay. The menu counts tickets waiting for us (red when any are overdue) and the ones assigned to you.
• The help bot inside MAD's apps: one script (www.myafricandream.net/mad-help.js) puts a Help button in My Family Tree, TLOTLO, ORC, Curio Earth and the Family Library, opening that platform's answers first and a ticket at support@ when a person is needed. Each app's own Help & support link opens it in place.
• The help answers (/api/help) and tickets can be reached from MAD's own sites only.
• support@myafricandream.net is read at GoDaddy's mail server (imap.secureserver.net): the mailbox is GoDaddy Workspace e-mail, not Titan.
• The Dibosto Dibosto books for MAD's apps (/api/books/list): My Family Tree's new Read tab sells them inside the app, through the MAD Store and Paystack's window, and the book's links appear there.
• Central Command > Accounting > EMP201: each month's PAYE, UIF (1% + 1%, to the R17 712 ceiling) and SDL (over R500 000 of payroll a year) from the payroll, its due date (the 7th, earlier over a weekend or holiday), past-due months flagged, Mark filed with the PRN, how to file a nil return on eFiling, and the staff list (name, pay and dates only). MAD has no staff now, so every month is a nil return.
• EMP201's back-filing list since September 2025 (nil months on both systems): each month's SARS EMP201 and Labour uFiling declaration, ticked separately.

The support mailbox says why it cannot sign in

• When support@myafricandream.net cannot be read, the Service Desk's mailbox job now gives the mail server's own reason (for example AccountNotFound, or a wrong password) instead of Command failed.

Service Desk, help pages and the MAD help bot

• Central Command > Service Desk: Heita's ticket module for MAD. Queues (Open, Answered, Overdue, My tickets, Closed, All) with search; each ticket's thread with Post reply (to the customer and collaborators by e-mail) or Internal note (staff only) and a status; priority with its due time, platform, who it is assigned to, linked tickets and collaborators; New ticket for a phone call; Reports; Canned responses.
• Heita's rules: a staff reply answers an open or overdue ticket, the customer writing again puts it back in our court (a closed one counts as reopened), a ticket past its due time becomes overdue, and a waiting customer gets one We're on it e-mail at 30 minutes and one Still working on it at 2 hours.
• support@myafricandream.net: every e-mail becomes a ticket, or is added to its ticket when it carries the ticket's number; auto-replies, bounces and lists are left out. The customer gets the ticket's number and a private link to follow it and add to it (opening it confirms their e-mail).
• Help pages (www.myafricandream.net/help): every platform's how to start and its questions and answers.
• The chat button on every page is now MAD's help bot: it asks which platform first, answers that platform's common questions, shows how to start, and opens a ticket right there when nothing helped. It replaces the Message us panel.
• Support (www.myafricandream.net/support): choose the platform and open a ticket.

Paystack figures fresh the moment something happens

• Every notice from Paystack (a payment, a subscription, a refund) clears the cached Paystack figures, so the Paystack summary and Analytics & BI show it on the next view instead of up to five minutes later.
• Read Paystack again now clears them too, so it really reads Paystack again.
• The Paystack page's figure cards are made once, not again on every view (three code-quality errors gone).

Analytics & BI: its two other outside calls kept in Valkey

• Analytics & BI was the one page Valkey had not sped up: it also reads Paystack's transactions page by page over the internet, and connects to every MAD site for its time and certificate, on every view. The Paystack figures are now kept five minutes and the site checks one minute.
• An error answer (Paystack or a site not answering) is never kept, so the next view tries again; its own database figures are still read fresh each time.

Other MAD apps can ask for a Confirm my e-mail link

• A signed way for MAD's other apps (ORC's clinic forms first) to have the website send someone the Confirm my e-mail link after their form is saved, so every MAD address is confirmed the same way and lands on the one confirmed list.

MAD's central "tell me when" lists, confirmed by e-mail

• One place on the website for every MAD "tell me when" list (migration 034), first TLOTLO's App Store and Google Play list, which until now lived only in the TLOTLO server's memory and was lost on every restart.
• A sign-up counts only once its e-mail is confirmed through the link we send; the address then also goes on MAD's confirmed list. An unconfirmed sign-up is deleted after 7 days by the store's morning job.

"Confirm my e-mail" on the website's forms

• One Confirm my e-mail link for every MAD form: opening it puts the address on MAD's confirmed list, so the Directory takes it in and Compose may write to it. The form's own job is never held up: a message still reaches the team, a booking still stands.
• Dimple's Joy: the contact form sends the sender a short confirm e-mail, and the booking and EFT e-mails carry the confirm link, unless the address is confirmed already.
• A buyer opening the download link in their book e-mail confirms their address too (since 1.35.0). The KingSol enquiry opens WhatsApp and keeps nothing, so it needs no link.

Valkey holds Central Command's four slowest calls; MAD-ID's confirmed e-mails marked

• Measured first (scripts/188): the four Central Command pages above 250 ms all wait on calls over the network, and now keep their answers in Valkey: Analytics & BI's site feeds and Websites' site checks for a minute, the Paystack summary's four Paystack calls for five minutes, and Comms' gateway status for two minutes (cleared at once when a connection is changed in API-MAN).
• The Directory now saves every e-mail MAD-ID has verified to MAD's confirmed list, so they are marked confirmed and Compose & send can reach them (the first fill marked none).

Valkey: MAD's one cache, and its page at valkey.myafricandream.net

• The website can keep answers it asks for again and again in Valkey (the open-source fork of Redis), in memory beside it, so the database is asked less. What it keeps is chosen from measured page times, not guessed.
• If Valkey is not there, stops or is slow, every page still works: it does the work itself and does not try Valkey again for 30 seconds.
• Central Command > Valkey (also valkey.myafricandream.net): whether it is up, its memory, how many answers it holds, how often it answered instead of the database, and how many it dropped when full. The cache itself is never reachable from the internet.

Family gatherings: "I don't know my house"

• Most people do not know their lineage house, so the list ends with I don't know my house: the registration goes through, the family tree's approvers place the person, and the organisers see them under House not known.

Only confirmed e-mails, across MAD

• MAD keeps one list of confirmed e-mail addresses. An address is confirmed when MAD-ID has verified it, when someone taps a family gathering's confirm link, or when a buyer opens the download link in their book e-mail.
• The Directory takes in only confirmed e-mails: a customer whose e-mail is not confirmed comes in by their numbers alone, if they gave any.
• Compose & send never sends to an unconfirmed e-mail; the Directory shows such addresses as not confirmed.

Family gatherings: confirmed by e-mail alone for now (no SMS costs)

• A registration is confirmed by the link in its e-mail alone: no SMS code is sent for now, so nothing costs SMS. The SMS code is ready and switches on with one server setting.
• SMS notices to the family named without an e-mail are held back for the same reason; the confirmation e-mail asks the person registering to tell them, and how they can have their details removed.

Family gatherings: guests apart from family, and every registration confirmed by SMS and e-mail

• The person registering says first whether they come as family or as a guest of the family. A guest's registration never goes to the family tree and opens no family gifts.
• Guests anyone brings have their own list: names only, for the organisers' RSVP list; never the family tree, no account, no messages.
• Only the person registering gives an e-mail. Family they add need a cell number (living adults) and an e-mail only if they have one; those with an e-mail get their own MAD-ID.
• Every registration is confirmed before anything happens with it: a 6-digit code by SMS to the cell, and a link to the e-mail. Then the MAD-IDs, the family tree's joining form, the notices to the family named and the consent record follow, once. A registration never confirmed is deleted after 7 days. When no SMS can go out, the e-mail alone confirms it, and the cell is shown as not confirmed.
• The family named without an e-mail are told by SMS that they were named and how to have it removed (POPIA section 18).
• The organisers' list, Central Command and the spreadsheet count confirmed registrations only, and show family or guest, the guests, and what was confirmed.

POPIA throughout: the privacy policy, the terms and family gatherings

• The privacy policy is rewritten for POPIA: who we are and our Information Officer, what we collect for each purpose and on what basis, family gatherings and family trees, children, information given by someone else, operators, security and breaches, how long we keep each thing, direct marketing, every right, and the Information Regulator's details.
• The terms have two new sections: Your Personal Information (POPIA), and Family Gatherings and Family Trees. The age rule now says how children are recorded: only by a parent or guardian, or with their consent.
• Family gatherings: no gift depends on agreeing to news and offers any more (consent must be freely given); the opt-in is separate and optional.
• Every adult someone names when registering is e-mailed, as POPIA section 18 asks: who named them, what we were given, why, who sees it, how long we keep it, and how to have it removed.
• The registration form shows how the details are used before anyone agrees; children's details need their parent's or guardian's consent.
• A registered person can see and delete their registration on their gifts page; only people who opted in go into MAD's Directory.

Family gatherings: the organisers' RSVP list, the family's tree named, made for phones

• The family's organisers open the RSVP list on their phone (www.myafricandream.net/<event>/organiser, with their MAD-ID): totals, each house, everyone registered with a tap to call or WhatsApp, and the list to download for Excel.
• The page says plainly that My African Dream takes no payments: entrance is paid to the family's organisers on the day.
• The My Family Tree banner names the family's own tree, shows one feature at a time (no more text on top of text), and has two clear buttons: add your family to the tree, and see what My Family Tree does.
• The house is chosen as Lelapa la hao (Lineage House #), numbered as on the tree.
• The memory gallery is an album on the family's Family Wall in My Family Tree, for the family's members; the page points there.
• The page has its own title for Google and sharing, and every field is large enough that phones do not zoom in when it is tapped.

Family gatherings: a registration page that feeds the family tree

• A family gathering can have its own page on the website (www.myafricandream.net/<event>), under the main navigation: the date, the venue, the prices, directions, and sharing to WhatsApp and Facebook with the event's own preview.
• Registering asks for name, surname, e-mail, cell and WhatsApp (with the country), home town, the family house and how many are coming, with the amount to pay at the gate. People can add their family too, each with how they are related.
• What they give goes to the family's tree as a joining form for its approvers: nothing reaches the tree until an approver lets it in. The person and each adult relative get a MAD-ID, and MAD-ID e-mails them to choose a password.
• A confirmation e-mail lists everything they registered and invites them to My Family Tree to check and correct it.
• Gifts for opting in, with a MAD-ID: a free book (with its fiction notice), a once-off PDF of the family tree after a family organiser confirms the person, and free days of My Family Tree to add the family.
• A memory gallery of the family's gathering pictures opens for people who registered, each picture to download.
• A cascading banner on the page shows what My Family Tree does.
• Central Command > Family gatherings: every registration, the totals per house and to collect, Confirm family for the tree PDF, and a spreadsheet download. Registrations go into the Directory, opt-ins into Consent, and are deleted after the gathering's purge date.

Prices in other currencies charged in rand, and the R1 card check given back

• A price set in USD, EUR, GBP, CNY or INR is charged in rand at the day's exchange rate (the European Central Bank's reference rate). The order keeps the price, the currency and the rate used, and the store's price list says what each foreign price is in rand today.
• Foreign-priced plans follow the rate: each morning (07:15) the store takes the day's rates and moves every such Paystack plan to today's rand amount, so each subscriber's next charge uses the new amount.
• The R1 card check that starts a free period is refunded as soon as the plan behind it is set up; the morning job tries again for any refund Paystack did not take. A refunded card check gets no invoice.
• TLOTLO's USD, EUR, GBP, CNY and INR plans are open, with the same 90 days free for a first subscription.
• Central Command > Automations shows the new morning job.

The TLOTLO app loads its card through the MAD Store

• TLOTLO's plan (R50 a month) is open in the MAD Store: the app at app.tlotlo.app loads a card with the MAD Store's checkout (an R1 card check), the first 90 days are free and Paystack bills from day 91.
• Someone whose TLOTLO plan ended gets no second free period: their plan starts on the day they come back.
• Only the R1 card check starts a plan after the free period, so a full first payment is never billed twice.

Billing: Items, Contracts, Reports, menu counts, and suspension switches the app off

• Items: the MAD Store catalogue as Billing's item list (one price list for every site), with New invoice with it on each item.
• Contracts (KESHO's): suppliers, clients, partners and ESD sponsors, with dates, value a year, discount, the signed document and whether it is in force. The Billing Overview warns 60 days before one ends, and in red when one has passed its end date but is still marked active.
• Reports (KESHO's): this month's invoiced, received, credited, owed and overdue; the last twelve months (received split into card and EFT or cash; credit notes never counted as money in); and the activity log of the last 200 billing actions.
• The menu shows counts on Subscribers and Billing: how many kinds of thing need you, red when one is urgent, refreshed every minute.
• An EFT customer's access now follows their payments in the app their product belongs to (My Family Tree first): paid gives access to the end of the month paid for, a suspension on the 3rd closes it, a payment or Restore opens it again, and ending the line cancels it.

Billing: invoices, quotes, credit notes, receipts and the EFT month

• Billing has KESHO's documents: Invoices, Quotes and Credit notes, each a tab with a New button. A document is made for a person in the Directory (or typed), with lines from the MAD Store catalogue or typed, totals as you type, VAT included.
• Invoices take the next number in MAD's one invoice series (MAD-000123), so the numbers stay unbroken; quotes are Q-, credit notes CN-, receipts R-.
• Every document has Send first (the customer gets a signed link to view, print or save it as a PDF), the step it waits for (Issue, Record payment), and Actions ▾ last with Sage's list: Preview, Print, Email…, Edit, Create Receipt, Create Credit Note, Create Invoice from a quote, Copy, Mark Accepted or Declined, View History, Void.
• Statuses read as in KESHO: Draft, Quoted (a draft e-mailed), Issued not sent, Sent, Part paid, Overdue, Paid, Credited. A credit note lowers what is owed but is never counted as money received.
• Recurring (EFT): add a customer who pays by bank transfer and their monthly amount. The EFT month then invoices them on the 25th, reminds them on the 1st and 2nd by e-mail and SMS, and suspends them from 18:00 on the 3rd if no payment is recorded, telling you by SMS. Recording their payment restores them. It is OFF until the owner switches it on, and shows what it would do each day.
• The Billing Overview adds overdue invoices, invoices never e-mailed, drafts and quotes waiting for an answer.
• From GYTE: each EFT customer is either e-mailed their invoice at once, or held for you to check first (GYTE's Auto inv), and the Comms pause switch stops every billing e-mail and SMS, the EFT run's included; while it is on, invoices are still made and reminders wait until sending runs again.
• Statements (KESHO's Bill As): one line per customer with what was invoiced, paid, credited and is owed, aged by due date (not yet due, 1–30, 31–60, 61–90, 90+ days) in colour. Send statement first e-mails every open invoice with its link and the total owed.

Subscribers: KESHO's module for MAD's subscribers

• Central Command has a Subscribers section of its own, as in KESHO: Overview first (what needs you: failing cards, renewals more than 3 days late, who is ending in the next 7 days, active subscribers with no payment recorded), then Active, Card failing, Ending, Cancelled and All.
• Each row has an Accounts column with what the accounts team needs to know, worst first: card failing, renewal late, renewal off, what they have actually paid in all, not yet in the Directory.
• Send first on every row sends the card link: Paystack's own e-mail to load or update the card. Actions ▾ last: the card, the card link by SMS, the Directory record, payments and Paystack.
• Each subscriber has a card: their state in colour, one row of actions with the next step highlighted, every payment with its invoice, and their history.
• The menu has Subscribers and Billing as sections of their own.

Compose: one message to people in the Directory

• Central Command > Comms > Compose & send: write one SMS or e-mail and send it to people in the MAD Directory, as in KESHO's Notify. Choose any mix of everyone, Directory groups, people you pick and numbers you type; doubles, opted-out people and people without that kind of address are taken out.
• Preview shows exactly who it reaches, how many are customers, and how many SMS parts it costs, before you confirm. {{name}} becomes each person's first name.
• Every message goes through MAD Guard: nothing is delivered while that system is sandboxed, nobody gets it twice, opt-outs are honoured. Messages to customers from staff wait for the owner, who approves the whole batch with one click on Sent batches.
• The Directory, its groups, templates and the opt-out list are one click away from Compose, and the Directory is in the Comms menu.

Billing in line with KESHO: Overview first, Send first, renewals matched, one table and jobs board

• Subscribers & bill runs opens on an Overview of what needs you (failed charges, payments that don't match, a bill run that stopped or didn't run), then Subscribers, Paystack payments and Bill runs as tabs, as in KESHO.
• Every Paystack payment row has Send first: it e-mails the customer their invoice, with copies if you like, and records who sent it and when. Actions ▾ comes last, in Sage's order: Preview, Print, Email…, View in Paystack, Copy reference, View History.
• Renewals that Paystack charges on a plan's own date are now matched to the customer's subscription instead of showing as unmatched, and every bill run looks again at the last 45 days of unmatched payments (KESHO's fix of the same day).
• Every table in Central Command has the one VOIMAR and MAD table standard: Search anything, Export to Excel, and pages with a summary of how many rows are shown.
• Automations & workflows now uses the same jobs board as KESHO, GYTE and HEITA, with each MAD timer's live state in the job's panel. MAD's list lives with the others, so the estate map can show every system's jobs.

Fingers on the Money: the fiction notice in the book

• The PDF and EPUB of Fingers on the Money that buyers download now say on the copyright page that it is a work of fiction: inspired by a real life, but its characters, events and dialogue are the author's own invention, and it is not a biography or a factual account of any person, family or event.

Automations & workflows in Central Command

• Central Command > Systems > Automations & workflows shows every job MAD runs by itself, across all the apps: the nightly backup and bill run, the health checks, the family tree checks, the code vault, book delivery and more.
• Each card shows what the job does, whether it is running (green), has failed (red) or has stopped (amber), and when it runs. Scheduled jobs (a clock) run on a timer on the MAD server; triggered ones (a bolt) run inside an app when something happens, like a payment.
• Click a job for the full detail: when it last ran and runs next, how it works step by step, what it reads and changes, what it sends, how it is kept safe, and where to see its results.
• A timer on the server that is not described yet still shows, marked so, so nothing runs unseen.

Clean covers for Money Moves and Men Dogs, Sex Gods

• The covers of Money Moves and Men Dogs, Sex Gods no longer carry the image tool's mark in the corner: on the books pages, in the free summaries, and in the PDF and EPUB that buyers download.

Fingers on the Money's summary: its inspiration, as fiction

• The free summary of Fingers on the Money names the real life that inspired the novel again, and says plainly that it is a work of fiction: its characters, events and dialogue are the author's own invention, and it is not a biography or a factual account of any person, family or event.

Short book addresses, and the clinic's own icon

• Old links to www.myafricandream.net/books now open the short address: books.myafricandream.net/happy-pill rather than books.myafricandream.net/books/happy-pill. Download links from earlier emails keep working.
• ORC Clinic has its own line icon in the menus, the footer and Central Command, drawn from the clinic's logo. It showed the family tree's icon before.

The books have their own address, and a free summary each

• The Dibosto Dibosto books now live at books.myafricandream.net. The old www.myafricandream.net/books links go straight there, and the emails with download links use the new address.
• Every book has a free summary to read first: a short PDF with the synopsis and what is inside, next to each Buy button and on the book's page.
• The About page no longer offers a book for free: Money Moves now has its summary and a Buy button (R99).
• The covers are shown whole, never cut off, on each book's own colours with its serif title, the same look as the books' share images.
• The top menu is in a new order: My Family Tree, MAD-Family, MAD-Shop and Dibosto Dibosto to the left of the logo; ORC Clinic, Dimple's Joy, Tlotlo.app, Curio.earth and About to the right.

Book sales in Central Command

• Central Command > Websites > Books and library shows the book sales: copies sold per book (in the last 30 days and in all) and the money taken, from the MAD Store's paid orders.
• Its downloads count each download of a paid book, PDF or EPUB; the old free form's and rabotapi.org's sign-ups are shown as before the sale.

The Dibosto Dibosto books are for sale, R99 each

• The six Dibosto Dibosto books are now sold on the website, R99 each, from MAD-BOOKS: pay by card through Paystack and the book downloads straight away as a PDF and an EPUB (for Apple Books, Google Play Books, Kindle and any e-reader), and the links come by email too, for 30 days.
• The books are the new MAD-BOOKS editions: edited, with a contents page, the MAD-BOOKS and My African Dream logos, and the reading edition in A5.
• The free download form is closed. Old download links now open the book's page, where it can be bought. Each download is recorded against its order, PDF or EPUB.
• Prices are set in Central Command (Catalogue & prices): the books are MAD Store products like every other sale.

Central Command on the one PWA frame

• Central Command now uses the same frame as every MAD and VOIMAR app: the whole menu in a MAD ink drawer on the left, the section you are in on the right, Back and Home at the top, and five tabs at the bottom on a phone (Analytics, Approvals, Notices, Websites, Security).
• On a computer the left menu stays open as a column and the right one starts folded; each remembers how you left it. On a phone both slide in from the edge handles and close on every new page.
• Books and library: its tables scroll inside their boxes on a phone instead of pushing the page sideways.

Spam protection and Fraud and attacks

• Every public form (books download, Dimple's Joy contact and booking, shop checkout) has spam protection: a hidden trap field, a too-fast check and a limit per address an hour. Nothing for a person to do.
• Central Command > Security > Fraud and attacks: payments that do not add up (Paystack paid a different amount, repeated failed card payments, many unpaid orders), forged payment notices, spam blocked on every MAD form, book sign-up floods, and every data export with who took it.
• Forged payment notices, scheduled jobs called without the right key, and data exports are now recorded (no visitor's internet address is kept).

Email security update; security policy reports

• Email sending moved to Nodemailer 10 (a security fix for the old version); every email still goes through MAD's own mail server.
• Central Command has Security policy reports: what each MAD site's new content security policy would block, as browsers report it, before it is switched on. The reports keep no IP address, no query string and nothing about the visitor, and go after 30 days.

The founder's letter, with its title

• On About, From our founder shows the letter's title again, Open Letter to the Black AfriKan Child & Youth, set in the same style as the rest of the page.
• The letter is now last on the page, above the footer, after Money Moves.
• Libraries with known security problems updated, from a security check of the MAD estate (5 Nov 2026).

Country codes always visible

• The country list on phone fields shows the code first (+27 South Africa), so it is never cut off.

Phone numbers from any country

• Every phone field (books download, Dimples Joy booking, the KingSol enquiry) asks the country first, with its code, and shows an example number in that country's format.
• Numbers are kept in one international form, for example +27 82 123 4567.
• The admin number fields show the format too.

From our founder: one clean letter

• About's From our founder is one clean letter: no title line, no numbers, the founder's words of 6 June 2020 word for word, signed at the foot.
• The home page links to it again.

The founder's letter, without its long title

• On About, From our founder keeps the letter of 6 June 2020; its title line, Open Letter to the Black AfriKan Child & Youth, is gone.

The founder's quote, neatly set

• On the home page, the line from the Open Letter and where it comes from each start on their own line, on one left edge.
• From our founder opens: My African Dream has been founded with one belief (on the home page and About).
• About's From our founder holds one thing only: the founder's Open Letter (the short introduction is on the home page).

The baobab, one letter, and the founder on the home page

• The hero banners show the baobab from the My Family Tree mark under its terracotta sun.
• About has one letter only, the founder's Open Letter, with a short introduction in our own voice; Money Moves is the last section, above the footer.
• The home page ends with From our founder in short, a line from the Open Letter, and a link to About.

From our founder

• The About page has a short introduction from the founder: why My African Dream exists, what each venture does for the African family, and the dream for Africa and its Black youth, and one letter: his Open Letter to the Black AfriKan Child & Youth (6 June 2020), word for word.
• It carries the same belief as Curio Earth's founder's vision: technology should not replace human connection, it should inspire it.
• The About page offers Money Moves, the founder's book, free (through the books form), with lines from it.
• The My Family Tree page carries the founder's vision: Our families remember. Now our families keep.
• New MAD hero banners on About, My Family Tree, Shop and Contact: a dark band with the baobab from the My Family Tree mark under its terracotta sun; the founder's letter now sits on cream.
• The home page ends, above the footer, with From our founder in short, a line from the Open Letter, and a link to the About page.

The MAD link: the Ndebele strip and the MAD logo

• The approved Ndebele strip runs down the left of every page, the MAD link across the whole digital estate, and the MAD logo sits at the foot of the page. Nothing else about the site changes.
• TenderCop no longer shows on any public MAD page (it keeps its own stand-alone coming-soon site).

Families as they really are

• The home page and the My Family Tree page lead with My Family Tree's promise: every child belongs on the tree. Mothers as the root of their household, fathers of children with several mothers, step-families, adoption and fostering, and two mothers or two fathers, recorded truthfully and without shame, with a link to the guide.

Help building a family tree, and Apostle King Sol's page

• My Family Tree's page shows the new services: a 2-hour online consultation (R1 500) with MAD's Chief of Families and Culture, a tree built for your family (R5 000, meetings not included) and technical help on quote, in the MAD Store.
• Apostle King Sol's page moves here from rabotapi.org, still unlisted: www.myafricandream.net/kingsol.

ORC Bookings, and Books and library

• ORC Bookings: the clinic's own appointments (no Cal.com): today, the week ahead, the last 30 days by outcome and service, and a follow-up centre: visits for the practitioners to mark (with an email reminder to the clinic), and patients to rebook after a missed or cancelled visit or to check on a week after it, each with a WhatsApp message ready and a Done with a note.
• Books and library: each Dibosto Dibosto book's downloads from the website and the Family Library, the form's sign-ups (and rabotapi.org's), and who in the family uses the library: visits, books opened, talks, Dad's books, last seen, and what is read most.

An old book link leads back to the form

• A book link used without the form, or after 24 hours, goes back to the form on the books page (it had pointed at the server's inside address).

Books open only behind the form

• The six books are no longer public files: the form records who asks, then gives links that work for 24 hours, one per book, saved under the book's own title (Safari had saved the wrong book). Each download is counted; Central Command shows how many and which book leads.

MAD-Family links to its public page

• MAD-Family on the website goes to the packages on the My Family Tree page (the MAD-Family page in the app is for members).

Central Command's icon on the iPhone

• On the iPhone: Central Command's pages name their own home-screen icon (cmd-apple-icon) and title (CMD), so Safari never reuses MAD's icon or name.

Central Command's own icon

• Central Command has its own app and browser icon, the MAD logo reading CMD: a mirrored D, a tall M in the centre, the D. On cmd.myafricandream.net only; the website keeps MAD's.

The website follows the brand directory

• Home page: Our Digital Assets shows every public product from MAD Brands, as Subscription services (My Family Tree, MAD-Family, curio.earth, tlotlo.app, TenderCop coming soon) and Digital assets (the clinic, dibosto dibosto, Dimple's Joy, MAD-Shop).
• The top menu and the footer list the same products, so the website, MAD Brands and Central Command never disagree.
• Change a product in Central Command > Brand and the website follows within 5 minutes.

Central Command on its own address: cmd.myafricandream.net

• Central Command now lives at cmd.myafricandream.net, with its own sign-in and its own app (PWA): add it to the home screen from there.
• www.myafricandream.net/admin goes to cmd, so the website's app stays the website and Central Command's stays Central Command.
• A member's sign-in from the website still happens on the website; approval and hire emails link to cmd.

Central Command: the sidebar logo 30% smaller

• The MAD logo at the top of the left sidebar is 30% smaller (12rem to 8.4rem wide), still centred.

Bank statements: the right closing balance from FNB's own download

• FNB's own CSV lists the newest transaction first: lines are now kept oldest first, so each month's closing balance is the last line's balance (it showed the first line's).

Bank statements: a download that spans months is split per month

• FNB's own CSV download can cover several months: each month is now kept as its own statement, and a month uploaded again replaces that month, so no line counts twice.
• The uploaded file's name is kept with long numbers cut to their last 4 digits (FNB names its download after the account number).
• FNB's R8.00 declined-transaction fees are tagged as bank charges at 15%, and its R0.00 notices are skipped.

VAT on bank lines, the way MAD's accountant does it

• Bank statements: every line has a VAT rate, 15% or 0%, set as Matshoba rates MAD's lines: 15% for FNB's fees, airtime, electricity, tolls, equipment and local suppliers with a tax invoice; 0% for foreign subscriptions, fuel, food and personal spending, cash, levies, SARS, transfers and loans; rent exempt. Change any line's rate by hand.
• Each month shows the VAT in money out (input) and in money in (output).
• VAT 201: a period with bank statements is worked out from them (field 1 sales, field 3 exempt rent, field 15 input VAT, field 20), with slips from Books added; otherwise from the books as before.
• FNB statements that came as PDF: tools/fnb-pdf-to-csv.py in mad-coder turns them into the CSV to upload, checked against the statement's closing balance.

Bank statements, read and reconciled

• Accounting > Bank statements: each month's FNB statement uploaded as CSV, read line by line, tagged by its description where it is clear (Paystack payouts, bank fees, SARS, hosting), the rest tagged by hand.
• Each month checks what Paystack paid into the bank against what the books say reached it, and shows money in and out by tag.
• No bank feed, no Sage and no bank login: long numbers are cut to their last 4 digits and no account number is kept; the PDF stays on MAD Repo in Banking.
• The tax calendar reminds you on the 5th of every month to upload last month's statement.

Paystack summary, tax repository and tax reminders

• MAD-Shop > Paystack: the balance, payouts to the bank, what came in with Paystack's fees, subscriptions, refunds, disputes and the latest payments, by site (All, ORC, TLOTLO, Family, Dimple's, Curio, Others). Read-only.
• Accounting > Tax repository: every company and personal tax document, where it is on MAD Repo, and when to renew it; red when due, green when current.
• The tax calendar includes the monthly UIF declaration, your own ITR12 and provisional tax, and says what each needs from you; the bell reminds you 30 days ahead.
• The statutory profile takes the bank (never its account number), the public officer, the Labour UIF reference and where the director's salary tax is handled.

Concession invoices emailed

• Each concession invoice is dated the day it is issued, which becomes the person's subscription anniversary, and shows the period, R 0,00 to pay and Balance due R 0,00.
• Issuing emails each person their invoice from hello@, with a copy to hello@.
• Every My Family Tree invoice notes what the package includes and its limits; a sponsored one says it is for the person's own use.

Concession invoices

• Accounting > Concessions: everyone My Family Tree sponsors gets a monthly invoice for Heavyweight at R999 less 100%, numbered with every other invoice, and the value given in total.
• Each sponsored person sees their invoice in My Subscription, marked Sponsored, 100% discount.
• Every invoice carries the Ndebele band down its left side.
• Dollar prices beside rand in the MAD Store.

My Family Tree tiers

• Lightweight R99 (500 people), Middleweight R699 (2,000 people) and Heavyweight R999 (no limit, MAD-Family for 6): a year is 10% off.
• Upgrades and downgrades: a new package stops the old one on Paystack, so nobody pays for two.
• Subscribers can cancel from My Subscription; it runs to the end of what is paid.

Legal register

• Legal in Central Command: every contract, licence, policy and company record MAD keeps, who it is with, when it was signed and renews, and a link to the signed copy on MAD Repo. Archived, never deleted.
• Renewals show in the tax calendar, and the next 90 days are flagged at the top of the register.

Accounting: VAT 201

• A draft VAT 201 for each period, following MAD's VAT category: standard-rated sales, output VAT, input VAT from expenses, and what is payable or due back. Checked by the owner and filed on eFiling.
• A tax calendar: every return and payment due in the next twelve months (VAT 201, EMP201, EMP501, provisional tax, ITR14, CIPC annual return, COIDA), from the statutory profile, which now has the date of incorporation.

Accounting: books

• Books in Central Command: MAD's sales month by month from the Paystack ledger, with gross, VAT (once VAT registered), Paystack fees and net to the bank.
• Expenses in Books: entered from each slip with its supplier, category, amount and VAT, input VAT only with the supplier's VAT number; a removed line stays, marked removed.

Invoices for renewals

• Renewals Paystack charges on a plan's date get their invoice too, and show in the customer's My Subscription.
• Central Command's billing page opens the invoice for every successful payment.

Invoices for every payment

• Every paid order has an invoice, numbered in order the first time it is opened: a tax invoice with VAT once MAD's VAT number is in the statutory profile, a plain invoice until then.
• Customers open theirs from the signed link in their My Subscription, and print it or save it as a PDF.

Central Command: Accounting

• Accounting in Central Command, starting with MAD's statutory profile: company details, CIPC number, SARS income tax, PAYE, SDL, UIF, COIDA and VAT, each checked against the format the authority issues, and every save kept as a version.
• The Accounting menu shows what comes next, in order: invoices and statements, VAT 201, UIF & COID, provisional tax, annual returns, books, the tax repository and bank feeds.

MAD Store: invoices for the applications

• The applications can show each customer their own payments (date, what, amount, status, reference) on their My Subscription page, asked for with the store's signature. No card details are kept or given.

My Family Tree: the Family package

• The Family package: R399 a month for 6 people, you included. The people you add never pay.
• Paying for a year takes 10% off: R1,069 for one person, R4,309 for the Family package.

My Family Tree: price per person and devices

• The base package is R99 a month per person, on 2 devices: a computer and a phone. Outside South Africa it is $10 a month per person, charged in rand at the exchange rate on the day.
• Every other package shows an approximate dollar price on the same ratio.

My Family Tree: every feature and the base package

• Everything in the base package: every feature of My Family Tree on one list, for R99 a month per person, on 2 devices (a computer and a phone). Outside South Africa it is $10 a month per person, charged in rand at the exchange rate on the day.
• Every other package shows an approximate dollar price on the same ratio. All packages are charged in rand, at the exchange rate on the day.

My Family Tree: native African

• The My Family Tree page now leads with what makes it different: designed in Africa, for African families, our culture and our traditions.
• A new section shows what is built in: houses and wives, relation words in the family's own language, names carried from elders, surnames over the years, both sides of the family, and remembering those who passed on.

Version numbers, release notes and menu icons

• Every page shows its version in small grey letters in the bottom-right corner: the company site, Dimple's Joy, MAD-Status and Central Command. Tap the number to see what changed, or tap refresh to reload the page.
• What's new: www.myafricandream.net/releases lists every version of this site, newest first.
• Central Command > Versions and release notes: every MAD app's version, when it was last deployed and its release notes, on one page.
• Every menu item has a simple line icon next to its name: the company site menu, the Dimple's Joy menu and the Central Command menu.
• Dimple's Joy shows only its own icon in the browser tab and on the home screen, and its link preview shows its own address, dimples.myafricandream.net.
• Other MAD systems can read this site's version at /api/version.

First numbered release

• The company site, www.myafricandream.net: every MAD product, About, Contact, the legal pages, the free dibosto dibosto books, the My Family Tree page, and one shop where each product's plans are paid through Paystack.
• Dimple's Joy, dimples.myafricandream.net: jumping castles, VIP toilet trailers and caretakers for hire, with a booking calendar, a cart, and payment by Paystack or direct EFT.
• MAD-Status, status.myafricandream.net: is every MAD system working? Open it on your phone and add it to your home screen, and it works like an app.
• One MAD-ID for everything: Sign in and Create MAD-ID on every page, with no separate passwords.
• Central Command, cmd.myafricandream.net: one panel for the whole MAD estate. Analytics, approvals, people and consent, SMS and email, the shop, Dimple's Joy bookings, subscribers and bill runs, every website, the brand, AI modules, the server, backups, security and notifications.
• Everything runs on MAD's own server in South Africa, with MAD's own database and mail.

Subscriptions and the My Family Tree page

• The shop sells subscriptions through Paystack, monthly or yearly, with renewals kept in the same order list as every other sale.
• My Family Tree has its own page on the site, with its plans and payment.
• On 2 Nov the shop moved to MAD's own database on MAD's own server.

Security update

• The site's framework, Next.js, was updated to close serious security holes. Nothing changes for visitors.

Dimple's Joy on its own address, and MAD-ID for the admin

• Dimple's Joy moved to dimples.myafricandream.net with its own look: Home, How It Works, Who We Serve, Business, ESD/ED, Consulting, Contact, Shop, a cart and Book Now. The old myafricandream.net/dimples-joy links still work.
• Customers pay in full before anything is booked, with transport worked out from the nearest base. Direct EFT is offered as well as Paystack.
• The admin is opened with MAD-ID. Owners change things directly; changes to money matters made by staff wait for the owner's approval.
• Geist is the site's typeface.

Dimple's Joy hire site

• Dimple's Joy: jumping castles, a VIP toilet trailer and a caretaker for hire, with a booking calendar and online payment.
• An indemnity and damages agreement comes with every order.
• Icons for browser tabs and phone home screens, and a theme colour for phones.

One shop for the products, and the admin overview

• One shop for Curio Earth, ORC Clinic and Tlotlo: pick an app by its logo, then see only that app's items.
• The admin overview: revenue, payments, site health and each product site's own numbers.
• The MAD share card for links, the favicon and installable app icons.
• An old payment path that could not safely take money was removed.