Skip to content

Issue W1-B3-02 β€” Progress and Performance API FoundationΒ #59

Description

@Abdully-dev

πŸ“‹ Overview
Prepare the service boundaries for future student analysis.
This issue does not implement BKT yet. It establishes where progress and performance logic will live.
🎯 Objectives
β€’ Create progress schemas.
β€’ Create progress service skeleton.
β€’ Create performance analyzer skeleton.
β€’ Define progress response format.
β€’ Define topic performance response format.
🎯 Scope
API and service contracts only.
πŸ”— Call Chain
Attempts
↓
Performance Analyzer
↓
Progress Service
↓
Progress API
βš™οΈ Technical Notes
Do not hardcode frontend-specific calculations inside routes.
Routes call services.
Services call analysis logic.
🚫 Out of Scope
β€’ BKT formulas
β€’ Recommendations
β€’ AI teaching
πŸ”— Dependencies
β€’ W1-B3-01 Attempt Architecture
βœ… Acceptance Criteria
β€’ Progress schema exists.
β€’ Service boundary is defined.
β€’ API endpoint returns valid placeholder/test data.
β€’ No business logic exists directly inside routes.
🌿 Branch
progress-performance-foundation
🚨 Files Concerned
backend/app/
β”œβ”€β”€ schemas/
β”‚ └── progress.py
β”œβ”€β”€ api/routes/
β”‚ └── progress.py
β”œβ”€β”€ services/
β”‚ └── progress_service.py
└── adaptive/
└── performance_analyzer.py

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions