UNX Code ops
- intake, selection, start events
- QA acceptance authority
- continuity and replacement
- employer relationship ownership
loading…
From need intake to collaboration record: operator-owned phases for intake, invite, delivery, change, and acceptance — including failure states and role ownership.
Work moves through desks with owners. Skipping a desk is not a feature.
UNX Code is not “post a job → receive bids.” Need is framed, people are invited privately, delivery runs on evidence, change is explicit, and acceptance is laddered — not implied by a merge.
Intake & framing — shared problem, versioned scope, early risk notes
Invite & activation — private invite, accept path, operator start
Delivery — planning template, tasks, immutable evidence versions
Change & continuity — formal change, replacement, escalation without automatic penalties
Acceptance — QA events, criteria, record for future invites — no public ranking
Nobody is activated until the problem is shared and early risk is named.
Input: initial brief — Output: shared problem framing — Owner: UNX Code ops
Input: scope draft — Output: approved version — Decision: confirm or redefine
Dependencies and sensitive points — no fabricated probability scores
Selection is from the verified network. Developers never browse a public board.
From verified capacity and fit — not public search or bidding
Permitted details, deadline, accept / decline / structured negotiate
Capability-based — unknown means deny; revoked membership tears down access
Operator start event only — developers and leads cannot self-start
Milestone, sprint, task, or hybrid template — unknown templates fail closed
Assigned work only — tasks and deliverables with owners and windows
Immutable versions — edits create new versions; no overwrite of history
Scope change with reason, impact, and approval — no silent field edits
Raise issues with record — no automatic reputation penalty or takeover
Replacement and handoff when disruption hits — logged, not improvised
Work claims readiness — not the same as accepted delivery
Findings with accept or reject events — developer sees outcomes, not internal notes
When upload and file-check integration is connected: files pass checks and criteria before preview or download
History informs future invites — never a public ranking or peer scoreboard
Fail closed beats silent success.
Superseded invite versions cannot be accepted
Stale or expired capacity blocks accept until reconfirm
Unknown capability = deny; revoked membership ends subscriptions
When file-check integration is connected: pending, failed, or unsafe checks block delivery paths
After accept: pending activation only — no broken workspace links
Version conflicts on update surface — no optimistic contractual success
UNX Code sits as the accountable, operator-managed counterparty between organizations and elite engineering talent.
The central nervous system of UNX Code. Freezes runtime contract schemas with strict Zod validation, locks escrow funds into immutable milestone smart contracts, and runs the 16-stage automated verification gate before any payout.
Organizations start a conversation. Developers enter membership — never a public board.