Skip to content

Viceroy NM / Evaluation guide

Capability is useful only when the boundary is clear.

This page states how we frame custom software and applied automation so buyers do not have to infer operating limits from marketing copy.

01 / Intended use

Support the work. Keep people accountable.

Viceroy NM evaluates custom applications, workflow systems, integrations, document and data processing, analytical support, and carefully bounded automation for defined government operations.

These capabilities are intended to structure and accelerate work performed by qualified people. They are not presented as a replacement for human authority in eligibility, employment, procurement-award, security-clearance, health, legal, financial, or other consequential decisions.

02 / Evaluation boundary

Define the environment before promising deployment.

Users
Named roles, responsibilities, access needs, and decision owners.
Data
Allowed sources, sensitivity, retention, movement, and handling requirements.
Systems
Authorized interfaces, dependencies, availability needs, and recovery expectations.
Approvals
Required security, privacy, acquisition, accessibility, and operational reviews.

03 / Human review

Automation proposes. Authority stays named.

Any automated or model-assisted workflow is scoped with explicit permissions, human checkpoints, escalation paths, evidence requirements, and recovery behavior. The exact control design depends on the task and engagement.

Model outputs can be inaccurate, incomplete, biased, outdated, or unsuitable for the intended use. Qualified review and task-specific evaluation are required before reliance.

04 / Current posture

Design direction is not an authorization claim.

Viceroy NM describes alignment to or work toward NIST AI RMF, OWASP, CMMC, and FedRAMP. It does not currently represent CMMC certification, FedRAMP authorization, an ATO, an FCL, personnel clearances, a FedRAMP sponsor, an SPRS score, or SOC 2. Exact controls and evidence are confirmed for the proposed scope.

Define the boundary before the solution.

Bring the users, workflow, environment, data, authority model, required reviews, and success criteria. We will identify the assumptions that need evidence.

Necessary technology is always active because it provides security and remembers this choice.