FOR ENTERPRISE ARCHITECTS # Create a neutral deployment boundary for enterprise AI . Viorant helps enterprise architects describe complete AI systems as portable definitions, so architecture decisions, artifact evidence, and supported target choices can be reviewed as one coherent system record. [Explore Viorant Hub →](/hub)[Talk to Viorant →](/contact) Editorial visual for Enterprise architects 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 ### Separate definition from runtime Use `.vio` to describe the complete system without binding its meaning to a single provider, framework, or managed surface. 02 ### Review system structure Bring artifacts, composition, and declared deployment choices into one reviewable boundary for architecture and governance conversations. 03 ### Keep services optional The standard remains neutral while Viorant services can support authoring, verification, transformation, or deployment workflows where appropriate. USE CASES ## Put the system record to work . Three practical ways enterprise architects can use a declared AI system boundary to move a real decision forward. 01 USE CASE ### Frame an architecture decision before provider selection Situation. The organization agrees on the AI outcome but has not selected a provider, runtime, or hosting model. Separate the system definition from the eventual execution surface so the architecture can be reviewed on its own terms. - 01 Name the artifacts and relationships that are material to the intended architecture. - 02 Record the complete proposed composition in `.vio` without treating a provider choice as implicit. - 03 Compare only explicitly supported deployment paths when the decision reaches that stage. Review point. Which parts of the architecture remain true regardless of the chosen target? 02 USE CASE ### Run a design review across architecture and governance Situation. Architecture, security, and product teams need to review the same system but their documents describe it at different levels. Use a shared portable composition as the review object and attach each function’s questions to it. - 01 Establish the declared system boundary and its significant artifacts. - 02 Use the `.vio` composition to discuss dependencies, evidence, and operational choices together. - 03 Capture any approved supported-target decision as an explicit outcome of the review. Review point. Does the review cover the complete declared system rather than a diagram or component in isolation? 03 USE CASE ### Prepare an architecture handoff for a delivery team Situation. A design moves from central architecture into delivery, where intent is commonly recreated from diagrams and meetings. Hand over the system definition with the artifacts that make the architecture meaningful. - 01 Keep architecture-relevant system parts as signed, versioned artifacts where appropriate. - 02 Provide the `.vio` definition with its declared relationships and deployment choices. - 03 Ask the delivery team to confirm or amend the definition as implementation choices become concrete. Review point. Can the delivery team state what it received and where it made a deliberate change? 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 that make the AI system meaningful. - 02 Compose them into a `.vio` definition that captures the intended system boundary. - 03 Use Trust to verify stated evidence before a governance or release decision. - 04 Use Helix when preparing the definition for a supported deployment 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 Enterprise architects . 01 Is `.vio` tied to one cloud or model provider? + No. `.vio` is a neutral system definition. Supported deployment targets are explicit rather than assumed. 02 What does Trust verify? + Trust verifies artifact identity, integrity, provenance, signatures, and stated evidence. It does not make a general compliance or safety promise. 03 Can architecture teams use Viorant without a managed service? + Yes. The standard is neutral and Viorant services are optional. 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)