Skip to main content

2IX

2IX.org

How It Works

How 2IX matching works

A matching workflow that shows the evidence before anyone commits.

2IX starts with structured profiles and scoped opportunities. It keeps the early decisions visible: why a role fits, what is missing, what stays private, and what a contributor needs before they begin.

Browse opportunities
See score factors
Start matching

Step 1

Collect useful signal

Profiles and postings capture skills, causes, schedule, location mode, support, privacy, and screening boundaries.

Step 2

Show the fit

Match notes explain skill overlap, cause alignment, availability, location, trust status, and gaps.

Step 3

Start with context

Technical and operations-heavy work gets a public-safe brief so contributors can begin without reconstructing the project.

  1. Capture profile signal: who is offering help, what they can do, when they are available, and how visible they want to be.
  2. Capture opportunity signal: who needs help, what outcome is needed, what skills are required, and what trust or screening rules apply.
  3. Explain fit: show skills, cause, schedule, location, verification, and project-readiness evidence before a match is pursued.
  4. Preserve continuity: publish a clear project brief when an opportunity requires source files, decisions, docs, or setup context.

Data model

People, organizations, opportunities

The MVP stores these as registry records; the later platform can split them into relational entities and application flows.

Matching

Rules first, semantic scoring next

Start with transparent fit notes, then add normalized skill tags, vector scoring, and feedback loops when records have enough signal.

Continuity

Technical work gets a brief

Open-source and operations-heavy projects need current state, decisions, links, and next actions so contributors do not restart from scratch.

Public model

How 2IX turns intent into matchable work

2IX is intentionally narrower than a generic job board: it helps people understand whether a volunteer opportunity is real, scoped, safe, and ready for a contributor.

1. A profile becomes signal

Volunteers publish skills, causes, availability, location preference, work samples, and a visibility setting. Private contact details are stored for follow-up, not displayed as public browsing data.

  • Public: name, headline, skills, causes, broad availability.
  • Limited: searchable fit signal with fewer personal details.
  • Private: shared only through an application or steward workflow.

2. An organization turns a need into a scoped outcome

Organizations are asked for a concrete deliverable, steward contact, required skills, acceptance criteria, time estimate, screening notes, and project context before a post becomes useful.

  • Good posts name the outcome and the first safe action.
  • Weak posts are vague, unowned, or too large to start.
  • Sensitive work must describe screening without exposing private records.

3. Fit is explained before commitment

The MVP score is deterministic and visible. It compares skills, availability, cause alignment, location mode, verification/readiness, and project context without pretending to be machine intelligence.

  • Missing required skills are shown plainly.
  • A high score is a starting point, not a guarantee.
  • Color is never the only way status is communicated.

Key terms

Scoped work
A bounded outcome with a steward, deliverable, acceptance criteria, and estimated effort.
Match signal
Structured data that helps explain fit without exposing private information.
Project readiness
The degree to which a new contributor can understand current state and safely start.