Engineering record — internal detail. The manual is authoritative for product behaviour.
Module gaps & fixes (current)
The approved plan closing the operational gaps recorded in the manuals: fleet, cashbook, approvals, analytics and admin seat enforcement.
Why this plan exists
Each module manual carried a 'current limitations' section listing behaviour that was documented but not finished. This plan converts those caveats into work: it is the direct source for the remaining-limitation callouts you see scattered across the manual chapters.
Scope
| Module | Gap closed |
|---|---|
| Fleet | Settlement finalize action on pending rows, expense edit and delete, role and report fixes |
| Cashbook | Bank account to GL account link, counter-account selector, partial receipts reachable, audited petty cash |
| Approvals & AI | Web AI approvals card fully wired, invoice tax extracted and posted |
| Analytics & Reports | Real KPI Explorer values, Telegram-delivered scheduled reports, CSV export, budgets and targets |
| Administration | Seat limit enforcement |
Note
Explicitly out of scope
Platform billing and the customer portal are out of scope. Billing remains a placeholder and the portal is deferred — both are recorded as such in the manual.
Documentation consequence
Several manual chapters now carry two contradictory statements: an earlier limitation and a later resolved note. The published manual resolves these in favour of the resolved state and keeps only the still-true limitations. The raw contradiction remains in the source documents for the record.
Source records
- Plan
- docs/superpowers/plans/2026-09-17-module-gaps-fixes-plan.md