UI, Seal and Chart: three libraries, one family
Why our three open-source libraries are separate packages, and how they fit together when you use them side by side.
AI agents now use websites on behalf of people. They read pixels and guess. A button labelled "Continue" might save a draft — or charge a card. Three of our libraries come from one question: how do you build an interface that people and agents can use safely?
Three jobs, three packages
VhyxUI draws the interface. Accessible React components with motion and design tokens. Nothing unusual so far — except that every interactive component also carries a contract: its intent, how risky it is, and whether a person must confirm.
VhyxSeal publishes the contracts. It collects them into one manifest at /__agent__/manifest.json, signs it, and binds it to your domain. An agent reads the manifest, acts freely on low-risk actions, and stops to ask a person before anything that needs confirmation. VhyxSeal works without VhyxUI too — with React, Next.js, Vue or plain JavaScript.
VhyxChart explains the flow. Diagrams written as text that animate. VhyxSeal uses it to draw a manifest as a flow, so you can see exactly where an agent has to stop — and you can use it for any architecture, sequence or algorithm in your own docs.
Why not one big package?
Because each one is useful on its own. Plenty of teams want animated diagrams and have never heard of agent contracts. Keeping the packages separate keeps each one small, focused and honest about what it does. When you use them together, they share a design language — rose for UI, emerald for Seal, sky for Chart — and they simply fit.
Start with whichever problem you have today: vhyxui.com, vhyxseal.com or vhyxchart.com.