najibcode/ibuild

Purpose and Entry Points

IBUILD ERP is an internal, multi-platform construction-operations system for supervisors and owners. Flutter is the client runtime for web, Android, iOS, desktop; its application entry point is lib/main.dart. Routing and adaptive shell/layout boundaries are centralized in lib/core/routing/router.dart, lib/mobile_dashboard.dart, and lib/web_dashboard.dart.

Application Composition

The codebase is organized primarily by feature, commonly separating data models/repositories, domain repository contracts, and Riverpod-backed presentation controllers/screens. A typical flow is screen → controller → repository interface/implementation → Supabase. Examples: lib/features/projects/presentation/controllers/project_controller.dart, lib/features/projects/domain/repositories/project_repository.dart, and lib/features/projects/data/repositories/supabase_project_repository.dart.

Identity, Authorization, and Navigation

Authentication is isolated behind an implementation and domain contract, with login, recovery, and startup screens under lib/features/auth/data/repositories/auth_repository_impl.dart, lib/features/auth/presentation/controllers/auth_controller.dart, and lib/features/auth/presentation/screens/splash_screen.dart. RBAC supplies role/permission models, a Supabase role repository, and UI guards for restricting sensitive features: lib/features/rbac/data/repositories/supabase_role_repository.dart, lib/features/rbac/presentation/providers/permission_provider.dart, and lib/features/rbac/presentation/widgets/permission_guard.dart.

Operational Domain Modules

Projects provide the central site/project identifier used to connect operational records and project dashboards: lib/features/projects/data/models/project_model.dart, lib/features/projects/presentation/screens/project_operations_screen.dart, and lib/features/projects/data/repositories/project_dashboard_repository.dart. Workforce workflows cover employees, attendance, daily wages, and reports through lib/features/employees/data/repositories/supabase_employee_repository.dart, lib/features/attendance/presentation/controllers/attendance_controller.dart, and lib/features/attendance/data/services/attendance_report_service.dart. Site execution tracks daily progress, activities, checklists, drawings, and tickets, including evidence-oriented models/repositories such as lib/features/daily_progress/data/repositories/supabase_daily_progress_repository.dart, lib/features/drawings/data/repositories/supabase_drawing_repository.dart, and lib/features/tickets/data/repositories/supabase_ticket_repository.dart.

Commercial, Asset, and Reporting Workflows

Financial workflows include expenses, billing, quotations, sales bills, payments, and ledger documents: lib/features/expenses/data/repositories/supabase_expense_repository.dart, lib/features/billing/data/building_pdf_generator.dart, and lib/features/payments/data/payment_ledger_pdf_generator.dart. Inventory and equipment track stock/history and fleet placement: lib/features/inventory/data/repositories/supabase_inventory_repository.dart, lib/features/inventory/presentation/screens/inventory_history_screen.dart, and lib/features/equipment/data/repositories/supabase_equipment_repository.dart. Shared export capabilities produce PDF/Excel outputs via lib/core/services/generic_pdf_table_generator.dart, lib/core/services/excel_generator_service.dart, and lib/features/reports/data/pdf_report_generator.dart.

Backend, Media, and Schema Boundary

Supabase is the external system of record for PostgreSQL data, Auth, RLS enforcement, and storage; the client integration boundary is lib/core/supabase/supabase_client.provider.dart. Versioned SQL migrations define the evolving relational schema and policies: supabase/migrations/001_rbac_tables.sql, supabase/migrations/003_project_operations.sql, and supabase/migrations/005_supervision_and_evidence.sql. Image uploads use ImageKit as a separate media service, with client services and a Supabase Edge Function that issues ImageKit authentication: lib/core/image/imagekit_auth_service.dart, lib/services/imagekit/imagekit_service.dart, and supabase/functions/imagekit-auth/index.ts.

Delivery and Platform Infrastructure

Web is deployed as a Flutter SPA to Vercel, configured by vercel.json; all routes rewrite to the client application. Native launchers package the same Flutter runtime for Android and iOS through android/app/src/main/kotlin/com/example/ibuild/MainActivity.kt and ios/Runner/AppDelegate.swift. CI runs through GitHub Actions at .github/workflows/dart.yml.