Target doc structure #60
Notifications
Due Date
No due date set.
Blocks
Depends on
#61 Comment destination map
haylan/LLM-Server
#62 Agent guide: writing docs and extending the glossary
haylan/LLM-Server
#56 Audit: contradictions and duplicates across docs and code comments
haylan/LLM-Server
#57 Research-doc index: current vs. superseded
haylan/LLM-Server
#58 Removal inventory: image generation and Open WebUI
haylan/LLM-Server
#59 Glossary: pin down domain terms in CONTEXT.md
haylan/LLM-Server
#63 Intent vs. source: fix the config or fix the doc?
haylan/LLM-Server
Reference: haylan/LLM-Server#60
Reference in new issue
Block a user
Part of #55
Question
Which doc files exist after cleanup, what each explains, and which source each one links as its source of truth? Includes the fate of stale docs (e.g. docs/proxy-request-priority.md) and the README's role. HITL: prototype an outline to react to.
Resolution — target doc structure
Every doc opens with its Source of truth line (map Notes); terms per
CONTEXT.md.README.md./scripts/update.sh), index of every docdocker-compose.yml,scripts/update.shCONTEXT.mddocs/architecture.mddocker-compose.yml→ each service--cache-reuse; per-slot context math (3 copies → 1); n-gpu-layers/mmap; healthcheck; mem_limitdocs/gateway.mdproxy-key-onboarding.md. Provider connections live in the dashboard; API key create/hand-over/revoke; the three OmniRoute timeouts (one section → the 3 research docs); SearXNG web search + search.home gotcha; OmniRoute stealth/MITM cautiondocker-compose.yml→ omniroute,.env.exampledocs/network-access.mddocker-compose.yml→ ports/exposedocs/operations.mdupdate.shdoes and why: .env sync/conflict prompt, secret generation (storage-key warning stays inline in source too), host-resolved values, vendored gum, model downloads; manual deploy stepsscripts/update.sh,.env.exampledocs/coding-cli-setup/--jinjaduplicate, tool-calling risk (3 → 1)docs/server-planing.mddocs/research/README.mddocs/agents/Moves / deletes
docs/proxy-request-priority.md→docs/research/, marked superseded by the OmniRoute migration.docs/proxy-key-onboarding.md→ becomesdocs/gateway.md.Build plans: neither
server-planing.mdnorresearch/500k-context-2-parallel-agents-gpu-roadmap.mdis an active plan — both are labelled background research in the indexes; files unchanged.