mirror of
https://github.com/Haidra-Org/AI-Horde.git
synced 2026-11-06 05:17:31 +00:00
tazlin
0822891e84
Broad editorial pass over docs/ plus a nav update in zensical.toml. - Wording and style: replace "carries"/"answers" phrasing with plainer terms, use periods instead of semicolons, and split long paragraphs. - Structure: add subheadings and tables in the chat, moderation, kudos, model reference and style contract docs. Add "Code map" and "Contract tests" sections to several reference pages. Move the code maps in chat_front.md and chat_requests.md to the end of those pages. Reorder the minimal chat worker page so the procedure comes before the source listing. - Content fixes: - Document the 404 ChatJobAborted vs ChatProgressNotStreaming progress responses. - Document the availability refusal table (503/404/400). - Document fail-fast admission and queue-position refresh. - Fix the stream parser example to check response.ok and error on a missing [DONE]. - Fix the style contract's max_length ceiling (16384). - Note that the kudos heartbeat metrics are quorum-node only. - Clarify tool_choice, strict conformance and capability caveats in the tutorial. - Navigation: reorder Tutorial and Topics in the docs landing page and zensical nav. Exclude /openai-chat-local/ from builds. - Chat doc summaries were rewritten in several front matter blocks and the generated README tables updated to match.
1.1 KiB
1.1 KiB
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 and procedures for AI-Horde operators and developers.
- Tutorial: a first working result, step by step.
- 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.