Lexiverse
Lexiverse - AI contextual reading engine for English learners. Your next article is your next review.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證OSCE Guide: api, web and assessment in one repository
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗A platform for practising and running medical exams. Doctors practise stations with an AI patient and get marked feedback. Institutions and employers run real exams on it and review the results.
Everything lives in this one repository, in three folders. Each one deploys on its own when its folder changes.
| Folder | What it is | Built with |
|---|---|---|
api/ | The backend. Accounts, stations, attempts, marking, exams, billing | Python, FastAPI, SQLAlchemy, Postgres |
web/ | The website and app people use | Next.js, TypeScript, Tailwind |
assessment/ | The marking engine, and the voice workers that play the patient and the tutor | Python, LiveKit |
The api uses the marking engine directly from assessment/packages/osce_assessment,
so a change to the engine and the api code that needs it go in one commit.
# api, on http://localhost:8002
cd api
docker compose up -d && poetry run alembic upgrade head
poetry run python scripts/seed_platform.py # a new database has no exams until this runs
make start
# web, on http://localhost:3100
cd web
npm install && npm run dev
# assessment (tests only; the workers need LiveKit keys, see assessment/README.md)
cd assessment
poetry install && poetry run pytest -q
cd api && make ci
cd web && npm run ci
cd assessment && poetry run pytest -q
Each of these also runs "guard" tests. A guard is a test that reads the code itself and fails when a house rule is broken, for example a screen reaching into a folder it should not, or a function with no explanation. The failure message says what to change.
AGENTS.md here: the map of the repository, who owns which area, and the rules everyone follows.api/docs/README.md: how the backend is put together, in reading order.web/AGENTS.md and web/docs/DESIGN.md: how the app is layered and how it should look.assessment/AGENTS.md: what the engine and the workers may and may not know about.web/docs/BACKLOG.md: the one list of work that is still open.A push to main goes to staging for the folders it touched. Production changes
only when someone runs the matching "Promote ... to production" workflow. The
table at the top of AGENTS.md has the detail for each folder.