Is UNX Code a freelance marketplace or public job board?
No. UNX Code is a private, managed network of vetted developers. Projects are registered manually and invites are private — there is no public bidding board.
Who is the developer’s contractual counterparty?
Always UNX Code. Developers do not work directly with the end client, and client identity is not shown in the developer layer.
What does “one counterparty” mean in practice?
Organizations contract with UNX Code for selection, activation, delivery, QA, and continuity. Developers also contract with UNX Code. The end employer is not a chat participant on developer surfaces.
Who does an organization contract with?
UNX Code. Team selection, execution, evidence, and quality control stay inside UNX Code’s managed model — not direct hire from an open market.
What are operator desks?
Named operational ownership for intake, selection, activation, delivery, acceptance, change, and continuity. Desks keep coordination visible and logged — not buried in side chats.
How is this different from an agency or marketplace?
Marketplaces optimize discovery and bids. Agencies may staff teams but still leave acceptance opaque. UNX Code is invite-only capacity with operator-owned activation, evidence gates, and continuity — see the organizations page compare section.
Do developers see a public project list?
No. Only private invites aligned with your skills and capacity are sent.
What is activation / operator start?
Accepting an invite is not self-starting a project. An operator start event provisions capability-scoped access. Unknown capability means deny; revoked membership tears access down safely (fail closed).
What is the acceptance ladder?
Ready-for-evidence is not final acceptance. Work moves through evidence, QA review, and explicit accept/reject events. Delivery after gates is logged — not implied by a merge or a progress percentage.
What does continuity mean if someone leaves?
Replacement and handoff are logged operational events with evidence history and scoped access — projects are not abandoned to informal favours.
How long does vetting take?
It depends on document completeness and review capacity. We do not publish fixed SLAs; status is tracked in the portal. When you may reapply (eligibility timing) is server-driven when applicable.
Is membership auto-scored?
No. Final membership is a human decision. Claimed skill levels are declared, not verified percentages. There is no peer ranking from dossier fields.
Does membership guarantee income or projects?
No. Acceptance means you can be invited when a real project matches — not a constant project feed. Settlement is manual at this stage.
What finance data do developers see?
Only their own amounts and statuses. Client amounts, margin, and peer financials never appear in developer surfaces.
How do team projects work?
UNX Code defines team structure, lead role, and access boundaries. Leads may propose membership adjustments; they do not run pool search. Execution continues in-system with tasks, evidence, and QA.
How is quality proven?
Through evidence, review, QA, and acceptance criteria — not auto-scores or invented percentages. See the quality page for the full loop.
How are scope changes handled?
Formal change requests with reason and impact. Silent scope edits via task fields are not a product path. New evidence versions preserve history.
Is end-client identity visible to developers?
Not on public surfaces or in the developer workspace. Only policy-permitted fields appear inside an assigned project. Employer identity stays out of developer payloads, DOM, logs, and telemetry.
Does AI make membership or QA decisions?
No. AI does not replace final identity, membership, or QA acceptance. Invites never use “AI chose you” messaging.
How do I contact UNX Code?
Use the contact page and pick a request type. Live backend delivery is integration-gated; status is shown honestly until connected. We never fake a success receipt.
How does sign-in work?
Passwordless auth at /auth. No tokens in browser storage. We do not disclose whether an account exists when you start.
Why might the work page be empty?
Only published, privacy- and claims-approved case material appears. Empty is honest — we do not invent case studies or client logos to fill the grid.