FOR DEVOPS & SRE TEAMS # Bring AI system definitions into deployment workflows . Viorant gives DevOps and SRE teams a neutral AI system definition to bring into established deployment conversations: artifacts retain identity, `.vio` records the composition, and Helix can transform the definition for explicitly supported targets. [Explore Viorant Hub →](/hub)[Talk to Viorant →](/contact) Editorial visual for DevOps & SRE 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 ### Treat system definition as a first-class input Use `.vio` as an AI Infrastructure-as-Code mechanism that records the declared composition and target choices of a complete AI system. 02 ### Keep target support explicit Helix reads the definition and prepares or deploys it only to supported targets, rather than inferring universal compatibility. 03 ### Bring evidence to the workflow Trust can verify stated artifact identity, integrity, provenance, signatures, and evidence where those checks are part of release practice. USE CASES ## Put the system record to work . Three practical ways devops & sre teams can use a declared AI system boundary to move a real decision forward. 01 USE CASE ### Receive a declared system definition into release practice Situation. Operations receives an AI release with deployment instructions but lacks a clear view of the artifacts and relationships those instructions refer to. Treat the `.vio` composition as a first-class release input alongside existing operational controls. - 01 Inspect the artifacts, declared relationships, and target choice in the definition. - 02 Use Trust for relevant artifact evidence checks where the release workflow requires it. - 03 Use Helix only for a target that is explicitly supported for the intended transformation or deployment. Review point. Is the operational team acting on a declared system, not an inferred bundle of configuration? 02 USE CASE ### Assess an environment move before execution Situation. A team is considering a new environment or supported target and must distinguish the system definition from the environment-specific decision. Review the portable composition first, then assess the specific supported deployment path. - 01 Confirm the `.vio` definition represents the intended system boundary. - 02 Identify the target-specific assumptions that need an operational decision. - 03 Document the supported transformation or deployment choice before executing it through Helix. Review point. Which aspects are portable system intent, and which are specific to the chosen target? 03 USE CASE ### Reconstruct release context after an incident Situation. An incident review needs a disciplined way to inspect the declared system without treating all runtime behavior as universally reproducible. Use the definition and its stated evidence to understand the release context while keeping environment conclusions explicit. - 01 Locate the definition associated with the relevant release. - 02 Review its artifact composition and target choice alongside the operational record. - 03 Use findings to update the declared definition or release controls as appropriate. Review point. What is known from the system record, and what still depends on the specific environment? 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 Receive meaningful AI system parts as signed, versioned artifacts. - 02 Review the `.vio` composition and its declared deployment choices. - 03 Verify relevant artifact evidence with Trust. - 04 Transform or deploy through Helix to an explicitly 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 DevOps & SRE teams . 01 Does Helix support every environment? + No. Helix works with explicitly supported targets. A target must be confirmed for the intended workflow. 02 Is this a replacement for existing DevOps tooling? + No. Viorant provides the portable AI system definition and related verification or transformation surfaces; teams retain their existing operational tooling and decisions. 03 What makes `.vio` infrastructure-as-code? + It is a declarative, portable composition of the complete AI system, including the artifacts and deployment choices that belong together. 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)