UTXOSUITE — home
LABS / BUILD ORGANIZATION

Diziplina bereiziak. Delivery rules partekatuak.

Labs-ek UTXO Suite eta sibling systems inguruko build organization azaltzen du, team size, external review edo production readiness ziurtatu gabe.

BUILD UNITS

Infrastructure eta applied software bereizita.

UTXO Labs Team eta Idovio Team elkarlanean aritu daitezke scope desberdinak mantenduz; ez du esan nahi capability guztiak shipped direnik.

UNIT 01

UTXO Labs Team

UTXO Labs Team protocol, security, transaction analysis, routing eta systems research-en fokuratzen da; UTXO Suite-n SafeSign eta Security Core bidez agertzen da.

TRANSACTION SECURITY
SYSTEMS / PROTOCOL RESEARCH
ROUTING / ANALYSIS
UNIT 02

Idovio Team

Idovio Team application/product software-an fokuratzen da. Sibling apps eta experiments core promise-tik bereizita daude.

APPLICATION SOFTWARE
PRODUCT ENGINEERING
SIBLING SYSTEMS
DELIVERY DISCIPLINE

Status arkitekturaren parte da.

Research, scaffold, prototype, integrated surface eta production release fase desberdinak dira.

RULE 01

LOCAL-FIRST

LOCAL-FIRST ahal denean — sensitive analysis eta preferences device-an.

RULE 02

NON-CUSTODIAL

NON-CUSTODIAL — request azaltzeko ez da private-key custody behar.

RULE 03

EXPLICIT AUTHORIZATION

EXPLICIT AUTHORIZATION — user/wallet signing boundary da.

RULE 04

EVIDENCE-LED STATUS

EVIDENCE-LED STATUS — strong labels evidence dagoenean soilik.

Research irekiProjects ireki
OPERATING MODEL

Lana engineering gate esplizituen bidez mugitu.

Research-tik production-era bidea explicitua: artifacts, security boundaries eta status batera aurreratu.

01 / DISCOVERY

DISCOVERY

User problem, threat model eta trust boundary-tik kanpo zer geratu definitu.

02 / SPECIFICATION

SPECIFICATION

Implementation aurretik invariants, supported inputs, failure behavior eta negative tests idatzi.

03 / VALIDATION

VALIDATION

Status igo aurretik positive, negative, adversarial eta regression fixtures exekutatu.

MATURITY GATE-AK

Status release control bihurtzen da, ez marketing adjective.

Research-tik production-era bidea explicitua: artifacts, security boundaries eta status batera aurreratu.

STAGE
ARTIFACT / INPUT
EVIDENCE / MEANING
OUTPUT
RESEARCH
problem + hypothesis
Direction badago; implementation ez da implied.
RESEARCH
SCAFFOLD
source + checks
Code dago baina real integration incomplete izan daiteke.
SCAFFOLD
RELEASE
validation + ops
Release artifact, rollback path eta operating evidence daude.
RELEASE
RELEASE RECORD
{
  "surface":"guard",
  "stage":"integrated",
  "required":["real provider flow","negative fixtures","payload-integrity test"],
  "publicLabel":"BETA"
}
SECURITY GATE
{
  "privateKeyCustody":false,
  "autoSign":false,
  "payloadMutation":"forbidden",
  "unsupportedInput":"visible failure"
}
LABS RULE

UI polished backend complete baino lehen egon daiteke, baina public status-ek difference zehazki azaldu behar du.