PTSRaiAgent

119 Commits 20 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
Arxip222andClaude Opus 5.5	44814b7293	fix(clinical): red flags, one crisis rule, callback after a crisis, one table of numbers Clinical review of the questionnaires (ADR-013): - Red-flag block first in stage 1 (config/instruments/red_flags.yaml); any «Да» stops the questionnaire with an acute alert and the help screen of its category. - One crisis rule: the crisis screen opens at a HIGH C-SSRS risk only; moderate stops and goes to a psychiatrist (24 h as a guide), low is a flag with the safety plan. PHQ-9 item 9 with a negative screener is a discrepancy flag; without a completed screener it asks the C-SSRS at once. config/questionnaire.yaml: cssrs_positive_policy graded (C01). - Every crisis leaves a callback task for the doctor on duty (post_crisis_call, one per patient) and the app asks how the person is the next day, the safety plan one tap away. - Routing: risk and flags first, scales second; PCL-5 >= 50 no longer means a priority appointment (pcl5_severe is moderate on the dashboard too). - Crisis numbers live only in config/texts/crisis.yaml; texts and the agent prompt refer to them via {phone:<key>}. Fixes the children's helpline offered to adults by the chat agent. Refs #92 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-04 16:21:16 +03:00
Arxip222andClaude Opus 5.5	b8a93ce9d4	feat(web): patient web app with ЕМИАС (demo) and anonymous sign-in A second channel to the same dialog engine as the Telegram bot: consent, onboarding, scales and check-ins come from app/dialog; the bot is unchanged. - API: /auth/emias (doctor's one-time connect code via EmiasMock), /auth/emias/demo (synthetic personas), /auth/anonymous (random token, nothing stored in the identity DB), /crisis/resources from crisis.yaml - web/: React + TS + Vite, mobile-first, safe areas, hash routing, tokens and texts isolated for a Capacitor mobile build Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-04 07:57:00 +03:00
ElebobaandClaude Opus 5.5	b4731fb1d6	chore(core): stage 1 contracts — dialog, API schemas + fixtures, integrations, monitoring, modules CI / ruff · pytest (pull_request) Successful in 22s Details Freeze interfaces between lanes A (bot), B (backend), C (dashboard) so three developers work in parallel without touching each other's files: dialog Event/Reply + engine registry with echo stub, integration protocols with in-memory defaults, MonitoringService with noop stub, /api/v1 schemas with fixture-backed routes, frozen main.py wiring, config/modules.yaml + due_scales(), DAR-5, tzdata, Andrey trajectory, lanes in WORKFLOW, ADR-010. Refs #34 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-03 15:22:25 +03:00

Author

SHA1

Message

Date

Arxip222andClaude Opus 5.5

44814b7293

fix(clinical): red flags, one crisis rule, callback after a crisis, one table of numbers

Clinical review of the questionnaires (ADR-013):
- Red-flag block first in stage 1 (config/instruments/red_flags.yaml); any «Да» stops the
  questionnaire with an acute alert and the help screen of its category.
- One crisis rule: the crisis screen opens at a HIGH C-SSRS risk only; moderate stops and goes
  to a psychiatrist (24 h as a guide), low is a flag with the safety plan. PHQ-9 item 9 with a
  negative screener is a discrepancy flag; without a completed screener it asks the C-SSRS at once.
  config/questionnaire.yaml: cssrs_positive_policy graded (C01).
- Every crisis leaves a callback task for the doctor on duty (post_crisis_call, one per patient)
  and the app asks how the person is the next day, the safety plan one tap away.
- Routing: risk and flags first, scales second; PCL-5 >= 50 no longer means a priority
  appointment (pcl5_severe is moderate on the dashboard too).
- Crisis numbers live only in config/texts/crisis.yaml; texts and the agent prompt refer to them
  via {phone:<key>}. Fixes the children's helpline offered to adults by the chat agent.

Refs #92

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-04 16:21:16 +03:00

Arxip222andClaude Opus 5.5

b8a93ce9d4

feat(web): patient web app with ЕМИАС (demo) and anonymous sign-in

A second channel to the same dialog engine as the Telegram bot: consent,
onboarding, scales and check-ins come from app/dialog; the bot is unchanged.

- API: /auth/emias (doctor's one-time connect code via EmiasMock),
  /auth/emias/demo (synthetic personas), /auth/anonymous (random token,
  nothing stored in the identity DB), /crisis/resources from crisis.yaml
- web/: React + TS + Vite, mobile-first, safe areas, hash routing,
  tokens and texts isolated for a Capacitor mobile build

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-04 07:57:00 +03:00

ElebobaandClaude Opus 5.5

b4731fb1d6

chore(core): stage 1 contracts — dialog, API schemas + fixtures, integrations, monitoring, modules

CI / ruff · pytest (pull_request) Successful in 22s

Details

Freeze interfaces between lanes A (bot), B (backend), C (dashboard) so three developers work in
parallel without touching each other's files: dialog Event/Reply + engine registry with echo stub,
integration protocols with in-memory defaults, MonitoringService with noop stub, /api/v1 schemas
with fixture-backed routes, frozen main.py wiring, config/modules.yaml + due_scales(), DAR-5,
tzdata, Andrey trajectory, lanes in WORKFLOW, ADR-010.

Refs #34

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-03 15:22:25 +03:00