# Using NovusLens Audience: People reading organisational records and taking evidence to a management discussion ## s00 · Start with one issue · Sign in and choose an organisation Start with the account your administrator supplied. Enter your login and passphrase, then select Sign in. Open Account menu to check your organisation and role. Choose an organisation to open its Overview. This film uses screenshots containing illustrative records. Pause at each screen and follow the same actions with the records your account can see. Sources: - apps/docs/content/using/sign-in-and-twins.mdx - apps/docs/content/manuals/user-manual.mdx ## s01 · Start with one issue · Find your way around Five destinations organise the application. Overview selects items to review. Organisation contains the map and accountability views. AI agents compares declarations with observations. The questions destination lets you find records or ask about them. Records contains knowledge, activity and the management brief. Pages sit beneath the destination you have open in the navigation on the left. Open Docs for the full Product Guide and manuals. Sources: - apps/docs/content/using/index.mdx - apps/docs/content/using/overview.mdx - apps/docs/content/manuals/user-manual.mdx ## s02 · Start with one issue · Choose one Overview item The Overview selects up to five items from available records. Read the issue, why it merits review, the accountable owner and its limitations. This selection is not a ranking of business risk. Select Inspect supporting records to investigate. Select Open responsible team to see its context. An absent owner means no name is recorded here. Sources: - apps/docs/content/using/overview.mdx - apps/docs/content/manuals/user-manual.mdx ## s03 · Check evidence and scores · Read the evidence labels Told means someone stated it. Shown means a document supports it. Measured means a connected source recorded it. These labels describe the evidence available. A source can still be incomplete, old or contested. Illustrative and simulated records demonstrate the product. Open a supporting record and inspect its source before relying on its claim. Sources: - apps/docs/content/using/evidence-and-proof.mdx - apps/docs/content/manuals/user-manual.mdx ## s04 · Check evidence and scores · Select a team and open Evidence Open Organisation, then Map, and select a team. In the right-hand panel, select Evidence. Read the source, its location, who supplied the record and its strength. Compare the observation time with the time recorded here. Your role determines which parts of the source you can read. Sources: - apps/docs/content/using/evidence-and-proof.mdx - apps/docs/content/using/map.mdx - apps/docs/content/manuals/user-manual.mdx ## s05 · Check evidence and scores · Switch the evidence basis Use What we were told and Current evidence at the top of the panel. This changes both values and supporting evidence. Complexity, Agility and Recoverability are calibrated indicators. Open How these are assessed, with sources. Read the local formula, source and validity period. A score of sixty has no universal meaning. If the rule or current inputs are missing, keep the indicator unknown. Sources: - apps/docs/content/using/car.mdx - apps/docs/content/using/evidence-and-proof.mdx - apps/docs/content/manuals/user-manual.mdx ## s06 · Check evidence and scores · Look behind the indicators Open Complexity, change and recovery under Organisation. Choose Own operations or Including descendants. Read sources, dates, missing evidence and access limits. This calculation uses records for the scope; it does not average team scores. Coverage shows where records exist. Discuss gaps with the named owner. If no owner is recorded, ask your administrator to identify the person responsible for the review. Sources: - apps/docs/content/using/car.mdx - apps/docs/content/manuals/user-manual.mdx ## s07 · Explore the organisation map · Select and explore separately Return to Map. Select a box, or type a name in Go to a team or service. A box represents a team, service, supplier or AI agent. Summary, Findings, Changes and Evidence describe the selection. Double-click a box to show its units, or use the Summary control to open them. Selecting and opening detail are separate actions. Sources: - apps/docs/content/using/map.mdx - apps/docs/content/manuals/user-manual.mdx ## s08 · Explore the organisation map · Read dependencies and findings Dependency lines describe handoffs, with classes Loose, Buffered, Rigid or unknown. Inspect one recorded line and note both endpoint names for the later scenario. A dependency is separate from a reporting line or accountability. Select Findings to see Needs your decision. Inspect sources. Where permitted, use the form to record a response and read its receipt. Sources: - apps/docs/content/using/map.mdx - apps/docs/content/using/status-and-states.mdx - apps/docs/content/manuals/user-manual.mdx ## s09 · Explore the organisation map · Read the dependency-chain index The critical path length, shown as the dependency-chain index, adds structural weights along a chain. Loose contributes half an index point, Buffered one, and Rigid three. A Buffered link followed by a Rigid link totals four index points. Unknown dependencies are excluded and disclosed. Read this as structure. It is not elapsed time or money saved. Sources: - apps/docs/content/using/map.mdx - apps/docs/content/manuals/user-manual.mdx ## s10 · Find accountability · Find the recorded accountable person Open Organisation, then Accountability. Read the business area and the teams delivering it. Keep capability, authority, responsibility and accountable owner separate. They describe what a team can provide, what it may do, its duty and who is answerable. Follow a team name to its map and supporting records. An authority gap means nothing is declared here. Sources: - apps/docs/content/using/accountability.mdx - apps/docs/content/manuals/user-manual.mdx ## s11 · Find accountability · Compare agent declarations and activity Open AI agents. Compare each published declaration with available observations. Read the accountable owner and any withheld-gap count. A missed target does not establish excessive autonomy. An absence of open gaps does not establish that every control was assessed. NovusLens surfaces the evidence. The responsible people decide what action follows. Sources: - apps/docs/content/using/ai-agents.mdx - apps/docs/content/manuals/user-manual.mdx ## s12 · Find accountability · Keep remit and runtime evidence separate When available, the remit panel compares permitted operations, resources and destinations with observed activity. An incomplete remit can require review. Omission from an incomplete list does not establish prohibition. Keep export generated, deployment reported and enforcement observed separate. A declaration approved in the product records intent. A runtime deployment report is a separate source. Inspect its coverage and the records supporting any finding. Sources: - apps/docs/content/using/ai-agents.mdx - apps/docs/content/manuals/user-manual.mdx ## s13 · Ask and explore a change · Open contextual help Select the question mark beside a heading to open contextual help beside your current page. Read What you are seeing, How to read it, Limits and What you can do next. Close the drawer or press Escape to return. For the full Product Guide and manuals, open Docs. These pages explain the product and remain separate from your organisation’s evidence. Sources: - apps/docs/content/using/guide-and-help.mdx - apps/docs/content/manuals/user-manual.mdx ## s14 · Ask and explore a change · Ask a scoped question Open Ask and find, then Ask. Choose About the records for an ownership or evidence question. Choose the whole organisation, as far as your role can see, or one team from the list. Try: which capabilities have no owner? Select Ask. Read the applied scope, answer, why, sources and limits. Open source titles and inspect Other records consulted separately. Sources: - apps/docs/content/using/ask-and-answers.mdx - apps/docs/content/manuals/user-manual.mdx ## s15 · Ask and explore a change · Explore an assumed dependency change In Ask, choose Explore a change. In the first list, choose the dependency whose endpoint names you noted. If it is absent, return to Map and select an available dependency. If none are mapped, skip this exercise. Choose Loose, Buffered or Rigid as the assumed class. Select Explore this change. Read the assumption, baseline, changed index, coverage and trade-off. This indicative comparison does not estimate hours saved. Sources: - apps/docs/content/using/ask-and-answers.mdx - apps/docs/content/manuals/user-manual.mdx ## s16 · Records and a management brief · Read knowledge and recorded activity Under Records, open Knowledge library. Read each statement’s title, author, date, audience and source. If contributing is permitted, check the audience preview before saving. A recorded statement is not an independently accepted decision. Open Activity log to filter recorded actions by person, role, organisation, date and action. Changes links updates to their affected records. Sources: - apps/docs/content/using/knowledge.mdx - apps/docs/content/using/activity-log.mdx - apps/docs/content/manuals/user-manual.mdx ## s17 · Records and a management brief · Take a brief to the discussion Choose your organisation, then open Records and Management brief. The brief uses your account’s access and selects items by the Overview’s fixed rule. You cannot manually choose its cards here. Check the prepared time, owner, sources, coverage and uncertainty. Select Download HTML or Print and save as PDF. Source links require the recipient’s access. Open Account menu and select Sign out. Sources: - apps/docs/content/using/brief.mdx - apps/docs/content/using/sign-in-and-twins.mdx - apps/docs/content/manuals/user-manual.mdx