FOR DEVELOPER TOOL BUILDERS # Build around a neutral AI system format . Viorant gives developer tool builders a neutral AI system format for developer tooling integrations: meaningful components retain artifact identity, `.vio` composes them into a portable definition, and verification and supported deployment surfaces can work from that record. [Explore Viorant Hub →](/hub)[Talk to Viorant →](/contact) Editorial visual for Developer tool builders 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 ### Work from a declared system boundary Build tools around a `.vio` composition that keeps the complete AI system distinct from any one authoring or runtime surface. 02 ### Preserve artifact identity Meaningful AI components stay signed, versioned artifacts rather than being reduced to anonymous configuration inside a larger definition. 03 ### Keep integrations honest Describe the supported target or verification surface explicitly; do not infer universal compatibility from the neutral system definition. USE CASES ## Put the system record to work . Three practical ways developer tool builders can use a declared AI system boundary to move a real decision forward. 01 USE CASE ### Build a tool around a declared AI system boundary Situation. A developer tool needs to reason about a complete AI system without treating one authoring surface or runtime as the canonical source. Use `.vio` as the neutral composition your tool reads, presents, or helps maintain. - 01 Map meaningful inputs and outputs to identifiable artifacts rather than anonymous configuration. - 02 Read or produce the `.vio` composition that connects those artifacts into a declared system. - 03 Expose any supported-target or evidence integration as an explicit capability of the tool. Review point. Does the tool preserve the distinction between the portable definition and any specific runtime? 02 USE CASE ### Surface artifact identity and evidence in a developer workflow Situation. A tool can show components, but users also need to understand the identity and stated evidence associated with the components they are selecting. Keep artifact identity first-class and make verification a clear, bounded workflow. - 01 Represent meaningful components as artifacts with their own identity. - 02 Allow the composition to point to those artifacts without flattening their context. - 03 Integrate with Trust only to show or request verification of stated identity and evidence. Review point. Can users distinguish artifact facts that are verified from broader claims the tool does not make? 03 USE CASE ### Declare a target integration honestly Situation. Your product wants to help users move a defined system into another environment, but compatibility and transformations must be scoped precisely. Treat the integration as a supported target choice, not a universal promise about `.vio`. - 01 Define which parts of the `.vio` system your integration can read or transform. - 02 State the target and constraints clearly in your product workflow. - 03 Use Helix where the target is explicitly supported and the user has chosen that deployment path. Review point. What does the integration support exactly, and what remains outside its declared scope? 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 Recognize meaningful components as artifacts with their own identity. - 02 Read or compose the complete declared system in `.vio`. - 03 Use Trust when stated artifact evidence needs verification. - 04 Use Helix for transformation or deployment only 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 Developer tool builders . 01 Is `.vio` an artifact format for every AI object? + No. Artifacts retain their own identity. `.vio` is the portable composition that describes the complete AI system. 02 Does a neutral format guarantee integration? + No. It provides a common system definition; integration and target support must be made explicit and verified for each workflow. 03 Where can tool builders learn more? + Start with the `.vio` and documentation pages, then verify the supported interfaces and targets relevant to the proposed integration. 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)