The components, grouped by the job each one does.

What they are for

The web application is built from ReactReactThe library used to build the interface from reusable pieces called components. components in apps/ui/components. Together they provide the organisation mapMapThe view of teams, services and their dependencies for the selected part of the organisation. Details appear beside the map., findingsFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner., evidence, AskAskThe tab that composes an answer to a question in your own words, from the records, with each statement pointing to its sources. Ask answers only as far as your role can see., accountability, agent views, import, documents and GuideGuideThe help pages inside NovusLens. They explain the pages, input formats and tasks in the version you use. They are product instructions, not evidence about the organisation.. A reader sees these as pages; an engineer maintaining them needs to know which component owns which view and where its data comes from.

This page groups the components by feature. For each group it gives a short description and a table: the component, its role, and how it reaches data. Data arrives in one of three ways, and the tables say which:

• PropsPropsValues a parent component supplies to another component, such as the organisation identifier or records it should display. from a server page. A page under apps/ui/app loads the 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. with loadTwinForPage (in apps/ui/lib/pageAccess.ts) and passes the result down as props.
• A fetch to the reasoning proxyProxyA service that receives a request and forwards it to another service. The NovusLens web proxy adds the signed-in identity and service token.. Browser code calls /api/reasoning/.... The route handler at apps/ui/app/api/reasoning/[...path]/route.ts forwards the call to the reasoning service.
• A fetch to a small route. A few components call /api/guide/{id} (help text) or /api/access/record (a receiptReceiptA recorded acknowledgement of a request or action, with its identity, time and result. An evidence intake receipt confirms storage. It does not establish acceptance or prove that an agent acted. check).

The shell and navigation

Every organisation page starts with the same header, navigation, refusal pattern and account controls. These components are what a reader sees before any content.

OrgHeader is the one header for organisation pages. It renders FidelityStrip, the live fidelityTwin fidelityCounts of the model's sourced facts at the told, shown and measured evidence levels. It describes the available support, not whether the claims are true. read-out with a plain-words explainer for each term. WorkspaceNav holds five destinations (organisation and records), with pages nested beneath the active destination in the left navigation. On phones, a navigation drawer presents the same links. AccessRefusal is the single refusal pattern, with three states: sign in, no access, and erased. Every page that loads a twin uses it when loadTwinForPage refuses.

The shared controls use shadcn sources in components/ui/ and the semantic theme in app/globals.css. The sign-in form uses Button, Input and Card. Overview items use Card. The theme follows the Novus paper, navy and blue brand, with self-hosted Source Sans. Focus outlines remain visible, and reduced-motion preferences apply to transitions.

The twin and the map

The twin surface is one page with several lenses. TwinView is the client shell: it holds the Twin lens (the graphGraphA model made of units and links between them. In NovusLens it records teams, services and their dependencies. and a context panel), the Accountability Map, Alignment and Ask. Selection, lens, view and drill-down live in the URL. The page passes the snapshot in as props, and TwinView itself does not fetch.

TwinGraph draws the graph with CytoscapeCytoscapeThe library that draws the interactive boxes and dependency lines in the organisation map. and places its units automatically using the ELKELKThe layout library that decides where the map boxes and lines are placed. It runs in the browser from code included with the application. layout library. It imports cytoscape and cytoscape-elk, then registers cytoscape.use(elk) at load. Bundled elkjs computes the layout in the browser without external downloads. The elk layout uses elk.direction: DOWN and INCLUDE_CHILDREN for hierarchy handling. This lets a selected team open in place to show its units. Selecting a node and drilling into it are separate gestures: a tap selects, and a double-tap or the panel’s button drills. If 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. are unmeasured, the node stays neutral. Complexity alone cannot determine its colour.

The Accountability Map, Alignment and Domains views are sub-views of TwinView. Each takes the twin’s cellsCellA 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., edges or domains as props. The Accountability Map and the Domains view open a team through an onOpen callback, so the change happens in place, without a reload. CarAssessment is the one exception: it is the complexity, agility and recoverability assessment on its own page at /car, and it does fetch.

Group of twins

A group is several regional twins seen together. The Group page shows each member’s published summary and the signed, verified facts that cross a region boundary. Raw in-region graphs are not shown here.

Findings and the evidence rail

The rail is the side panel beside the twin. It has four tabs, Summary, Findings, Changes and Evidence, and the active tab is held in ?tab=. The header holds the breadcrumb, the team picker and the switch between told and current evidenceCurrent evidenceA view that uses only measurements recent enough to count. The “What we were told” view uses recorded statements instead.. The rail is the place where a reader moves from a number to the record behind it.

Each finding carries a recorded detail, shown as labelled lines rather than raw JSONJSONJavaScript Object Notation: a text format for data, using named fields, lists and values. Configuration files and service messages use it.. For a generated finding, GeneratedFindingReview shows the support review that GET /api/reasoning/findings/support-review returns. Items that need a decision come first in NeedsDecision, and each carries the one action it needs. The evidence drawer lists the records behind a team or a finding, and it is where a reader can challenge a record. A challengeChallengeA recorded dispute of a value. Both the original and the disputed version are kept, and the challenge is listed under Findings., a resolution or a retractionRetractionThe withdrawal of a finding or meaning entry, with the reason recorded. The record keeps who withdrew it, when and why; it is not deleted. is a form in the drawer that ends in a receipt. The page never uses window.prompt.

Asking and answering

Ask is one field with a visible scopeScopeThe work, data, activity or access that a rule, statement or calculation covers. For access, it names the records an account can see. For team measures, “Own operations” covers the selected unit. “Including descendants” adds the units beneath it. and examples that fill it. An answer is shown as the answer, the reason it holds, its numbered sources, and what it does not establish. Saved questions have their own tab. The in-progress question is kept in sessionStorage, so switching tabs does not lose an answer that is still coming.

Ask does not answer from the browser. QuestionPanel posts to the reasoning service through the proxy, and reads the answer back with polling. The Interrogate panel adds two more routes on top of Ask: a named what-ifWhat-ifA scenario that changes one or more dependencies in the model and reports the result. A what-if changes nothing in the records, and its result is indicative. (tools/simulate_scenario) and a search. The cell chat is the reverse path. It captures what a reader tells the twin about one team. A document handed over mid-conversation is ingestedIngestRead supplied records or documents and add their information to NovusLens, after the required checks. inline, and its rung moves from told to shown in the same conversation.

Accountability and agents

The agent views show what each operational agent is permitted to do, and what it did. They are evidence for the customer’s own review, not a verdict. The governance lens states the evidence ladderEvidence ladderThe three levels of support a record can have, in order: told, shown and measured. once: a claim taken from the agent’s published facts, moving toward what the boundary telemetryBoundary feedRecords supplied by the customer’s own systems about activity at the edge of an agent or service. NovusLens reads those records; it does not watch the agent. observed. Each control gap is shown as evidence for the compliance function.

The remitRemitA written list of an agent’s allowed actions, resources and destinations for information. The list states whether it is complete. is the permitted scope of one agent: its operations, resources and destinations. RemitPanel shows that scope beside each observed activity, with the comparator’s result and the classification of any detector. An incomplete activity stream is shown as incomplete, never as clear. DeclareRemit lets a responsible person author a remit in the product. A draft publishes nothing, and approval comes from the named responsible person.

Meaning and import

Two surfaces change what the twin holds from outside it. The meaning panel manages the knowledge libraryKnowledge libraryThe organisation’s written procedures and definitions. Each entry records its source, date and who can read it. NovusLens cites these entries as supplied information.: scoped entries, an ingest form and retraction. The import panel takes an organisation chart, an interview transcript or a structured file, and shows what it proposes before anything is written.

In the import panel a person confirms every proposal. An org chart seeds a new twin’s team skeleton as shown, with no flow between teams. A transcript builds from nothing as told, or, against an existing organisation, challenges the skeleton and records contradictions as contested entries rather than edits. The panel can also export the org chart as the twin now knows it, with the evidence levels and recorded disputes marked. The import page passes readOnly for anyone who is not an operator.

Guide and brief

The Guide is the product’s own help. Docs opens the documentation bundled from apps/docs behind the reader’s session. app/guide/page.tsx redirects stable help identifiers to their local Guide pages. An unknown identifier shows links to the index and manuals. The complete User Manual and Operations Manual each remain one scrolling tutorial. Documentation search uses a local Pagefind index. The question-mark control still opens a help drawer, which reads a Guide page through app/api/guide/[id]/route.ts. See the Guide and help for the reader’s steps.

The briefBriefThe management brief: a printable summary of the differences to review, with their sources, observation dates and limits. It is a snapshot taken when it is printed. is a print-ready page. PrintBrief is the one control on it, a button that opens the browser’s print dialogue. The brief itself is rendered by app/brief/page.tsx, which uses OrgHeader, WorkspaceNav and AccessRefusal.

Shared interface controls

The controls under components/ui provide shared behaviour: the drawer and receipts, the form for a reason, tabs, help links, provider wiring and the time display.

The receipt is the most important of these. When a reader performs an action, a receipt says what happened. Receipts are kept for the session, and each is bound to the account it was issued under. When a receipt is reopened, its content appears only after /api/access/record answers 204 for that organisation. A refusal or an unavailable check shows a message and no content.

Open the diagramHow the page components, the rail and the primitives nest, and which proxy routes each one calls.