KADRY — documentation¶
Internal documentation for KADRY: how an employer finds a person, how a candidate confirms a grade, and what of that already exists in the code.
Sections¶
| Section | What it is |
|---|---|
| Product overview | What the platform does and for whom |
| Page map | Screens, primary action, empty states |
| BRD | Normative requirements. If code disagrees, the BRD wins |
| Specification | Goals, MVP, extra scope, and non-goals |
| Actors | Candidate, employer, administrator |
| Use cases | Scenarios by role |
| User flows | Step-by-step paths with diagrams |
| Glossary | Category, need, pattern, and neighbouring words |
| Engineering | How the current monorepo is built |
The platform in two sentences¶
The employer describes who they need and reaches out first. A candidate receives a category — specialization plus grade — only after a survey and a test, not from the resume text. The company sees the candidate's contacts after the candidate accepts an invitation or applies.
The interface is a Russian React SPA. The API is FastAPI under /api/v1. Data sits in PostgreSQL.