Velvet Ecosystem
Velvet is modular, offline-first machine intelligence infrastructure for embedded systems, beginning with vehicles and expanding across surfaces.
Velvet is infrastructure for local machine agency under human sovereignty.
Interfaces route intent. Gates authorize action. Executors touch hardware. Receipts prove what happened.
Start with the public docs, then move into the source repos. The docs explain Velvet’s doctrine, architecture, surfaces, repo boundaries, and safe authority model.
Vehicle and mobility surfaces. The first body of Velvet begins with retrofit vehicle intelligence, CAN-aware adapters, local control paths, and receipt-backed authority.
Fabrication surfaces such as 3D printers, CNC, and maker systems. The same doctrine applies: local control, bounded adapters, and receipts.
Future home, portable, and industrial surfaces. Each surface gets its own adapter pattern without becoming Velvet’s authority source.
DriveFi is Velvet’s experimental economic layer for receipt-backed machine work, motion, presence, and local value generation.
VELV is not required to use, study, build, or contribute to Velvet’s core architecture.
Token ownership does not grant runtime authority, governance control, hardware access, executor privileges, or system permissions.
The token layer must never bypass Velvet’s authority gates.
Domain: velvai.sol
Ticker: VELV
Remove the space in the displayed contract if copying. It is visually separated here to avoid cramped mobile overflow.
The early Velvet redpaper framed the economic vision: mint by movement, prove by presence, and resist OEM lock-in.
That vision remains experimental and must stay subordinate to Velvet’s safety, authority, and receipt doctrine.