Labs explains the build organization around UTXO Suite and sibling systems. It does not certify team size, external review or production readiness. Those statuses belong to the specific project and its evidence.
UTXO Labs Team and Idovio Team can collaborate across the ecosystem while retaining different scopes. The boundary is descriptive, not a claim that every named capability is already shipped.
UTXO Labs Team focuses on protocol, security, transaction analysis, routing and systems research. In UTXO Suite, that work is represented by SafeSign, Security Core and the security-oriented integration model.
Idovio Team focuses on application and product-layer software. Sibling applications and experimental productivity systems remain separate from the core UTXO Suite transaction-security promise.
A project can move through research, source scaffold, prototype, integrated surface and production release. The site should preserve those distinctions instead of marketing them away.
LOCAL-FIRST WHERE PRACTICAL — sensitive analysis and preferences stay on-device when the integration permits it.
NON-CUSTODIAL — transaction-security surfaces do not need private-key custody to explain a request.
EXPLICIT AUTHORIZATION — analysis may inform; the user or calling wallet remains the signing boundary.
EVIDENCE-LED STATUS — shipped, audited, peer-reviewed and production-ready are used only when support exists.
Make the path from research to production explicit: required artifacts, security boundaries and status labels must advance together.
Define user problem, threat model and what remains outside the trust boundary.
Write invariants, supported inputs, failure behavior and negative tests before implementation.
Run positive, negative, adversarial and regression fixtures before status is upgraded.
Make the path from research to production explicit: required artifacts, security boundaries and status labels must advance together.
{
"surface":"guard",
"stage":"integrated",
"required":["real provider flow","negative fixtures","payload-integrity test"],
"publicLabel":"BETA"
}{
"privateKeyCustody":false,
"autoSign":false,
"payloadMutation":"forbidden",
"unsupportedInput":"visible failure"
}A polished interface may exist before a backend is complete, but public status must describe that difference exactly.