Gradely project documentation

This is Gradely’s central cross-repository architecture and integration reference.

Start here

The verified documents cite the repository branch and source path used to establish each claim. They distinguish code-backed facts from items that need deployment or operational confirmation.

• Architecture baseline and recommendation streak flow
• Backend and service boundaries
• Frontend and AI boundaries
• Verification register and prioritised review backlog
• Legacy micro-frontend map
• Branch, pull request, and ticket workflow

Using this repository

• Use the verified documents to identify ownership and trace cross-repository changes.
• Keep implementation detail, commands, tests, and deployment configuration in the repository that owns the system.
• Update these documents in the same pull request as an API or cross-service contract change.
• Do not record credentials, learner data, database dumps, or production payloads here.

Historical references

Earlier backend and frontend guides are preserved because they contain useful context. They are not current contracts and may include stale examples or operational assumptions:

• Historical backend integration reference
• Historical frontend micro-frontend reference

Contribution guidance

See AGENTS.md for documentation verification and contribution rules.