CATALOGUED PROJECT

SYSTEM / EVIDENCE / SOURCE

BotMedic

Discord incident-triage platform combining live diagnostics, telemetry, rule-driven troubleshooting, and generated support documentation.

Source Live system

Reading repository metadata…

EVIDENCE LEDGER

Verifiable project claims before narrative.

README: incident triage platform

Documents the TypeScript monorepo, Cloudflare Worker backend, Discord interactions, shared diagnostic rules, Workers KV telemetry, and companion support site.

Live application

Recorded diagnostic scope6 slash commands · 10 diagnostic rule cases · 10 generated runbooks

Recorded automated testing28 tests · 100% pass rate · 76.68% line coverage · 85.71% function coverage

CASE STUDY

From problem to working system.

01 / PROBLEM

Turn Discord support incidents into repeatable diagnostic flows without letting troubleshooting logic drift away from commands, documentation, or regression fixtures.

02 / APPROACH

Built a TypeScript serverless platform on Cloudflare Workers with Discord signature verification, Workers KV telemetry, shared command and rule packages, and a generated companion site.

03 / IMPLEMENTATION

The decisions that turned the approach into a working system.

Implemented six Discord slash commands and ten diagnostic rule cases backed by shared TypeScript metadata.
Validated Discord interaction signatures with Ed25519 checks and covered both valid and invalid signature paths in tests.
Generated ten runbook pages and companion-site command data from the same packages used by worker behavior and incident fixtures.

04 / OUTCOME

The recorded metrics snapshot reports 28 automated tests at a 100% pass rate, 76.68% line coverage, and 85.71% function coverage.

INTERACTIVE SYSTEM

BotMedic incident-triage console

Run the documented BotMedic command surfaces, replay representative support incidents, inspect matched diagnostic guidance, and watch browser-only telemetry accumulate.

In-browser portfolio simulation only — it does not connect to Discord, Cloudflare Workers, Workers KV, or the deployed BotMedic service. Representative incident fixtures are intentionally labeled and do not claim to reproduce all ten repository rule cases verbatim.

Incident-triage console

Run BotMedic's documented command surfaces against a compact browser-only support simulation. The real project routes Discord interactions through a Cloudflare Worker, shared command and rule packages, incident fixtures, Workers KV telemetry, and generated companion documentation.

Slash commands

Diagnostic rule cases

Generated runbooks

Automated tests

Repository evidence records 28/28 passing tests, 76.68% line coverage, and 85.71% function coverage. Those metrics describe BotMedic's recorded project snapshot, not this embedded simulator.

Slash command surface

Choose one of the six commands documented by the real project.

Command runner

Replay a fixture-backed support scenario and render diagnosis guidance.

Representative incident fixture

Selected symptom

Bot cannot respond in channel

high severity

A slash command is accepted, but the bot cannot send the expected follow-up in the target channel.

Simulated response

Bot cannot respond in channel

The interaction path is healthy, but the bot lacks a channel permission required for the requested action.

Interaction reached the worker.
Response path is available.
Channel action is rejected by the simulated permission check.

Matched rule

permission-path-blocked

Runbook

Permission diagnostics

Recovery sequence

1. Review the bot role and channel overrides.
2. Restore the required permission without widening unrelated access.
3. Re-run the permissions check and retry the command.

Browser telemetry

The real worker records telemetry through Workers KV and renders dashboard data. These entries exist only in local component state and demonstrate the observability flow.

2 runs1 diagnosed108 ms avg

Command	Outcome	Duration	Time
/health	ok	84 ms	Seed · 09:14
/incident	diagnosed	132 ms	Seed · 09:16

Source-of-truth design: BotMedic's real companion site is generated from shared command and rule packages, while incident fixtures also feed diagnostics and tests. The four scenarios embedded here are deliberately representative portfolio fixtures, not a claim that they reproduce all ten repository rule cases verbatim.

Representative incident fixture loaded.

Loading interactive workspace…

REPOSITORY DOCUMENTATION

README

Full repository documentation is available on demand for deeper technical inspection.

Expand full repository README

No README found for this repository.