Below five people, a count is a name.
NovusLens keeps individual personnel records out of product pages. The key-person findingFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner. reports a small team with fewer than five mapped people, without names or exact counts.
What you will see
The key-person finding says that 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. on the measured critical pathCritical pathThe dependency chain with the greatest total coordination weight in the map. It identifies a structural constraint. It does not state elapsed time. has fewer than five people represented in the personnel mapping, and stops there. No answer, screen or export names the person, at any level of privilege, including the board. The constant is PRIVACY_FLOOR = 5 in keyperson.py.
A very small 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. therefore reads less precisely. That is the floor working, not an absence of risk.
What to do about it
Acting on the finding belongs to the accountable ownerAccountable ownerThe person recorded as answerable for a team, service or agent. NovusLens does not assume that this person is also the one who runs it day to day.. NovusLens surfaces where the exposure sits and advises. It does not say who the person is and does not change the team. For how the finding is raised, see Complexity, Agility and Recoverability. For how people are loaded and their identifiers replaced by hashesHashA fixed-length fingerprint calculated from content. Comparing fingerprints helps detect changes and match records., see the people export.