Appendix: traceability
This appendix links each part of the manual to the product design and to the evidence behind it. It is for the release record, not for day-to-day use.
- The automated acceptance evidence for v0.1.0-rc.2
(
docs/testing/MooTidy_Pre_Pilot_Acceptance_v0.1.0-rc.2.md) still covers behaviour that did not change in rc.3. - The rc.3 changes are traced to the founder UAT findings in
docs/testing/MooTidy_Founder_UAT_v0.1.0-rc.2.md, each fixed in production and human-verified before the rc.3 freeze:
| Manual section | rc.3 change | UAT finding |
|---|---|---|
| 2 Getting started; 17 Notifications | 12-hour clock with AM/PM everywhere, including emails | UAT-F20 |
| 3 Dashboard | Needs attention: one row per clean with its reason and a link | UAT-F09 |
| 6 Properties; 10 My Jobs | Password confirmation for access details, 5 minutes, never preloaded | UAT-F01 |
| 8 Recurring service plans | Generate jobs names plans and reports what it created | UAT-F02 |
| 8 Recurring service plans; 17 | The plan's cleaner applies to newly generated cleans; Regular work assigned email | UAT-F04 (UAT-F05 deferred) |
| 9 Calendar and scheduling | Confirmations after actions; reschedule keeps the length; one duration per clean; rescheduled clean shows once | UAT-F03, UAT-F06, UAT-F07 |
| 9 Calendar and scheduling | A one-off clean takes the service's defaults | UAT-F23 |
| 9 Calendar and scheduling | Billing links to the clean's invoice | UAT-F10 |
| 13 Customer Requests; 18 Customer Portal | Structured reschedule requests; the clean named; booking confirmation email | UAT-F14, UAT-F15, UAT-F16 |
| 14 Invoices | Hourly invoices use the booked length; extra Confirm price step | UAT-F21 (UAT-F22 deferred) |
| 18 Customer Portal | Business-clock times and dates; plain payment methods; invitation clarity; no portal routing to business setup | UAT-F08, UAT-F11, UAT-F12, UAT-F17, UAT-F18, UAT-F19 |
| 18 Customer Portal | Exactly one list per clean; Awaiting update and In progress | UAT-F24, UAT-F25 |
| 18 Customer Portal | Property Update always linked to one of the customer's own properties | UAT-F26 |
The section map below is unchanged from rc.2:
| Manual section | Product Design v0.5 | Acceptance evidence |
|---|---|---|
| 1 Welcome | 2 Product vision; 3 Current release; 4 v0.1 product boundary | 5.2 Core business journey |
| 2 Getting started | 6 Roles and access; 19 Release model | 5.1 Release integrity; 5.8 Auth, bootstrap |
| 3 Dashboard | 3 Current release (Revenue, Outstanding) | 5.5 Finance (Revenue, Outstanding, Overdue); 5.9 Error states |
| 4 Leads | Lead to customer conversion | 5.2 (Leads, conversion) |
| 5 Customers | Customers | 5.2 (customers) |
| 6 Properties | Customers; sensitive property access | 5.2 (properties, access details); 5.8 |
| 7 Services | 7 Service catalogue | 5.2; 5.5 (service descriptions) |
| 8 Recurring service plans | Recurring plans; scheduling | 5.2 (plans, job generation) |
| 9 Calendar and scheduling | Native scheduling | 5.2 (scheduling, assignment); 5.3 Time zones |
| 10 My Jobs | Cleaner execution | 5.4 Cleaner workflow (including completion) |
| 11 My Cleaner Profile | Roles; availability | 5.4 (Cleaner Profile, notes privacy) |
| 12 My Availability | Availability | 5.4 (Availability) |
| 13 Customer Requests | Customer portal core | 5.7 Customer portal |
| 14 Invoices | Finance administration | 5.5 (invoices, numbering, presentation) |
| 15 Recording payments | Finance administration | 5.5 (payments); 5.3 (payment date) |
| 16 Finance at a glance | Finance administration; status summary | 5.5; 5.10 Deferred boundary |
| 17 Notifications | Notifications | 5.6 Notifications |
| 18 Customer Portal | Customer portal core (off in production) | 5.7 |
| 19 Business Settings | Release model; time zones | 5.5 (settings); 5.3 |
| 20 Roles and access | 6 Roles and access | 5.8 Authorization and isolation |
| 21 Common situations | (operational guidance) | 5.4, 5.5, 5.9 |
| 22 What v0.1 does not include | 21 Status summary (future and deferred) | 5.10 Deferred boundary |