Course 4.2 · Curriculum 2026.1
The done rule: why an agent may not mark its own work complete
The course. A change may be called complete only after end-to-end verification under the real user’s permissions, with the test data deleted.
- Estimated effort
- 3 hr
- Lessons
- 26
- Modules
- 5
- Material
- 3 hr
Estimated effort is the sum of the lesson and lab times in the course outline, for this version of the course.
This course is planned and not on sale. The curriculum below is the plan, and it may change before the course opens.
See the courses on sale01What you will learn
7 capabilities, stated as things you can do
Each one is what you should be able to do at the end, not what the course covers. If an outcome is not testable, it is not an outcome.
- State the done rule precisely, including the permission clause and the cleanup clause.
- Explain why an administrator’s successful test proves nothing about a standard user.
- Run a verification pass as the real user, on desktop and on a phone.
- Create test data deliberately and delete all of it, every time.
- Report work as pending verification when a permission-scoped test is impossible.
- Design an agent workflow where the agent cannot set the done state itself.
- Review someone else’s claim of completion and find what was not verified.
02Curriculum
5 modules, 26 lessons
Every lesson shows its length and its type, from the course outline.
5 modules · 26 lessons · 3 hr of material
Four clauses. Verified end to end, as the real user, on the real devices, with the test data deleted. Each clause exists because of a specific failure.
- VideoAI cannot mark work doneThe differentiator is not that an agent writes Apex. It is that the agent is not permitted to decide whether the work is finished.Preview8 min
- VideoThe permission clause: as the real user, not as an admin7 min
- VideoWhy an administrator’s successful test proves nothing about a standard userField-level security, sharing and record types all behave differently. A test run as an administrator is a test of the administrator’s access.7 min
- VideoThe cleanup clause: create it, then delete all of it6 min
- ReadingFour clauses, one rule, stated precisely5 min
- QuizCheck: the rule, stated7 min
Field-level security, sharing and record types all behave differently by user. A test run as an administrator only tests the administrator’s access.
- VideoField-level security, sharing and record types behave differently by user7 min
- VideoMatching a permission set versus logging in as6 min
- VideoOn the real devices, including the phone7 min
- VideoCreate the test data, then delete all of it6 min
- LabLab: run the same flow as an admin and as a standard user9 min
Sometimes there is no permission-scoped way to test a change. Saying so is not a failure of the work; calling it done anyway is.
- VideoPending verification: the honest state7 min
- VideoWhen a permission-scoped test is genuinely impossible6 min
- ReadingSaying so, instead of calling it done5 min
- LabLab: write a pending-verification note that says what is missing9 min
- QuizCheck: as the real user8 min
Building the rule into a workflow so it cannot be skipped by a tired person at 6pm on a Friday.
- VideoA workflow where the agent cannot set the done state itself7 min
- VideoWho holds the done button, and why it is never the agent6 min
- LabReviewing a completion claim, and finding the gap9 min
- ReadingWhat “verified” has to include before a reviewer signs it5 min
- QuizCheck: the workflow7 min
The best proof point in the portfolio: a fix, fully designed and quantified, that stayed unshipped until a human signed off on it.
- VideoA fix, fully designed, deliberately not shipped“Not deployed. It changes the reported contract value on a customer-facing progress claim, so the controller should confirm first.”7 min
- VideoWhy a progress-claim number needs the controller’s word, not the agent’s6 min
- ReadingThe line between technically correct and safe to publish5 min
- LabLab: write the confirmation request a controller can actually answer9 min
- QuizCheck: the done rule9 min
04Before you start
What you need first
Assumed knowledge and setup
- Course 4.1.
- An org with at least two user profiles, so the permission clause can be tested.
- This course is short and is the one to take first if you only take one.
Before this course
Courses often taken next
- 4.3 · The seven design gates, and shipping systems instead of dashboards
- 4.5 · Verification: logging in as the real user, and cleaning up after yourself
- 4.9 · The autonomous task loop: the org is the queue and the completion target
Each is a separate course, bought on its own.
05Who teaches it
Elliot Saha
Co-founder, Chief Technology Officer
Platform architecture, custom Apex and Lightning Web Components, AI systems, and the Academy platform itself.
06Reviews
No learner reviews yet
This course has not been taken by enough people to publish an honest rating, and we will not print invented quotes on a page that sells verification discipline. Here is what we can evidence instead.
- Assessment
- Lesson checks onlyThis course carries lesson checks and issues no certificate.
- Curriculum version
- 2026.1You enrol into a version. Content changes do not move you mid-course, and your required-lesson count is snapshotted at enrollment.
- Refunds
- 14 daysAn individual purchase can be refunded within 14 days if you have completed less than 20% of the lessons. Team seats are refundable before they are assigned. From the Academy terms.
Start 4.2
This course is in development and not yet open for enrolment. The courses open now are listed in the catalogue.
- 3 hr estimated effort, labs included
- A ShareCo certificate is not a Salesforce certification