kumbalpuri/sfc

Purpose and Entry Points

This is a TypeScript React operations/continuous-improvement application, centered on dashboards, Kaizen workflows, PPSR inspection, safety, 5S audits, and red-flag reporting. The browser entry point is index.html, which loads src/main.tsx; src/App.tsx composes the application-level UI. A separate server.ts indicates a server-side runtime or API host boundary, though its responsibilities are not visible from the tree.

Application Shell and Navigation

The shared application frame is formed by src/App.tsx, src/components/Header.tsx, and src/components/Sidebar.tsx. These components likely own top-level screen selection and persistent navigation, separating global layout from individual operational modules.

Dashboard and Cross-Module Visibility

Dashboard views provide aggregate and management-facing visibility:

• src/components/Dashboard.tsx

• src/components/GlobalDashboard.tsx

• src/components/KaizenReviewBoard.tsx

These are the primary read/monitoring surfaces, likely consuming status and progress data produced by the workflow modules below.

Kaizen Improvement Workflow

The Kaizen subsystem is a core authoring, review, tabular-management, and presentation flow:

• src/components/KaizenSheetForm.tsx

• src/components/KaizenSpreadsheet.tsx

• src/components/KaizenPresentationMode.tsx

The expected control flow is create/edit improvement records in the form, manage or compare them in the spreadsheet view, then expose them in review or presentation contexts. src/components/KaizenReviewBoard.tsx is the review-stage boundary.

PPSR Inspection and Presentation

PPSR functionality is isolated as its own operational workflow:

• src/components/PpsrSystem.tsx

• src/components/PpsrSheetInspect.tsx

• src/components/PpsrPresentationMode.tsx

This suggests a progression from a system-level workspace to sheet inspection, with a dedicated mode for presenting results. It is architecturally parallel to the Kaizen workflow but remains component-separated.

Quality, Safety, and Problem Analysis Modules

Independent domain modules cover structured audits, incident handling, escalation, and root-cause analysis:

• src/components/FiveSAudits.tsx

• src/components/SafetyIncidents.tsx

• src/components/RedFlagSystem.tsx

src/components/IshikawaFishbone.tsx provides a distinct cause-analysis surface, likely linked conceptually to incidents, audit findings, or red flags without being embedded in their component paths.

Shared Data and Runtime Boundaries

src/types.ts is the central contract boundary for domain entities shared across screens, while src/utils.ts holds shared transformations or presentation logic. Styling is application-wide through src/index.css. The frontend is built with Vite configuration in vite.config.ts; dependencies and runnable scripts are defined by package.json. Runtime configuration is expected through .env.example, and server integration—if used—crosses the frontend/backend boundary at server.ts.