Core Diagnostics
- GET /health
- GET /offline/health
- GET /offline/modules
- GET /offline/search
- POST /search
- GET /troubleshoot/flow
- POST /reference/find
- POST /rca/analyze
- POST /screenshot/analyze
Map
Scan the current surface area across web, mobile, and API when you need a capability overview.
Horologium App Map
Review the current product surface without mixing that reference view into the daily solve workflow.
Supported scope
The seeded offline repository spans functional, cross-module, and Basis-adjacent support scenarios.
Category 01
A single-screen consultant cockpit that keeps issue intake, status, and navigation visible.
Category 02
The core support engine that turns issue text, screenshot hints, and context into next actions.
Category 03
Operational tooling for turning diagnosis into owned work, reusable fixes, and structured documentation.
Category 04
Features that expand the system beyond seed data and train consultants over time.
Category 05
Shared-work features for support teams that need assignment, collaboration, and expert routing.
Category 06
Commercial controls, usage visibility, and outbound workflow connectivity.
Category 07
Provider-aware features and runtime architecture that support future upgrades without changing the UI.
Backend map
These groups represent the main backend surface used by the product clients and the QA scripts.
Implementation notes
These are the important real-world constraints in the current repository state.