Manual · Engineering

Engineering record — internal detail. The manual is authoritative for product behaviour.

Engineering6 min read

Known gaps & roadmap

Every limitation that survives the module-gaps plan, in one place, with the module it belongs to.

ForEngineerAdministrator

Open items after the fixes

ModuleLimitationImpact
FleetTrip status is not set to Settled automatically when a settlement finalizesA manual step; the trip stays in Completed until an operator closes it
FleetA posted trip-expense amount cannot be editedCorrect by deleting and recreating the expense
CashbookNo bank-statement import or automatic matchingReconciliation is a manual flag against your own statement
AnalyticsDashboards use fixed windows with no per-page date filterUse Reports when a specific date range is required
AdministrationTransfer CEO has no interface controlRequires an administrator or API action
AdministrationBilling & Portal is a placeholderSoftware subscription is not yet self-service
AdministrationAudit coverage is broad but not totalVerify a specific control is captured before relying on it
TelegramApproval parity between web and Telegram should be re-verified against the current buildThe plan flagged it as pending; the manual asserts parity

Deferred by decision

  • Customer portal — deferred when the port and warehouse modules were designed.
  • Automatic Cost of Goods Sold and shrinkage posting — deliberately excluded, available via manual journal today.
  • Payroll ledger integration — out of the automated ledger by design.

Documentation debt

  • AGENTS.md names Supabase and Supabase Auth; the stack is Neon and Better Auth.
  • Fleet, cashbook, approvals and analytics manuals each carry an earlier limitation section that contradicts a later resolved note in the same file.
  • The administration manual's pending-approvals alert note contradicts the approvals manual's resolved note on the same alert.
  • Features/feature-01.md still describes the Supabase and Stripe architecture and is historical only.