Skip to Content
Product GuideInput format: the domain taxonomy

Input format: the domain taxonomy

Run the commands below from the installation directory. See Run operator commands for how ./lens reaches the running installation and copies files into it.

The taxonomy is the business view of the organisation, gathered in one workshop: which domains exist, who owns each, which teams serve each. It is ingestedIngestRead supplied records or documents and add their information to NovusLens, after the required checks. with:

From the installation directory:

./lens connectors domain-taxonomy --org harbour --fixture taxonomy.json

On success the command prints a summary of what it wrote and exits 0; the map shows the result after the projectionProjectionThe regular pass that brings the read model up to date with the canonical log. It runs every 30 seconds by default. service’s next pass (about 30 s by default). A refusal names what was wrong.

It lands at the shown rungRungOne of three levels of support for a recorded value: told, shown or measured. The level appears beside the value.. A cellCellA box on the map that stands for a team, service, supplier or AI agent. It is a unit you can inspect, not necessarily a department or a person. named here that does not exist in the map raises a findingFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner. and is not invented. Where this carving and the team carving disagree, the map shows the disagreement as a misalignment.

Required fields

  • domains: a list. Each domain needs domain_id (lower case, no spaces).

Optional fields per domain

  • label: the display name. Defaults to the id.
  • description: one sentence.
  • accountable_owner: a name or role.
  • cells: the ids of the cells that serve this domain.

Minimal valid example

{ "domains": [ {"domain_id": "freight", "label": "Freight movement", "accountable_owner": "Chief Operating Officer", "cells": ["bookings", "warehousing"]}, {"domain_id": "compliance", "label": "Border compliance", "accountable_owner": "Head of Customs", "cells": ["customs"]} ] }

What a re-run does

SituationWhat happens
Stable identityThe domain id, slugged; a mapping is the pair of cell and domain.
The same file twiceDomains and mappings written again; no change.
A changed label, description or ownerThe latest wins. A field omitted keeps its old value.
A cell added to a domainA new mapping.
A cell removed from a domain’s list, or a domain omittedThe mapping and the domain stay. The taxonomy can only grow; there is no removal.
A renamed domain idA new domain; the old one and its mappings stay.
A mapping naming a cell the map lacksNot mapped; an undeclared-domain-cell finding opens and does not close by itself.
An entry without a domain idSkipped, and not counted in the summary.

Read more

Last updated