änderungen von vorherigen Codexnutzung: sollte den Agent lassen die Aufgaben zu erzeugen
This commit is contained in:
@@ -13,13 +13,20 @@ FlowiseAI runs as a Docker container on the same VPS and Docker network. The fro
|
||||
|
||||
## Backend
|
||||
|
||||
The Go API is the system of record. It owns auth, learner profiles, language profiles, exercises, attempts, progress, Azure calls, and Flowise calls.
|
||||
The Go API is the system of record. It owns auth, learner profiles, language profiles, generated exercises, attempts, progress, Azure calls, and Flowise calls.
|
||||
|
||||
Flowise owns the first version of the lesson logic: when the dashboard or `POST /lessons/next`
|
||||
needs the next task, the API sends profile/progress context to Flowise with a stable
|
||||
`sessionId`. Flowise returns one exercise JSON object. The API stores that exercise in PostgreSQL
|
||||
for the current user and returns it to the frontend. If Flowise is unavailable or returns invalid
|
||||
JSON, the API falls back to seeded A1 exercises. Feedback and the simple conversation screen stay
|
||||
local backend behavior in this first Flowise-generation phase.
|
||||
|
||||
Important boundaries:
|
||||
|
||||
- `httpapi`: request/response handling.
|
||||
- `services`: auth, Azure Speech, Flowise teacher logic.
|
||||
- `store`: PostgreSQL schema, seed data, repositories.
|
||||
- `store`: PostgreSQL schema, seed data, generated exercise persistence, repositories.
|
||||
- `domain`: shared API/domain structs.
|
||||
|
||||
## Multilingual Design
|
||||
|
||||
Reference in New Issue
Block a user