Skip to Content
ArchitectureOverview
Architecture

Four services and a database, one shared record.

A NovusLens twinTwinNovusLens’s model of one organisation, built from records about its teams, services and how they rely on one another. It is only as current as those records. runs on the customer’s own infrastructure. Its four service families are meshMeshA set of connected Mycelium services that exchange updates and keep the NovusLens log. nodes, reasoning, projectionProjectionThe regular pass that brings the read model up to date with the canonical log. It runs every 30 seconds by default. and the web application, alongside PostgresPostgresThe database software that stores the tables read by the NovusLens screens, along with document bodies, access records and protected personnel records.. The Docker deployment runs Postgres with the other services in one Compose file. ./lens setup writes the settings and starts the services. ConnectorsConnectorSoftware that reads records from a source system, such as an incident tool. A customer-written file connects those records to teams or services in NovusLens. run as jobs that feed the twin. Observations enter the MyceliumMyceliumThe application infrastructure underneath NovusLens. Its connected services exchange updates and keep the ordered structural log. mesh log. Existing log entries are kept. The log supplies the mapMapThe view of teams, services and their dependencies for the selected part of the organisation. Details appear beside the map., C/A/RC/A/RThree separate scores for a team or service: Complexity, Agility and Recoverability. Each uses current evidence and the customer’s stated scoring rules. (Complexity, Agility and RecoverabilityRecoverabilityThe R in C/A/R: how well a team or service restores acceptable service after a failure. Recovery times and tested alternatives can supply evidence.) figures, findingsFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner. and answers. The processes that build these views can be stopped and replayed.

Video explainerArchitectural Overview

6:08 running timePeople evaluating, explaining or operating NovusLens

Chapters (14)
Connectors add observations to the mesh log. The projection worker builds the Postgres read model. People read it through the web application and reasoning service. Blue marks the write path.

The interactive diagram goes further: it follows each path step by step.

Every deployed unit, what it reads and writes, and the boundary between the twin and the customer's own systems.

Explore the system layer by layer to see Docker, Mycelium, source connections and AI model calls in a wide diagram with labelled data flows.

These pages explain each service, the tools that run it, and the modules that provide its behaviour. Each page ends with the files to open next.

Mycelium mesh nodesThe connected services that keep the shared log.Reasoning serviceQuestions, answers, findings and agent accountability.Projection and read modelThe Postgres view rebuilt from the log, and the measurement engine.Connectors and meaningHow customer sources become observations.Web applicationThe product people use.Deployment and gatesRunning, backing up and checking a twin.
Last updated
TroubleshootingHow the system works