Ping flow
Launch /health → Worker validates signature → ephemeral reply.
Command gallery
Built, tested, deployed, and measured
BotMedic includes Discord request verification, shared command/rule metadata, incident fixtures, generated runbooks, Vitest regression tests, CI deployment, and a metrics report generated from repo and CI evidence.
The public report keeps portfolio claims tied to raw artifacts instead of hand-counted numbers.
Review metricsArchitecture diagram
Discord user
Launches /health or /helpme from a guild member context.
Cloudflare Worker
Validates signatures, routes commands, writes telemetry, returns ephemeral response.
Command/Rule layer
Switches on command name, consults rule cases, and builds internal + customer replies.
Runbook surfaces
Static site, runbook library, and incident gallery explain failures for reviewers.
Each step mirrors the documentation in docs/architecture/README.md: Discord signs the payload,
the worker validates it, routes to the command handler, and optionally writes to Workers KV for dashboards.
Failure gallery
Runbook library preview
Runbooks mirror the RuleCase logic in @botmedic/rules and expand what teams need to do.
Walkthrough highlights
Symptom intake
Select symptom → button interaction → internal/customer response.
Runbook handoff
Case data becomes static runbook, bridging polished explanation + raw logic.
How diagnosis works
Each symptom button routes through @botmedic/rules. Evidence gains a confidence score, a
diagnosis string is assembled, and the worker returns internal and customer-friendly text in buildSupportResponseSections.
This static page explains the flow and proofs that runbooks keep the story aligned with the worker logic.
Read the full explanationNeed a quick checklist? See what to check first.