Level 4 taught an owner to govern AI across the business. Level 5 is about building the part that acts. A drafting assistant suggests; an automation does. It books an appointment, sends a follow-up, writes to the customer list or prepares an invoice, and when it is wrong the error has already reached a customer or the books by the time anyone looks. This level teaches automation whose authority is bounded in writing, whose every action is recorded, and whose failures are caught by design rather than by a complaint. No coding is assumed or required.
The first three modules set authority and build the first chain. Module one places every proposed automation in one of three bands, suggest, act inside the business or never act outside without a person, names the three ways an automation ends up doing more than anyone meant, writes the authority register before anything is built, and lists the acts that never go to an automation: money, refunds, prices, claims, signatures and filings. Module two chooses a first automation that cannot hurt anyone, writes its limits as you would to a new employee, runs the smallest useful version beside the manual process, and agrees in advance what decides whether it is kept, narrowed or switched off. Module three chains enquiry, booking and follow-up with a person approving what leaves the business, and carries the federal calling-hour, do-not-call and consent rules, the ruling on AI voices, commercial email rules, bot disclosure and call recording into every channel, with California as the named worked example.
Modules four to six are the connections. Module four draws every system and supplier an automation touches, specifies each boundary by direction, fields, data class and limits, makes "do nothing and tell someone" the default for a bad record, and shows why card data is governed by contract and why health information usually falls outside HIPAA for an ordinary small business. Module five starts accounting and customer connections read-only, earns each write one at a time, keeps the automation to proposed entries a person commits, leaves the trail a bookkeeper, preparer or attorney still needs, and never lets it take a tax position, decide an entity question or answer a wage question. Module six marks where an automation stops near payments, refunds, payouts and bank changes, separates who prepares from who approves even in a one-person business, holds a changed payee until a person verifies it on a number already held, and keeps the credential that moves money out of the automation.
Modules seven to nine are human control. Module seven designs a gate card that produces a decision rather than a reflex, explains what the research on automation bias and complacency found, sizes gates to a real working day, and measures whether a gate catches anything. Module eight gives every automation its own identity and never the owner's login, applies least privilege to the tools a small business actually uses, keeps keys out of prompts and messages, and closes every credential when someone leaves. Module nine designs a stop anyone may use, a manual route that is written down and rehearsed, an honest estimate of how long the business can run without each automation, and a stop-and-recover checklist.
Modules ten to twelve are defence and observation. Module ten threat-models enquiries, invoices, reviews, resumes and web pages as carriers of instructions, from the defender's side only, and explains why prompt injection is a residual risk that controls reduce but no product removes. Module eleven specifies the action log, what it must never hold, a record someone can follow six months later without the tool, and retention, integrity and secure disposal. Module twelve finds failures no error message announces, retests after a model, vendor, price or policy change, watches spend before the invoice arrives, and sets alerts a small business can act on.
Module thirteen responds when an automation has already acted: stopping it, freezing the log, scoping every run, reversing or compensating, identifying the recorded notification duties to take to an attorney, telling customers plainly, and making the change before restart. Module fourteen measures time, quality, cost and upkeep against the business's own baseline, refuses savings counted twice and work moved onto the owner, explains why no published study can set the target, and takes a pilot to a recorded rollout decision. The capstone is the Automation Implementation Project for a fictional small business. The level ships with a printable workbook and fourteen templates, and the examination draws forty scenario questions from a reviewed bank.
Everything here is professional education. It is not legal, tax, accounting, employment, privacy, security or insurance advice, and it does not replace an attorney, a tax professional, a bookkeeper, an insurance broker, a licensed professional where a trade or profession requires one, or the law of your state. Completing the level earns an independent educational certificate issued by AI Coalition Network with a public verification page. It is not a business licence, a professional qualification, a security credential or a government approval, it carries no professional education hours, and it satisfies no licensing or compliance requirement.