Labels

apps/api (NestJS backend, Prisma models, CASL permissions)

apps/gateway (patient-facing app for remote assignments)

Deployment, Docker, CI, logging, CLIs, build and test tooling

Instrument authoring API, bundling, runtime, rendering, measures and the built-in library

apps/outreach and docs/ (marketing site and user documentation)

apps/playground (in-browser instrument editor)

Cross-tier packages (schemas, react-core, etc.) not covered by another area

apps/web (clinician-facing React SPA)

Type: existing behavior is wrong

Type: maintenance with no user-visible change (dependency upgrades, tooling, tests, refactors)

Pull requests that update a dependency file

More than a day, or touches several workspaces

Isolated change, about 2 hours or less

Straightforward change, about a day or less

Multi-week or architectural; needs a written design before implementation

Type: an open design question that needs a decision before work can start

Type: user, admin or developer documentation only

Type: an improvement to an existing feature, including performance

Type: a new capability that does not exist yet

Pull requests that update GitHub Actions code

Well-scoped, low-risk and self-contained; a good entry point for a new contributor

Pull requests that update javascript code

Well-defined, but blocked on a maintainer decision about direction or design

Cannot act until the reporter or a maintainer supplies more information

Speed, memory or scalability

Data loss, security exposure or a broken core workflow in production; drop other work

Significant or frequently hit user impact; target the next release or two

Nice to have, cosmetic or speculative

Real value; schedule normally

Authentication, authorization, data exposure or a vulnerable dependency