FOR SECURITY & GOVERNANCE TEAMS # Review AI system evidence in its full context . Viorant gives security and governance teams a clearer object to review: a portable `.vio` definition that composes meaningful artifacts, alongside stated evidence that Trust can verify when the process calls for it. [Explore Viorant Hub →](/hub)[Talk to Viorant →](/contact) Editorial visual for Security & governance 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 ### Review the whole composition See the declared system boundary instead of assessing isolated components without their intended relationships or deployment choices. 02 ### Check stated artifact evidence Trust is designed to verify artifact identity, integrity, provenance, signatures, and stated evidence in a review workflow. 03 ### Keep the control point neutral A neutral definition supports governance conversations without requiring one vendor, runtime, or hosting model to become the architecture. USE CASES ## Put the system record to work . Three practical ways security & governance teams can use a declared AI system boundary to move a real decision forward. 01 USE CASE ### Prepare evidence for an AI release review Situation. A review board needs to understand the system being released and the evidence associated with its meaningful parts. Use the declared composition to connect evidence review to the full system boundary. - 01 Identify the artifacts and stated evidence relevant to the decision. - 02 Review the `.vio` definition to establish which artifacts belong to the declared system. - 03 Use Trust to verify stated identity, integrity, provenance, signatures, and evidence where required. Review point. Does the evidence answer a question about the declared system, rather than an isolated component? 02 USE CASE ### Investigate a change without losing system scope Situation. A reviewer is asked about one configuration or artifact but needs to understand where it sits in the intended AI system. Start from the portable composition, then narrow the investigation while keeping the boundary visible. - 01 Locate the artifact in the `.vio` composition and inspect its declared relationships. - 02 Check the relevant stated evidence with Trust as part of the investigation. - 03 Record the review finding against the declared target and system context. Review point. What system-level assumption would be missed if the artifact were reviewed by itself? 03 USE CASE ### Coordinate a governance sign-off across functions Situation. Security, architecture, product, and operations need different assurances before the system progresses. Give each function the same neutral definition while keeping their approvals and policies distinct. - 01 Agree the composition is the specific system under review. - 02 Assign evidence and target questions to the relevant reviewers. - 03 Use the outcome to decide whether the definition is ready for a supported transformation or deployment path. Review point. Are sign-offs tied to an explicit system and target, rather than a general claim of readiness? 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 evidence relevant to the decision. - 02 Review the `.vio` definition as the declared complete system composition. - 03 Use Trust to verify artifact identity and stated evidence where required. - 04 Confirm any transformation or deployment is directed to a supported target. 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 Security & governance teams . 01 Does Trust certify compliance? + No. Trust verifies stated artifact evidence. Compliance conclusions remain a matter for the applicable policy, controls, and reviewers. 02 What is being governed? + The reviewable object is the declared AI system composition in `.vio`, including its meaningful artifacts and stated deployment choices. 03 Can the definition support different deployment decisions? + Yes, as long as the target is explicitly supported and the resulting configuration is reviewed for that environment. 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)