project-d90b1537

Develop authentication routes using JWT for secure access control.

Develop API endpoint for document uploads, ensuring validation and storage.

Implement API endpoints to retrieve applicable rules and precedents for documents.

As a frontend developer, implement the FeaturesSection for the Landing page. This section displays a grid of features using the `motion` library for animations. Each feature card includes an icon, title, and description, with animations that fade in and slide up as they come into view. Ensure the section highlights features relevant to Karnataka government employees. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the Footer for the Landing page. This section includes branding, a tagline, and links to various pages such as Upload, Rules, Precedents, and Drafts. Ensure that links to restricted pages are conditionally shown based on the user's persona. The footer also includes a copyright notice. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the HeroSection for the Landing page. This section features a dynamic animation using `motion` and `useMotionValue` to create a parallax effect as the user moves their mouse. It includes a badge, title, subtitle, and call-to-action buttons. Ensure the animations are smooth and responsive, and the content is relevant to Karnataka government employees. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the Navbar for the Landing page. This component includes a logo, navigation links, and a responsive menu toggle. It uses state to manage the scroll effect and menu open/close state. Ensure the Navbar adapts to different screen sizes and that links to restricted pages are conditionally shown based on the user's persona. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the WorkflowSection for the Landing page. This section outlines the steps of the legal workflow using the `motion` library for animations. Each step includes a number, icon, title, and description, with animations that fade in and slide up as they come into view. Ensure the section clearly communicates the workflow process to Karnataka government employees. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the Navbar section for the Login page. This component includes a responsive navigation bar with a logo, toggleable menu, and links to Landing, Login, and Dashboard pages. The Navbar changes style when scrolled and includes a hamburger menu for mobile views. Ensure links to restricted pages like Dashboard are conditionally shown based on user persona. Page access: shared by all personas (Government Employee, System Administrator).

As a Data Engineer, design and implement database models for users, documents, rules, precedents, and drafts. Ensure the models support all required relationships and constraints.

As a Data Engineer, create database migrations for users, documents, rules, and precedents to ensure schema changes are applied consistently.

As a frontend developer, implement the Footer for the Landing page, which includes brand information and navigation links. The footer provides links to various sections like Upload, Rules, Precedents, and Drafts, with conditional access based on user roles. This component may already exist from previous pages. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the Navbar for the Landing page, which includes a logo, navigation links, and a toggleable menu for mobile views. The Navbar changes style when scrolled and provides links to pages like Login and Dashboard, with conditional visibility based on user roles. Page access: shared by all personas (Government Employee, System Administrator).

As a Data Engineer, establish data retention policies for documents, rules, and precedents to ensure compliance with data protection regulations.

Implement role-based access control for System Administrator functionalities.

Develop the routing shell for the application, ensuring protected routes for persona-specific pages.

As a frontend developer, implement the LoginFormPanel section for the Login page. This component includes a form with email and password fields, client-side validation, and a toggle for password visibility. It handles form submission and displays error messages for invalid inputs. Ensure the form is styled according to the design and integrates with potential OAuth or API calls for authentication. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the LoginSocialDivider section for the Login page. This component visually separates the traditional login form from social login options with a styled line and text. Ensure the divider is responsive and matches the design specifications. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the LoginSocialButtons section for the Login page. This component includes buttons for Google and Microsoft sign-in, each with respective icons and OAuth flow initiation. Ensure the buttons are styled correctly and handle click events to initiate the OAuth process. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the LoginSignupLink section for the Login page. This component provides a link to the signup page for users who do not have an account. Ensure the link is styled according to the design and is accessible. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the Footer section for the Login page. This component includes branding, a tagline, and links to various sections like Product, Case Work, and Account. Ensure the footer is styled consistently with the rest of the application and links are conditionally shown based on user persona. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the CaseListSidebar section for the Dashboard page. This section includes a sidebar with tabs for 'Current Cases' and 'History', displaying a list of cases with status icons. It uses React state to manage the active tab and toggles the sidebar's visibility. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the AdminSidebar section for the Admin Dashboard. This component includes a collapsible sidebar with menu items such as 'Overview', 'Rules Management', 'Precedents Management', 'API Supervisor', 'Users Management', and 'Activity Logs'. It should support opening and closing via a button, highlight the active section, and conditionally render based on the 'isOpen' prop. Ensure that links to restricted pages are conditionally shown based on the System Administrator persona access. Page access: System Administrator only.

As a Backend Developer, create an API endpoint to generate draft representations and OA/Writs based on analyzed documents. Ensure the drafts are customizable and align with legal standards.

As a Backend Developer, develop an API endpoint to provide an evidence checklist based on the uploaded documents and analysis results. Ensure the checklist is comprehensive and aligns with legal requirements.

As a Backend Developer, implement an API endpoint to provide expected litigation strategies based on document analysis. Ensure the strategies are detailed and actionable.

As a Backend Developer, implement authentication and role-based access control for Government Employees and System Administrators, ensuring secure access to persona-specific pages.

As a Backend Developer, develop API services for document analysis, rule retrieval, and precedent matching, ensuring they are optimized for performance and security.

As a Backend Developer, develop an API endpoint for analyzing uploaded documents to extract relevant service rules, precedents, and generate draft documents. Ensure the API is optimized for performance and security.

As a frontend developer, implement the AdminPageTitle section for the Admin Dashboard. This component displays the page title 'Admin Dashboard' with breadcrumbs navigation. It includes a welcome message for the System Administrator persona. Ensure the styling aligns with the design tokens and the breadcrumbs are functional. Page access: System Administrator only.

As a frontend developer, implement the AdminStatusBar section for the Admin Dashboard. This component displays the current time, API Supervisor status, system health, and includes a 'Sync Rules' button that triggers a synchronization alert. It uses React hooks for state management and effects for time updates. Ensure the component is styled according to the design specifications. Page access: System Administrator only.

As a frontend developer, implement the AdminOverviewStats section for the Admin Dashboard. This component displays a grid of statistics cards, each showing an icon, value, and label for metrics like 'Total Rules', 'Total Precedents', 'Active Users', and 'System Health'. Ensure the grid layout is responsive and visually consistent with the design. Page access: System Administrator only.

As a frontend developer, implement the AdminActionCards section for the Admin Dashboard. This component displays action cards for managing rules, precedents, and employees. Each card includes an icon, title, description, and a button that navigates to the respective management page. Ensure the cards are styled with accent colors and are accessible to the System Administrator persona. Page access: System Administrator only.

As a frontend developer, implement the AdminRecentActivity section for the Admin Dashboard. This component lists recent activities with details like type, description, time, and actor. It includes a link to view all logs, accessible only to the System Administrator persona. Ensure the list is styled for readability and aligns with the design. Page access: System Administrator only.

As a frontend developer, implement the UploadPageHeader section using React and motion for animations. This section includes a breadcrumb navigation, a title with an SVG icon, and a subtitle explaining the document upload process. It also features a rules context bar displaying supported document types with badges. This section is accessible by Government Employees only and must include page-level dependencies from the Dashboard. Page access: Government Employee only.

As a frontend developer, implement the RulesHeader section which includes breadcrumb navigation linking back to the Dashboard, a title 'Karnataka Government Service Rules', and a subtitle describing the repository's purpose. This section is accessible by Government Employees and System Administrators. Ensure the breadcrumb links are conditionally displayed based on user access. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the APISupervisorHeader section which includes a breadcrumb navigation indicating 'Admin Dashboard > API Supervisor', a title 'API Supervisor Dashboard', and a system health badge showing 'System Operational'. This section is accessible only by the System Administrator and depends on the Admin Dashboard's sidebar implementation. Page access: System Administrator only.

As a frontend developer, implement the UsersHeader section for the Users page. This section includes a breadcrumb navigation using the lucide-react icons ArrowLeft and ChevronRight, and a title block with motion animations for the title and subtitle. The section also displays an active user count badge using the UsersIcon from lucide-react. This page is accessible by System Administrators only, and links to restricted pages must be conditionally shown. Page access: System Administrator only.

As a Tech Lead, verify the end-to-end integration between the Rules and Precedents frontend implementation and their respective backend APIs. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a QA Engineer, develop integration tests for critical workflows such as document upload and rule retrieval to ensure end-to-end functionality.

As an AI Engineer, integrate the GPT 5.4 model using LiteLLM for document analysis and legal precedent retrieval. Ensure the integration is seamless and responses are accurate.

As a Full Stack Developer, implement a notification system to alert users about document processing status and updates. Ensure notifications are delivered in real-time and are configurable.

As a frontend developer, implement the UploadDropZone section using React with state management for drag-and-drop file uploads. This section supports file validation for specific extensions and size limits, displays error messages, and manages accepted files. It is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the UploadFilePreview section using React to display a list of uploaded files with their status, progress, and actions for retry or removal. This section uses state management and timers to simulate upload progress. It is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the UploadDocumentTypes section using React to display detailed information about each document type, including icons, rules, descriptions, and context examples. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the UploadRequirements section using React to outline the technical requirements and processing workflow for document uploads. This section includes a checklist, accepted file formats, and a timeline of processing steps. It is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the UploadFAQ section using React to provide answers to frequently asked questions about document security, processing time, supported document types, and applicable service rules. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the RulesSearch section which includes a search input with debounce functionality and a sort dropdown. The search input allows filtering by rule title, number, or keyword, and the sort dropdown offers options for sorting by relevance or title. This section is accessible by Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the RulesCategories section which displays tabs for different rule categories. Each tab shows the category name and the count of rules within that category. Clicking a tab filters the displayed rules. This section is accessible by Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the RulesListContainer section which displays a grid of rule cards. Each card shows the rule number, title, jurisdiction, description, and relevance score. Clicking a card selects it, and keyboard navigation is supported. This section is accessible by Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the RelatedResources section which displays cards for additional resources like precedents, evidence checklist, and litigation strategy. Each card includes an icon, title, description, and a call-to-action link. This section is accessible by Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the UsersSearch section for the Users page. This section includes a search input with a clear button, using motion/react for animations. The search functionality allows filtering by name or email, and the input state is managed with React hooks. This page is accessible by System Administrators only. Page access: System Administrator only.

As a frontend developer, implement the UsersFilters section for the Users page. This section includes dropdown filters for role and status, with animated dropdowns using motion/react. The section manages filter state with React hooks and displays active filter badges. This page is accessible by System Administrators only. Page access: System Administrator only.

As a frontend developer, implement the UsersActions section for the Users page. This section includes a bulk actions dropdown with various options, using motion/react for animations. The section manages the dropdown state and handles outside clicks to close the dropdown. This page is accessible by System Administrators only. Page access: System Administrator only.

As a frontend developer, implement the UsersTable section for the Users page. This section displays a table of Karnataka government employees with columns for name, email, role, department, status, and last login. The table uses React hooks for state management and includes animations with motion/react. This page is accessible by System Administrators only. Page access: System Administrator only.

As a frontend developer, implement the PrecedentsHeader section using the provided JSX code. This section includes an animated header with a compliance badge and title, utilizing an IntersectionObserver to add a 'visible' class when the header is in view. Ensure the header displays the title 'Karnataka Service Precedents' and a subtitle describing the access to court rulings relevant to Karnataka government employees. This section is accessible by both Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the LogsHeader section for the Logs page. This section includes a breadcrumb navigation with links to the Admin Dashboard and the current Logs page. It also displays the title 'Activity Logs'. Ensure that this section is accessible only to the System Administrator persona. The component may already exist from previous pages, so check for reusability. This section depends on the Users page header task. Page access: System Administrator only.

As a frontend developer, implement the RulesDetailPanel section which displays detailed information about a selected rule. It includes the rule number, title, jurisdiction, full text, and amendments. The panel supports closing via a button or the Escape key, and copying the rule text to the clipboard. This section is accessible by Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the UsersTableActions section for the Users page. This section provides action buttons for each user in the table, including view, edit, and toggle status. The section uses React hooks for state management and includes animations with motion/react. This page is accessible by System Administrators only. Page access: System Administrator only.

As a frontend developer, implement the UsersPagination section for the Users page. This section includes pagination controls for navigating through the user table, with options to change the number of rows per page. The section uses React hooks for state management and includes animations with motion/react. This page is accessible by System Administrators only. Page access: System Administrator only.

As a frontend developer, implement the FilterBar section using the provided JSX code. This section includes interactive filters for searching precedents by case name, type, court, and year range. It features a mobile toggle for filter visibility and a reset function to clear all filters. Ensure the filters are functional and responsive, providing a seamless user experience for Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the LogsSearchInput section for the Logs page. This section includes a search input field with a clear button, allowing the System Administrator to search logs by user, action, or resource. The component uses a state hook to manage the search term and provides a callback for search term changes. Ensure accessibility for the System Administrator persona. Page access: System Administrator only.

As a frontend developer, implement the LogsDateRangeFilter section for the Logs page. This section includes a date range picker with presets like 'Today', 'This Week', and 'Karnataka FY'. It uses state hooks and the motion library for animations. Ensure that the date range filter is functional and accessible only to the System Administrator persona. Page access: System Administrator only.

As a frontend developer, implement the LogsTypeAndUserFilters section for the Logs page. This section includes dropdowns for filtering logs by action type and user, using state hooks to manage selected filters. It features animations for dropdowns using the motion library. Ensure that the filters are functional and accessible only to the System Administrator persona. Page access: System Administrator only.

As a frontend developer, implement the LogsTableAndPagination section for the Logs page. This section displays a table of logs with pagination controls. It uses state hooks to manage pagination and includes animations for table updates. Ensure that the table is functional and accessible only to the System Administrator persona. Page access: System Administrator only.

As a frontend developer, implement the DraftsHeader section which includes breadcrumb navigation linking back to the Dashboard, a title 'Draft Documents', and a badge indicating 'AI Generated'. Ensure the back link navigates to the Dashboard. This section is accessible by Government Employees only. Note that this component depends on the Precedents page setup. Page access: Government Employee only.

As a Tech Lead, verify the end-to-end integration between the Upload frontend implementation and the Upload backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a frontend developer, implement the RuleDetailLinks section which displays links to related precedents and rules. Each link opens in a new tab. This section is accessible by Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the PrecedentsResultsContainer section using the provided JSX code. This section displays a list of precedent cards with details such as case name, court, year, and summary. Use IntersectionObserver to reveal cards as they enter the viewport. Ensure the data is accurately represented and accessible to Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the DraftsTabs section which includes two tabs: 'Representation Draft' and 'OA / Writ Draft'. The active tab is highlighted with a moving indicator. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseHeader section for the Case page. This section includes a breadcrumb navigation linking back to the Dashboard, a back button to navigate to the previous page, and displays metadata about the case such as the title 'Disciplinary Proceedings – Suspension Order' and badges for document type and upload date. This section is accessible by Government Employees only and should conditionally show navigation links based on persona access. Page access: Government Employee only.

As a frontend developer, implement the PrecedentsPagination section using the provided JSX code. This section includes pagination controls to navigate through precedent results, with buttons for previous, next, and specific pages. Ensure the pagination is functional and provides a smooth navigation experience for Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the CaseStudies section using the provided JSX code. This section displays case studies with titles, narratives, and links to explore more. Use IntersectionObserver to reveal the section when it enters the viewport. Ensure the case studies are presented clearly and are accessible to Government Employees and System Administrators. Page access: shared by all personas (Government Employee, System Administrator).

As a frontend developer, implement the RepresentationDraftContent section which displays the draft title and body. It allows editing via a textarea when in editing mode. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the OAWritDraftContent section which displays the draft title and body. It allows editing via a textarea when in editing mode. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseTabNavigation section for the Case page. This section provides a tabbed navigation interface with tabs for 'Rules', 'Precedents', 'Drafts', 'Weaknesses', 'Evidence', and 'Strategy'. It uses props to manage the active tab state and handles tab changes via the onTabChange callback. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the EvidenceBreadcrumb section which includes a breadcrumb navigation trail and a case reference with a copy button. The breadcrumb trail links to the Dashboard and Case Review pages, and the current page is Evidence Checklist. The case reference 'KAR/2025/CASE-0042' can be copied to the clipboard, with a visual feedback 'Copied!' shown upon success. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the RepresentationDraftActions section which includes buttons for copying the draft to clipboard, toggling edit mode, and downloading the draft. It also includes feedback buttons for user interaction. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the OAWritDraftActions section which includes buttons for copying the draft to clipboard, toggling edit mode, and downloading the draft. It also includes feedback buttons for user interaction. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseRulesTab section for the Case page. This section displays a list of rules related to the case, with each rule expandable to show detailed information. It uses a state hook to manage which rules are expanded. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CasePrecedentsTab section for the Case page. This section displays precedents grouped by court, with each precedent expandable to show detailed information. It uses a state hook to manage which precedents are expanded and a function to group precedents by court. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseDraftsTab section for the Case page. This section provides templates for legal drafts, allowing users to copy or download them. It includes functionality to copy text to the clipboard and download drafts as text files. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseWeaknessesTab section for the Case page. This section lists weaknesses in the department's case, sorted by severity. It uses a function to assign severity weights and sort the weaknesses accordingly. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseEvidenceTab section for the Case page. This section displays an evidence checklist with the ability to toggle the collected status of each item. It uses a state hook to manage the evidence list and calculates the progress of evidence collection. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the CaseStrategyTab section for the Case page. This section outlines the litigation strategy in phases, each with a description, timeline, and action items. It visually represents the phases in a timeline format. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the StrategyHeader section which includes a breadcrumb navigation linking to the Dashboard and Case pages, a header title 'Litigation Strategy', and a case badge displaying 'Case #KA-CS-2024-56'. Ensure the back link navigates to the Case page. This section is accessible by Government Employees only. Note that links to restricted pages must be conditionally shown. This section depends on the Evidence page tasks for integration. Page access: Government Employee only.

As a frontend developer, implement the StrategyOverview section which displays a recommended approach with a confidence level indicator. The section uses a color-coded badge to show confidence levels (high, medium, low) and provides a summary of the recommended legal strategy. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the LitigationPhases section which outlines the phases of litigation with expandable cards for each phase. Each card includes phase number, name, duration, actions, responsibilities, and rule references. The section uses state to manage expanded/collapsed views. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the KeyRecommendations section which lists strategic recommendations with priority badges. Each recommendation includes text, reasoning, and impact, with color-coded priority indicators. This section is accessible by Government Employees only. Page access: Government Employee only.

As a frontend developer, implement the RiskAssessment section which displays a grid of risk cards. Each card includes a description, severity, likelihood, mitigation, and contingency plan, with color-coded severity indicators. This section is accessible by Government Employees only. Page access: Government Employee only.

As a Tech Lead, verify the end-to-end integration between the Strategy frontend implementation and the Strategy backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.