| title |
Omnius documentation |
| description |
Evidence-qualified entry paths for backend, web, LLM, and MCP users. |
| status |
experimental |
| implementation |
implemented |
| profile_availability |
|
| public_exposure |
not-applicable |
| audience |
evaluator |
rust-application-developer |
application developers |
ai-application-developer |
mcp-developer |
operator |
|
| topics |
getting-started |
navigation |
evidence |
|
| capabilities |
|
| source |
docs/navigation.md |
docs/evidence-inventory.md |
docs/coverage-matrix.md |
|
| evidence |
apps/server/src/main.rs |
web/src/app.tsx |
crates/llm-http-api/src/lib.rs |
apps/mcp-server/src/lib.rs |
|
| last_verified |
2026-09-03 |
Start with the overview for the product boundary. Omnius includes checked-in minimal backend, OAuth/API, and authenticated tools-only MCP processes plus broader backend, web, LLM, and MCP libraries, generators, contracts, and tests. A profile or generated artifact does not by itself prove that a capability is assembled or publicly reachable; check the availability and exposure matrix before following a broader path.
| Journey |
Start here |
What the current path establishes |
Continue with |
| Backend |
Minimal-service quickstart |
A runnable checked-in process with a small assembled HTTP and lifecycle surface; it does not establish the broader generated profile as assembled. |
Choose a profile, configuration and secrets, and HTTP APIs |
| Web |
Web integration quickstart |
Checked-in React and SDK integration evidence, not a browser application assembled into the active backend runtime. |
Application architecture, generated contracts and SDK, and browser security |
| LLM |
LLM integration quickstart |
A deterministic library and contract evaluation path, not a mounted LLM HTTP surface. |
Model requests and responses, providers and routing, and HTTP and web integration |
| MCP |
Authenticated MCP server quickstart |
A dedicated OAuth-authenticated Streamable HTTP process at POST /mcp exposing only reference_records.list.v1; optional primitives remain unassembled. |
Server architecture, protocol support, and the MCP capability matrix |
- Availability and exposure matrix — compact implementation, profile, and exposure classifications.
- Coverage matrix — capability owners, evidence, verification gaps, and contradiction notes.
- Evidence inventory — source hierarchy, stable capability registry, and inspected evidence.
- Modules, profiles, and composition — canonical semantics for selection, generation, assembly, and exposure; profiles and modules and capabilities provide the exact machine-catalog selections and identifiers.
- Glossary — direct links from terms to their sole canonical concept owners.
- Documentation navigation and ownership — complete page inventory, ownership, and review ring.