Fleet Ops — final acceptance evidence

Accepted implementation

Runtime commit: 29325b6c2775806080dc40e1988634d6ceb300a0 (master).
Live demo: http://192.168.10.150:1236 — public passwordless synthetic demo.
Deployment: Unraid /mnt/user/appdata/mobilityops, Compose project mobilityops.
Database migration: b913a72e8c14 (head).
Product name: Fleet Ops; MobilityOps remains the technical repository/deployment ID.

Clean acceptance — 2026-08-10

Backend, isolated PostgreSQL: 239 passed, zero warnings
Playwright, fresh local build: 150 passed (5.2 min)
Playwright, live production:   150 passed (4.2 min)
Ruff:                          clean
Mypy:                          clean across 58 source files
Frontend lint/build:           passed
npm audit, full and prod:      0 vulnerabilities
Alembic:                       b913a72e8c14 (head)

The browser suite covers both roles, protected routes, booking/return/maintenance/user/privacy workflows, five data-quality resolution types, correlated audit, retryable orchestration, grounded knowledge in three languages, the complete guided demo, the recruiter highlights, keyboard behaviour and responsive layouts from 360 to 1440 px.

The first production run correctly exposed two stale test assumptions: the redesigned Knowledge Hub shows localized source titles rather than raw file names. The evidence contract was changed to require the localized title and the language-specific source fragment. That focused matrix passed 4/4, followed by the complete 150/150 green production run.

Production hand-off state

The final reset completed at 2026-08-10T16:31:27Z and restored:

users 2 · customers 180 · vehicles 50 · bookings 254 · inspections 75
maintenance 40 · data-quality issues 33 · workflow runs 20
scenario_integrity.all_ready = true (5/5 scenarios)

API readiness is ready, PostgreSQL is up, and API, web, database, scheduled backup, Prometheus and Grafana are running healthy/current. No traceback or critical error appears in post-deployment API/backup logs.

A pre-deployment custom-format backup was created and independently verified by SHA-256 plus pg_restore --list:

/mnt/user/appdata/mobilityops/backups/postgres/mobilityops-20260810T161659Z.dump

External integration evidence

Existing central n8n: configured, dispatch enabled and operational. All four expected workflows have recent healthy heartbeats. The reset state contains 19 successful runs, zero pending, zero unexpected failures and one explicitly synthetic failed-retry scenario.
RAGcore: reachable and ready for tenant northstar-mobility-demo, workspace mobilityops, collection internal-procedures. Fleet Ops manages 11 authoritative Dutch sources; the latest n8n report records 33 synchronized language documents and zero failures. RAGcore exposes no reliable index-size endpoint, so document_count deliberately remains null.
ITWorx MCP Hub: registration is enabled and the Hub is reachable. A reset intentionally clears demo audit history, so the final state has no recent tool-call evidence and the UI labels MCP not connected rather than inferring success from configuration. Four tenant-bound service-authenticated endpoints remain contract-tested and read-only.

Recruiter and visual acceptance

The public entry now offers a direct 90-second Highlights route. It links three product actions to their engineering proof, while the Engineering workspace explains domain ownership, commit-before-orchestration, citation-bound AI, security and explicit scope.

Interactive live inspection confirmed:

no horizontal overflow on Highlights or Engineering at desktop; automated coverage confirms 360/390 px mobile layouts;
clear hierarchy, consistent primary actions and readable proof cards;
truthful live n8n/RAGcore/MCP labels after reset;
no dead links, placeholder numbers or unexplained raw data-quality references;
complete synthetic-data disclosure on login and in the persistent shell.

Current evidence images are in artifacts/evidence/screenshots/:

1-login.png
2-highlights.png
3-engineering-story.png
4-dashboard.png
5-knowledge-evidence.png
6-highlights-mobile.png

Deliberate boundary

This is a completed, production-shaped public demo—not claimed customer adoption and not a general ERP. Accounting, payments, public reservations, CRM, inventory, HR, a second RAG stack, a separate MCP server and autonomous write agents remain intentionally excluded. A real personal-data rollout would additionally require the adopting organisation's identity provider, retention approvals, secrets lifecycle, alert ownership and disaster-recovery governance.

4.6 KiB Raw Blame History