Run the demonstration cases
All three cases are simulated and say so on every record. They exercise the real path: signed intake, projectionProjectionThe regular pass that brings the read model up to date with the canonical log. It runs every 30 seconds by default., assessment, findingsFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner., notifications.
Use an approved demonstration organisation with existing agent and owner 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.. These commands activate simulated evidence sources and write records. They are not a read-only preview of a customer’s estate. Use your actual operator login; the installer may have created a name other than operator.
For Docker, run the first phase inside the configured reasoning containerContainerA running program with its own packaged software and isolated environment, managed by Docker on the host.:
./lens connectors agent-demo --org <org> \
--viewer <operator-login> --agent-cell <agent-cell> --owner-cell <owner-cell> --phase initialReplace every angle-bracket placeholder. The cells must belong to the named organisation. Keep the same running container and repeat the command with --phase correction to send the later correction. The command keeps its case state in that container’s temporary directory. These cases use stored fixturesFixtureA prepared set of records used for a test or demonstration. A fixture is sample data, not a live customer's records.; they do not require a language modelLanguage modelSoftware that produces text from instructions and supplied context. NovusLens checks its answers against the records retrieved for the question..
- The five-step case:
agent-demo --phase initial, read the case, then--phase correction. An operation outside a limit, an authorisation, an execution, an observation, and a correction that withdraws the earlier support without rewriting history. - Several agents over their mandate: add
--fleet 3, with--agent-cellnaming the unit the fleetFleetA group of AI agents considered together. Related activity can be grouped only when the records establish what the agents share. serves. One fleet incidentFleet incidentA finding about several agents that completed the same operation above their recorded limits in one period. The agents must share something recorded in the model. above three member cases. - Activity outside a declared remitRemitA written list of an agent’s allowed actions, resources and destinations for information. The list states whether it is complete.:
--scenario drift. Thirty workers on one shared credential, three flows to an unlisted destination, one later re-attributed; a containment authorised by the responsible person, executed, and observed with a route unseen (no all-clear), and a second containment whose execution failed.
Re-running a case with --fresh enrols new keys under the same source names, so the earlier run’s findings are withheld. The development driver’s ./lens ops walk resets its separate development installation. It does not reset the Docker demonstration. See the operator shell for Docker command context.