Track B // Engineering
14 dated entries in build order: architecture, security and tenancy reviews, module designs, implementation plans, the delivery log, known gaps and the changelog.
Internal engineering material
This track is published for transparency and for the team. It contains security findings, tenancy and policy details, migration internals and unresolved gaps. Do not treat it as customer guidance — the manual is the authoritative source for how the product behaves.
What the platform is built from today: frameworks, datastore, auth, storage, jobs, AI, testing and the design contract.
Design and plan for 21 issues found in an inventory subsystem audit: 5 critical, 3 type-safety, 3 performance, 6 medium, 4 low.
Historical: moving the datastore from Supabase Postgres to Neon, Supabase Auth to a first-party auth stack, and Supabase Storage to Cloudflare R2.
Superseded by the Telegram integration. A Meta Cloud API gateway in front of the in-app AI orchestration for executive lookups, reports, approvals and uploads.
Tenant isolation, cache consistency, the role matrix and staged policy enforcement for the inventory module.
Replacing the WhatsApp gateway with a Telegram bot: chat-ID allowlist, secret-token webhook, approval parity with the web app, and media upload.
Fourteen findings across trips, vehicles, drivers, advances, expenses and settlements, with fix designs F1–F7.
The container-first model, four operation types, twelve new tables, the demurrage engine, document PDFs and the warehouse gate bridge.
The procurement and sales order and invoice modules reviewed for cache-key leakage, cross-org references, deadlock-safe stock locking, status re-checks and transition rules.
One predicate for sidebar visibility and server route authorisation, plus a rebuilt sidebar rail on the design tokens.
The approved plan closing the operational gaps recorded in the manuals: fleet, cashbook, approvals, analytics and admin seat enforcement.
The per-task execution reports that record what each agent run actually changed, kept alongside the dated plans.
Every limitation that survives the module-gaps plan, in one place, with the module it belongs to.
Every dated design and plan in the record, in order, with status.