# Product Overview Audience: A first-time viewer with no knowledge of NovusLens or its framework ## s00 · Product Overview · Product Overview Changing a service can affect teams you never expected. Novus Lens helps you see those connections and the evidence behind them. This guide follows one question: if we change this service, who else is affected? Sources: - apps/docs/content/start/what-is-novuslens.mdx ## s01 · The problem · The organisation chart leaves questions unanswered Imagine your organisation is replacing a customer service system. The organisation chart names the teams, but it does not show every handoff. Operations relies on a data team. That team depends on a supplier. An AI agent also uses the service. Their records sit in different places. Before changing anything, you need to understand those relationships and who answers for them. Sources: - apps/docs/content/start/what-is-novuslens.mdx - apps/docs/content/concepts/organisation-model.mdx ## s02 · The solution · Find the people your change affects Novus Lens brings teams, systems, suppliers and AI agents into one inspectable model. We call it an organisation twin. A connection shows that one part needs something from another. Select a team or service to see its recorded owners, dependencies and supporting evidence. The twin reflects the records supplied to it, so missing information remains a question to investigate. Sources: - apps/docs/content/concepts/organisation-model.mdx - apps/docs/content/start/first-hour.mdx ## s03 · Bring in the evidence · Use your existing records to establish the picture Start with an organisation chart to identify teams and reporting lines. Add policies and service documents to explain responsibilities. Supported infrastructure exports describe systems, while configured connections bring in operational records. People can contribute what they know. These inputs build different parts of the picture. An imported chart alone cannot establish how work actually moves between teams. Sources: - apps/docs/content/architecture/how-it-works.mdx - apps/docs/content/concepts/organisation-model.mdx ## s03a · How it works · From records to a connected picture Imports read company files, while configured connections bring in operational records. Novus Lens turns structural records into teams, systems and relationships you can inspect. It keeps supporting evidence alongside that picture, so you can return to the source. Sources: - apps/docs/content/architecture/how-it-works.mdx ## s04 · Understand the support · Know what supports the decision Each claim carries an evidence label. Told means somebody stated it. Shown means a document supports it. Measured means a source recorded an observation. In our example, a team says recovery takes one hour. The plan states the same target. An incident record shows two hours on one occasion. Read each source, its date and what it covers. The label describes support, not certainty. Sources: - apps/docs/content/concepts/evidence-ladder.mdx ## s05 · Investigate differences · Turn conflicting accounts into a useful question Those different accounts are useful. A recovery target and an incident outcome describe different things. Novus Lens preserves their sources so people can investigate the difference. It also surfaces gaps in recorded ownership and disagreements about structure. A finding is an item to review. It gives the people involved something specific to examine before deciding what needs to change. Sources: - apps/docs/content/concepts/evidence-ladder.mdx - apps/docs/content/concepts/organisation-model.mdx - apps/docs/content/start/first-hour.mdx ## s06 · Keep organisational knowledge · Keep the knowledge behind the decision Relationships tell only part of the story. For this service change, the Knowledge library can retain the recovery procedure and explain the supplier's role. It holds procedures, definitions and written accounts linked to the teams they concern. Each entry keeps its author, date and audience. These records can support answers to questions. A written account remains its author's statement and can be challenged or withdrawn. Sources: - apps/docs/content/using/knowledge.mdx - apps/docs/content/architecture/how-it-works.mdx ## s06a · How it works · From evidence to an answer When you ask a question, Novus Lens retrieves records you are permitted to see. Its reasoning service uses configured AI models where interpretation is needed. The result links the answer to supporting sources. Your organisation can run this system on its own infrastructure. Sources: - apps/docs/content/architecture/how-it-works.mdx ## s07 · Ask a practical question · Take a sourced answer into the discussion Return to our service change. Use the organisation view to inspect connected teams and their recorded owners. In Ask and find, ask who is accountable for the service. Novus Lens retrieves relevant records and uses configured AI models where interpretation is needed. Answers link statements to sources and state their limits. You can bring the ownership record into the discussion, and show everyone what supports the answer. Sources: - apps/docs/content/using/ask-and-answers.mdx - apps/docs/content/start/first-hour.mdx - apps/docs/content/architecture/how-it-works.mdx ## s08 · Assess a possible change · Read measures alongside their evidence You can examine Complexity, Agility and Recoverability: the current structure, ability to change and ability to restore service. These scores depend on documented local rules and available evidence. Separately, Explore a change compares the dependency-chain index under one assumed change to a handoff. This index describes the weight of the longest dependency chain. The comparison helps people discuss trade-offs. It does not estimate time or money saved. Sources: - apps/docs/content/concepts/car.mdx - apps/docs/content/using/ask-and-answers.mdx ## s09 · Include AI agents · Identify accountability gaps before assigning work When an AI agent takes on work, someone must answer for its outcome. Novus Lens separates what it can do, what it may do and who is responsible. Compare reported activity with recorded permissions. If ownership is missing or the accounts differ, you have a specific question to put to the people responsible before assigning more work. Sources: - apps/docs/content/concepts/agentic-accountability.mdx - apps/docs/content/concepts/layer-boundary.mdx ## s10 · Use the result · Bring a decision brief, not scattered records Return to the service change. The affected teams, supplier and agent owner are now visible. Bring them together around a management brief with the supporting records. In our example, the recovery plan says one hour; the incident record says two. Ask the service owner to review that difference with Operations and the supplier. Record the review and the decision. Everyone can examine the same basis for proceeding. Sources: - apps/docs/content/start/first-hour.mdx - apps/docs/content/architecture/how-it-works.mdx ## s10a · Value through change · Keep the understanding you have built The next change need not start from scattered records again. Keep the decision, its sources and the explanation behind it. Suppose a new supplier record arrives. Revisit the affected relationships and the recovery question. Your team can inspect the new account alongside the earlier review. The organisation retains the context for its next decision. Sources: - apps/docs/content/guide/concept-rail-changes.mdx - apps/docs/content/using/knowledge.mdx ## s11a · The value to your organisation · See the consequences before committing A service change reaches beyond the team leading it. Novus Lens makes the recorded dependencies visible: the data team, the supplier and the agent using the service. Follow those connections to find who needs to be involved. You can take the proposal into review with its wider implications in view. Sources: - apps/docs/content/start/engagement.mdx - apps/docs/content/start/what-is-novuslens.mdx ## s11b · The value to your organisation · Find where the accounts disagree The organisation chart places a team in Operations. A team account names a different reporting line. A division record gives another view. Which account applies to this decision? Novus Lens keeps the sources distinguishable and supports review of contradictions. Novus-i2 advisers help you examine the evidence, its dates and scope, and work through the disagreement. You gain a question to resolve before relying on the picture. Sources: - apps/docs/content/start/engagement.mdx - apps/docs/content/start/what-is-novuslens.mdx - apps/docs/content/using/overview.mdx - apps/docs/content/architecture/how-it-works.mdx ## s11 · The value to your organisation · Managing Organisational Transformation Know what your change affects. Give the right people a shared basis for deciding. Keep the evidence and understanding for the next change. That is the value of Novus Lens alongside Novus-i2 advisory support. Start with one transformation decision. Build towards an organisational twin your team can run, use and retain. Sources: - apps/docs/content/start/engagement.mdx - apps/docs/content/start/what-is-novuslens.mdx