Accept
Eligible for private invites aligned with capacity and skills.
loading…
Human review across identity, history, skills, capacity, and optional interview — evidence over claim, no auto membership score.
A managed network cannot run on profile slogans.
Invites depend on people who can carry evidence, privacy boundaries, and continuity. That requires review of documents, history, and capacity — not an instant acceptance rate badge.
UNX Code does not auto-approve membership, does not treat OCR as identity truth, and does not publish peer rankings from dossier fields.
Identity — Iranian documents, manual review, no public KYC storage
History — professional experience that can be discussed with evidence
Skills — declared levels are claimed, not verified skill percentages
Capacity — realistic windows; stale capacity blocks later accept paths
Interview — technical or professional conversation when the case needs it
Consents — versioned, never pre-checked as a dark pattern
Closed network, UNX Code as counterparty, invite-only work — or stop here
Official /auth path — no token storage in the browser
Server-held draft with conflict checks — signed upload sessions; file checks before submit when upload integration is connected
Ops review across dimensions — internal notes never enter developer payloads
Accept, reject, conditional acceptance, or hold — with explicit conditions when conditional
Eligible for private invites aligned with capacity and skills.
Membership with explicit conditions shown — not hidden fine print.
Hold or reject with server-driven eligibility timing (when you may reapply) when applicable.
Approval does not dump you onto a project board. Work arrives as private invites. Declines and negotiations are structured — not free-form employer DMs.
Finance remains manual at this stage; you see your own amounts only. Employer identity never appears in developer payloads.
How we protect developers from open bidding races to the bottom while guaranteeing elite execution for clients.
Pure engineering evaluation with zero demographic or resume bias.
pub struct MilestoneEscrow { pub id: EscrowId, pub amount_cents: u64, pub state: EscrowState, } impl MilestoneEscrow { /// Invariant: Funds cannot disburse without peer consensus pub fn lock_milestone(&mut self, sig: &[u8; 64]) -> Result<(), ContractError> { assert_eq!(self.state, EscrowState::Funded); verify_unx_signature(sig, &self.id)?; self.state = EscrowState::Locked; emit_event(EscrowEvent::MilestoneCommitted); Ok(()) } }
Read the ladder, then start passwordless auth. No auto score. No marketplace.