Victus is a modular scientific knowledge platform for nutrition and food-related health evidence.
This repository is the documentation control plane for the Victus ecosystem. It owns global architecture, shared contracts, architecture decisions, and AI-agent navigation.
Victus documentation follows a hybrid Hub-and-Node model:
000-SYSTEM-CONTEXT.md
100-ARCHITECTURE.md
200-OPERATIONS.md
300-CONTRACTS.md
decisions/
The numbered files are Maps of Content. Detailed documents remain in their owning folders and are linked from these hubs.
| Reader | First document | Next document |
|---|---|---|
| Human | README.md | 100-ARCHITECTURE.md |
| AI agent | AGENTS.md | 100-ARCHITECTURE.md |
| Architecture reviewer | 100-ARCHITECTURE.md | decisions/ |
| Contract reviewer | 300-CONTRACTS.md | docs/contracts/artifacts.md |
Victus is organized around:
| Repository | Responsibility |
|---|---|
victus-docs |
Global documentation, contracts, ADRs, and agent-readable navigation |
victus-infra |
Infrastructure, networking, storage, secrets, observability, and deployment foundation |
victus-processing |
Paper ingestion, extraction, structured blocks, canonical evidence, and embeddings |
victus-rag |
Retrieval, vector database integration, API orchestration, prompts, and answers |
Implementation details and source changes belong in the owning repositories.
Agents can use synchronized repository documentation as read-only context:
| Repository | Mirror entrypoint | System context | Architecture | Operations | Contracts |
|---|---|---|---|---|---|
victus-infra |
README | 000 | 100 | 200 | 300 |
victus-processing |
README | 000 | 100 | 200 | 300 |
victus-rag |
README | 000 | 100 | 200 | 300 |
These mirrors are navigation and context only. Changes must happen in the owning repository.