DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to log an outage with its fix so the next one is faster with Kyb

Capture what broke, the affected windows and how it ended as a searchable incident report.

Authorization notice. Kyb is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn on-call engineer or agent handling a production incident who wants the fix findable the next time the same failure happens.

The problemIncident lessons evaporate when the session ends, so the same failure gets debugged from scratch.

The outcomeA structured incident report with a detection check, affected windows and a resolution that agents can search later.

What you need first

  • A Rust toolchain with cargo, to run cargo install knowyourbusiness --locked
  • A host or Docker setup where the kyb-server process can keep its data directory
  • Network access from agent machines to the server port, default 127.0.0.1:9310
  • Optional: a model directory with model.onnx and tokenizer.json for hybrid search; without it the server runs lexical-only

Steps

  1. Print the report skeleton with kyb incident --template.
  2. Create the report with kyb incident --key inc-2026-07-22-orders-api-oom --title "..." --service orders_api --severity high. (inferred, check the README)
  3. Add a detection check with --detection "check + healthy result" and affected windows with --affected as a JSON list of scope, from and to.
  4. Link related knowledge entries with --knowledge <key> and list hosts with --hosts <host>. (inferred, check the README)
  5. Check the record and its history with kyb history inc-2026-07-22-orders-api-oom. (inferred, check the README)

Prompt for your agent

Use the KYB repo at alex09x/kyb. Create an incident report for <service> using `kyb incident` with the key inc-<date>-<service>-<short-name>. Expected output: the server reply, including any hints about missing parts. Verify that the reply has no missing-field hints, or list the hints you still need to fix.

Caveat. The README says closing an incident requires a resolution and archives it, so plan to write the resolution before you close it, not after.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for alex09x/kyb and "Log an outage with its fix so the next one is faster"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer