UpSkillZone

Standards track — UpSkillZone

RFC-UZ-002 — Talent and Hiring Marketplace Protocol

Wire formats, lifecycle, and policy obligations of the UpSkillZone talent discovery and hiring marketplace. The canonical document lives in source at reference/PROTOCOL_RFC_002.md; this page is the stable public summary employer counsel and regulators cite. The key words MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are interpreted per BCP 14 (RFC 2119, RFC 8174).

Document metadata

Document
RFC-UZ-002
Version
v2.4.0
Status
Active
Effective
2026-04-15
Category
Standards Track
Supersedes
RFC-UZ-002 v2.3.x
Companion
RFC-UZ-001 (Credential and Attestation Layer)

Tip — this page prints cleanly. Use your browser’s print dialog to save a dated PDF for counsel review.

Abstract

This document specifies the wire formats, lifecycle, and policy obligations of the UpSkillZone talent discovery and hiring marketplace. It defines the talent profile shape and consent model, the employer registration ladder, the constrained SkillQuery interface that all talent search MUST flow through, the cryptographic envelope for HireAttestation and OutcomeAttestation records, the take-rate billing model, the per-tier outreach quotas, and the bias-audit obligations enforced against every public skills search.

1. Terminology

Defines talent profile, employer, skill query, hire attestation, outcome attestation, outreach, take-rate, calibrated mentor, and consent scope. Where a term also appears in HIRING_TERMS.md, the form here is operational; the reference document is the legal form.

2. Talent Profile Shape

A talent profile is a tree of typed records rooted on a stable talent_profile_id (ULID). The root carries a ConsentRecord, zero or more AvailabilityBlock and GeographyBlock records, and at most one SalaryBand. The shape is normatively defined in upskillzone.domains.skills_graph.

3. Employer Registration and Verification

A four-rung tier ladder — unverified → email_verified → domain_verified → kyc_verified — gates access to projection levels and outreach quotas. Each rung specifies the evidence the platform requires before promotion.

4. Talent Profile DTOs

Three projections — public, employer_index, and kyc_only — control which fields a recruiter sees at each tier. evidence_count is rounded for low tiers; SalaryBand and evidence_glimpse are tier-gated to kyc_verified.

5. Skill Query Protocol

All employer talent search MUST flow through the constrained SkillQuery interface. Free-text search over profile bodies is out of scope and MUST NOT be implemented. The schema is closed; extra fields fail with HTTP 422 and the skillquery-extra-field-forbidden problem type.

Ranking inputs are documented (§5.2): trust_score derives only from calibrated mentors' assessments.

6. Hire Attestation

A signed record asserting that a hire occurred. Conformant HireAttestation records are the only artefact that triggers take-rate billing. Signature uses the employer's Ed25519 recruiter-seat key registered in §3.

7. Outreach

First-contact messages from a recruiter seat to a previously-unengaged talent profile are quota-bound per tier. Quota exhaustion returns HTTP 429 with the outreach-quota-exceeded problem type.

8. 90-Day Outcome Attestation

A post-hire signed record capturing whether the hire is still_employed, promoted_or_extended, or terminated, plus a free-form OutcomeAnswer. Submission outside the §8.1 window returns HTTP 409.

9. Take-Rate

12% platform fee on channel_attribution=talent_search hires. Mentor-introduced and self-applied hires are out of scope. Clawbacks for terminated outcomes are surfaced in the invoice payload, not as errors.

10. Bias Audit Obligations

§10.1 — Every public-scope SkillQuery is logged with HMAC-hashed identifiers; retention is 2 years.

§10.2 — Quarterly four-fifths-rule monitoring of inferred subgroup selection rates; flagged subgroups appear on /admin/bias-audit and in the public report.

§10.3 — Top-25 drift monitoring against a 50-query reference suite; >30% Jaccard distance over four consecutive weeks pages on-call.

§10.4 — Geographic representation diff against the eligible talent base; >0.25 KL-divergence on >5% of unfiltered queries in a quarter is disclosed.

§10.5 — Public quarterly bias audit report published no later than 45 days after quarter close, machine-readable JSON served alongside.

11. Status Codes and Error Wire Format

All errors use application/problem+json (RFC 9457). Field-level errors carry an errors[] with pointer and code members. The problem type catalogue is normative.

12. Security Considerations

Employer key custody — recruiter-seat Ed25519 secret keys are never custodied by the platform. Lost keys trigger a rotation event and revoke previously-signed HireAttestation records.

Talent profile re-identification risk — combinations of region, proficiency_band, last_evidenced_at, and evidence_count can re-identify owners. Implementations SHOULD apply k-anonymity (k≥5) checks on result sets when required_skills length exceeds 8.

13. References

BCP 14 (RFC 2119, RFC 8174); RFC 9457; reference/HIRING_TERMS.md; reference/MENTOR_AGREEMENT.md; RFC-UZ-001; reference/DATA_RETENTION.md.