Files
tazlin 5e0456b616 feat(moderation): filter prompt events by reason
- `GET /operations/moderation/prompts` takes a repeatable `reason`; an unknown value is `400 InvalidModerationReason`
- `(reason, id)` index on `prompt_moderation_events` in the model and `sql_statements/5.1.14.txt`, so a page of a rare reason does not walk the common ones
- `hold_source` on each listed event (`note`, `account_status` or null), computed in the page query from the same predicates `_under_moderation_action` applies, so the listing never disagrees with retention; nothing is stored and there is no release
- the migration test applies every migration that changes a moderation table, now 5.1.12 and 5.1.14
- version 5.1.14
2026-10-03 00:57:55 -04:00
..
2026-08-19 14:02:10 -04:00

AI Horde service documentation

How this repository's service is built and how it is run:

  • Explanation: why a subsystem is built the way it is.
  • Reference: contracts, schemas, gate orderings, and code maps.
  • How-to: integration guides; procedures for AI-Horde operators and developers.
  • Decisions: dated records of each choice, the alternatives, and the consequences.
  • Topics: the same documents grouped by subject.

General Horde concepts (what the Horde is, workers, jobs, kudos) live in haidra-assets/docs. This tree assumes them.

Some subsystems are listed but not yet written up. Those pages describe the subsystem in a paragraph and point at the code that holds the behavior.