Platform · Three parts, one system
Matrix by HiCode organizes users, company members, AI resources and authorized devices to complete software work with verifiable results. The product is three parts with clear owners, so nothing is stored twice and nothing succeeds by accident.
Accounts and organizations, Tasks, Brains and Hands, resource permissions, DAG orchestration, run views and internal accounting. Operated by HiCode at matrix.hicode.com.
Projects, code and visual editing, Compile, Preview and AutoTest, plus the flow editing, import and debugging that development needs. Powered by the VL language.
One shared engine owns workflow semantics, state, tools, protocols, services and lifecycle. Matrix and Build both run on it; there is no second scheduler or run ledger.
Work, resources, orchestration, execution, results and accounting are separate layers with a single source of truth each, so any one can improve without breaking the loop.
A Task keeps its goal, context, scope, responsibility and completion condition. Saving a Task and starting execution are separate acts. A pure question never forces a workspace.
Every resource has an owner, a channel, an account-level quota pool and a device. A brand or model name is never its identity. Using a model and reading a device's files are two permissions.
Single agent, AI Leader team or human-managed; no flow, a static flow or a dynamic plan. The run graph shows participants, process, feedback and real execution together.
Tool calls travel as lease-bound envelopes. The Hand verifies, persists a replay fence, executes within its workspace root and returns a signed receipt.
Results link to the executor, Run, node, attempt, inputs, outputs, artifacts, errors and usage. Real runs, fixtures, mocks and skipped tests are told apart.
A round is one real model turn with its tool loop. Your own and free resources return automatically when it ends; paid Standby is borrowed and returned by hand, and billed while held.
Product decisions from the 2026-09-30 boundary review and the current Matrix and VLC requirements. Requirements being unified does not mean every path is deployed or accepted on every platform.
VL Agent is retired as a standalone product, IDE and installer. Agent Apps you built keep running; flow editing happens in Build, orchestration in Matrix.
Matrix schedules declared capability. Provider logins and keys stay in the secure storage of the device that owns them.
Accounts, cookies, tokens and sessions are not resold, and subscription logins are not turned into a public model endpoint. Matrix is not a VPN, proxy or remote desktop.
An unavailable device, an unmet policy or missing evidence is reported as such. Unknown execution stays pending rather than becoming a success.