FOR REGULATED AI TEAMS # Create a reviewable system record for regulated AI work . Viorant helps regulated AI teams prepare a clearer record for internal review: a `.vio` definition composes the meaningful artifacts of an AI system, and Trust can verify stated evidence without turning that verification into a compliance claim. [Explore Viorant Hub →](/hub)[Talk to Viorant →](/contact) Editorial visual for Regulated AI teams AI SYSTEM RECORD 01 Artifacts Signed, versioned system parts 02 .vio Portable system composition 03 Supported target Explicit transformation or deployment choice WHAT THIS MAKES POSSIBLE ## Make the AI system easier to understand . 01 ### Make the declared system reviewable Bring the components, relationships, and target choices that define the AI system into one portable record for review. 02 ### Verify evidence without overstating it Trust verifies artifact identity, integrity, provenance, signatures, and stated evidence; applicable controls and approvals remain with your organization. 03 ### Keep deployment decisions explicit Helix prepares or deploys definitions to supported targets, making the intended target a stated part of the system record. USE CASES ## Put the system record to work . Three practical ways regulated ai teams can use a declared AI system boundary to move a real decision forward. 01 USE CASE ### Prepare an internal control review Situation. A regulated workflow needs a clear description of the system under review and the evidence that can be examined without overstating what verification proves. Use a neutral system record to organize review material around the declared AI system. - 01 Identify the artifacts, relationships, and target choices that belong to the reviewed system. - 02 Compose or inspect the `.vio` definition as the declared boundary. - 03 Use Trust to verify stated artifact evidence where controls call for it, while retaining your organization’s approval process. Review point. Does the review distinguish verified evidence from the organization’s own compliance conclusion? 02 USE CASE ### Review a release candidate with its stated deployment choice Situation. A candidate must be assessed before it moves forward, and the deployment environment is a material part of that assessment. Make the full composition and supported target visible in the review rather than treating the target as a downstream detail. - 01 Confirm the artifacts and evidence associated with the candidate. - 02 Review the `.vio` composition and the stated supported target. - 03 Document the outcome against the applicable controls before a Helix deployment path is considered. Review point. Is the approval based on an explicit system and target rather than a generic description of the capability? 03 USE CASE ### Explain a system handoff to an internal reviewer Situation. A new reviewer or control owner needs to understand what has changed without relying solely on a narrative history. Use the portable definition as the starting record and make amendments explicit. - 01 Review the definition’s artifacts, relationships, and evidence references. - 02 Clarify which assertions have been verified by Trust and which require policy judgment. - 03 Record any new owner, target, or composition change before the next decision. Review point. Can a new reviewer identify both the declared system and the boundary of the evidence they are assessing? THE DEPLOYMENT PATH ## From system parts to a supported target . A `.vio` definition keeps the complete AI system composition legible through the next workflow decision. - 01 Identify the artifacts and stated evidence relevant to the review. - 02 Compose the complete declared AI system in `.vio`. - 03 Verify artifacts with Trust where your controls require it. - 04 Evaluate any Helix transformation or deployment against the supported target and your own requirements. THE VIORANT SYSTEM ## Use the surfaces that fit your workflow . [Hub Optional local-first workspace for working with artifacts and definitions. →](/hub)[.vio Portable composition of the complete AI system. →](/vio)[Trust Verification of stated artifact identity and evidence. →](/trust)[Helix Transformation and deployment for supported targets. →](/helix) QUESTIONS, ANSWERED ## For Regulated AI teams . 01 Does Viorant make a system compliant? + No. Viorant provides a reviewable system definition and artifact evidence verification. Compliance determinations require the applicable controls and authorized reviewers. 02 Can evidence remain associated with the artifact? + Trust is designed to verify stated artifact identity, integrity, provenance, signatures, and evidence as part of the workflow. 03 Are deployment targets assumed? + No. Target support is explicit and must be confirmed for the intended deployment workflow. AI DEPLOYMENT INFRASTRUCTURE ## Start with a system record your team can review . Explore the local-first Hub workspace or talk with Viorant about the deployment path you are considering. [Download the Hub →](/download)[Talk to Viorant →](/contact)