windy-revenue

As a developer, I need to implement the backend logic for analyzing clinic revenue data to generate insights and reports for clinic managers. Implementation contract: - Outcome: Implement Revenue Analysis Backend - Requirement sources: - src-b7c14f99eb26c314 - src-4153fa1c0631c47a - src-53e272b4aad94007 - src-860672b180181a73 - src-508cbbd198996fd7 - src-9c8e07a785fdceeb - src-630a1a39d814f555 - Owned behavior: - As a developer, I need to implement the backend logic for analyzing clinic revenue data to generate insights and reports for clinic managers. - Revenue data analysis - Report generation - Analyze Clinic Revenue Data (Clinic Manager) — trigger: Scheduled analysis or manual initiation by Clinic Manager; inputs: Follow-up records, Package details, Repeat visit data; outcomes: Revenue leakage report - Execute revenue analysis and manage analysis workflow. - Interfaces: - GET /api/dashboard - Input contract for Analyze Clinic Revenue Data: Follow-up records, Package details, Repeat visit data - Consume identity.access.management: Manage user authentication and session persistence. - Provide revenue.analysis.execution: Execute revenue analysis and manage analysis workflow. - State transitions: - Revenue analysis records created - When Scheduled analysis or manual initiation by Clinic Manager: Revenue analysis records - Failure and safety behavior: - Analysis error - Data retrieval failure - If Analyze Clinic Revenue Data cannot complete: Analysis error notification. Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - Successful generation of revenue reports - Error notifications for analysis failures - When Scheduled analysis or manual initiation by Clinic Manager, Clinic Manager produces Revenue leakage report. - Analyze Clinic Revenue Data includes the required human touchpoint: Dashboard. - Capability identity.access.management implements Manage user authentication and session persistence. and is verified through its declared interfaces. - Capability revenue.analysis.execution implements Execute revenue analysis and manage analysis workflow. and is verified through its declared interfaces.

As a Frontend Developer, implement the shared Navbar component from its approved JSX/CSS design and reuse it across all declared pages without duplicating local variants. Implementation contract: - Outcome: Implement Shared Navbar - Requirement sources: - src-71aea7343b77ea25 - Owned behavior: - As a Frontend Developer, implement the shared Navbar component from its approved JSX/CSS design and reuse it across all declared pages without duplicating local variants. - Implement shared design sections: Navbar. - Interfaces: - Consume identity.access.management through session state. - State transitions: - Dynamic navigation based on session. - Use neutral loading, empty, anonymous, and error states instead of restoring prototype data. - Failure and safety behavior: - Use neutral loading, empty, anonymous, and error states; never use prototype data as a runtime fallback. - Never retain or restore hardcoded prototype data as the runtime fallback when live integration fails. - Prototype-to-live replacements: - Replace "const NAV_LINKS = [ { label: 'Authentication', href: '/', icon: LogIn, requiresSession: false }, { label: 'Clinic Dashboard', href: '/clinic-dashboard', icon: LayoutDashboard, requiresSession: true }, ];" with session state. Dynamic navigation based on session. Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - The shared Navbar component renders once and is reused by every declared consuming page. - Dynamic navigation based on session. - The prototype value is absent from successful runtime rendering and from error fallbacks.

As a Frontend Developer, implement the approved Authentication page design and the task-owned sections below. Implementation contract: - Outcome: Implement Authentication page - Requirement sources: - src-53e272b4aad94007 - src-860672b180181a73 - src-508cbbd198996fd7 - src-9c8e07a785fdceeb - src-630a1a39d814f555 - Owned behavior: - Enable Clinic Manager authentication and session establishment - Interfaces: - Submit credentials securely to backend and receive session token - Consume identity.access.management: Manage user authentication and session persistence. - State transitions: - Transition to Clinic Dashboard upon successful login - Failure and safety behavior: - Show authentication failures and recovery guidance Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - The Authentication page must render the AuthenticationContainer component exactly once. - The page must display email and password fields with real-time validation feedback. - The submit button must show a loading state during submission and handle errors gracefully. - Upon successful login, the page must redirect to the Clinic Dashboard, preserving session credentials in local storage. - Access is restricted to Clinic Managers. - Capability identity.access.management implements Manage user authentication and session persistence. and is verified through its declared interfaces.

As a Frontend Developer, implement the approved Clinic Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Clinic Dashboard Header - Requirement sources: - src-f039b542f24a8a74 - src-53e272b4aad94007 - src-860672b180181a73 - src-508cbbd198996fd7 - src-9c8e07a785fdceeb - src-630a1a39d814f555 - Owned behavior: - visible and interactive behavior owned by these sections - Interfaces: - consumed API, data, or event contracts - Consume identity.access.management: Manage user authentication and session persistence. - State transitions: - material source-backed transition with its trigger and observable result - Failure and safety behavior: - source-backed failure behavior owned by this task Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - observable task-owned checks - Capability identity.access.management implements Manage user authentication and session persistence. and is verified through its declared interfaces.

As a Frontend Developer, implement the approved Clinic Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Clinic Dashboard - AnalysisPanel - Requirement sources: - src-b7c14f99eb26c314 - src-4153fa1c0631c47a - src-53e272b4aad94007 - src-860672b180181a73 - src-508cbbd198996fd7 - src-9c8e07a785fdceeb - src-630a1a39d814f555 - Owned behavior: - Trigger manual analysis or display scheduled analysis status - Display analysis loading/progress state with user feedback - Present revenue analysis records and key metrics - Show error notifications and enable retry recovery - Manage analysis state lifecycle (idle → analyzing → completed/failed) - Analyze Clinic Revenue Data (Clinic Manager) — trigger: Scheduled analysis or manual initiation by Clinic Manager; inputs: Follow-up records, Package details, Repeat visit data; outcomes: Revenue leakage report - Interfaces: - API endpoint '/api/revenue-analyses/run' - Input contract for Analyze Clinic Revenue Data: Follow-up records, Package details, Repeat visit data - Consume identity.access.management: Manage user authentication and session persistence. - Consume revenue.analysis.execution: Execute revenue analysis and manage analysis workflow. - State transitions: - Idle → Analyzing → Completed/Failed - When Scheduled analysis or manual initiation by Clinic Manager: Revenue analysis records - Failure and safety behavior: - Analysis service unreachable - Unexpected response from analysis service - If Analyze Clinic Revenue Data cannot complete: Analysis error notification. Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - AnalysisPanel renders on Clinic Dashboard - Manual and scheduled analysis initiation - Loading and results states display correctly - Error handling with retry options - Historical analysis records are shown - Design matches provided CSS styles - Access restricted to Clinic Managers - When Scheduled analysis or manual initiation by Clinic Manager, Clinic Manager produces Revenue leakage report. - Analyze Clinic Revenue Data includes the required human touchpoint: Dashboard. - Capability identity.access.management implements Manage user authentication and session persistence. and is verified through its declared interfaces. - Capability revenue.analysis.execution implements Execute revenue analysis and manage analysis workflow. and is verified through its declared interfaces.

As a Frontend Developer, implement the approved Clinic Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Clinic Dashboard InsightsPanel - Requirement sources: - src-7d6bcf4c55b24dea - src-1c136994f56dbb2e - src-3070cc2e3301bd97 - src-53e272b4aad94007 - src-860672b180181a73 - src-508cbbd198996fd7 - src-9c8e07a785fdceeb - src-630a1a39d814f555 - Owned behavior: - Display insights only after analysis completes successfully - Highlight high-priority insights visually - Hover/tap insight → show expanded recommendation - Interfaces: - Consume identity.access.management: Manage user authentication and session persistence. - State transitions: - Analysis completion triggers insights display - Failure and safety behavior: - Hide insights during analysis or after error state Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - InsightsPanel renders once on Clinic Dashboard - Insights display only when analysis is completed - Design matches provided CSS - High-priority insights are highlighted - Access restricted to Clinic Manager after login - Capability identity.access.management implements Manage user authentication and session persistence. and is verified through its declared interfaces.

As a Frontend Developer, implement the approved Clinic Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Clinic Dashboard page - Requirement sources: - src-5e4f7f33b8bd966c - src-bcc5348ad986e3cb - src-53e272b4aad94007 - src-860672b180181a73 - src-508cbbd198996fd7 - src-9c8e07a785fdceeb - src-630a1a39d814f555 - Owned behavior: - Display revenue leakage amounts and percentages with visual trend - Show follow-up efficiency metrics through chart - Present package utilization breakdown - Visualize repeat visit trends and patterns - Interfaces: - revenue_analyses data entity - Consume identity.access.management: Manage user authentication and session persistence. - State transitions: - Update visualizations when new analysis completes - Failure and safety behavior: - Data not available or incorrect format Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - The Clinic Dashboard page must render the RevenueVisualizationPanel exactly once. - The panel must display interactive charts with hover feedback and responsive legends. - The design must be responsive and maintain the specified color scheme and typography. - The section must read data from the revenue_analyses entity and update visualizations when new analysis completes. - Access is restricted to Clinic Managers, requiring login. - Capability identity.access.management implements Manage user authentication and session persistence. and is verified through its declared interfaces.