# Core concepts

> Plain-language definitions of the building blocks the docs lean on, such as challenges, verifiable credentials, rubrics, team formats and sponsored challenges.

This page is the reference for the vocabulary the student and company pages lean on. If you want to look up exactly what one term means, this is the place.

For short definitions of other words, see the [glossary](/docs/reference/glossary.md). This page is the longer version for the core ideas.

## Challenge

The unit of work on Ewance. A short, project-shaped brief modelled on the work a professional in a given discipline would do. Every challenge has:

- A **scenario**: the situation you are working in.
- A **deliverable**: what "done" looks like (slide deck, written report, code repository, design file or a mix).
- **Constraints**: time, budget, audience, technical limits.
- A **rubric**: what reviewers will look for.

Briefs come from two sources: **Ewance's editorial team** (most of the catalogue) and **industry partners** who sponsor briefs directly. Sponsored briefs are flagged on the challenge page. See [How challenges work](/docs/students/how-challenges-work.md) for the longer version.

## Verifiable credential

The artefact a student earns when their submission is accepted. Not a PDF: a **standards-compliant, cryptographically signed document** anchored on a public blockchain (Base, an Ethereum L2).

Three standards converge in one document:

- **W3C Verifiable Credentials 2.0**: the umbrella spec for portable, verifiable claims.
- **Blockcerts v3**: the blockchain-anchoring profile.
- **Open Badges 3.0**: the achievement-credential profile.

This is what makes a credential **independently verifiable**: a recruiter can confirm authenticity without trusting Ewance. The cryptography speaks for itself.

Longer versions: [Certificates](/docs/students/certificates.md) (student view) and [Verified credentials](/docs/companies/verified-credentials.md) (recruiter view).

## Rubric

The published evaluation framework for a challenge. Every brief states its rubric up front. Reviewers grade against the stated criteria, not against any hidden bar.

Three rubric outcomes:

- **Accepted on first submission.** Signal: got it right the first time.
- **Accepted after revision.** Signal: responded well to feedback.
- **Not accepted.** Rare. It needs several compounding issues.

Recruiters can look at the rubric outcome when they review candidates. See [Searching for talent](/docs/companies/searching-talent.md).

## Submission

The deliverable a student uploads when a challenge is complete. The format depends on the brief: slide deck, report, code repository, design file or a mixed bundle.

A submission **stays private by default**. Ewance does not publish it. What becomes public is the *credential* the submission is anchored to, not the work itself. The student decides who to share the work with directly.

## Team format

Three working modes for a challenge:

- **Solo**: one person, end to end.
- **Pair**: two students splitting the work along natural seams.
- **Squad**: several students, often from different disciplines.

The team format is recorded on the credential, so recruiters see how a submission was produced. See [Teams and collaboration](/docs/students/teams-and-collaboration.md).

## Sponsored challenge

A challenge whose brief was contributed by an industry partner. Students who complete sponsored challenges can surface in that sponsor's recruiter search. It is the most direct route from the learning side into the recruiting side.

Sponsored challenges are flagged on the challenge page. The student experience is the same as any other challenge. The difference is on the recruiter side.

See [ewance.com/companies](https://ewance.com/companies/) for sponsorship enquiries.

## Recruiter

The end user on the hiring side: an internal talent team, a hiring manager or an external recruiter. A recruiter looks for talent by what candidates have shipped, reads the submissions and reaches out directly. Recruiting runs on paid plans. See [ewance.com/pricing](https://ewance.com/pricing/).

See [How recruiting works](/docs/companies/how-it-works.md) for the recruiter-side flow.

## Industry partner

A company that **sponsors challenges** on Ewance. An industry partner is different from a recruiter: a recruiter might be from any company, while an industry partner is one that has put a brief in front of students. The two roles often sit in the same company.

## Anchor

The on-chain transaction that ties a credential to a permanent, public record. We use **Base** (Ethereum L2) for low gas costs while inheriting Ethereum's tamper-evidence. The anchor is what makes a credential outlive the platform. Even if Ewance disappears, the cryptographic proof remains on Base, and any Blockcerts-compatible verifier can confirm authenticity.

## Verification

The process of confirming a credential is authentic. Five checks run client-side:

1. **Schema**: is this a valid W3C VC, Blockcerts or Open Badges document?
2. **Signature**: was it signed by Ewance's issuer key?
3. **Issuer**: is the issuer key currently valid?
4. **Anchor**: does the on-chain reference match?
5. **Revocation**: has the credential been revoked since issuance?

If all five pass, the credential is valid. Verification happens in the recruiter's browser, with no call to Ewance.

The verification page is at [verify.ewance.com](https://verify.ewance.com).

## Revocation

The mechanism for marking a credential as no longer valid after issuance, for example if plagiarism is discovered after the fact. Revocation is rare in practice. Its existence is what makes the credential trustworthy at issuance.

A revoked credential is not deleted (that would be cryptographically suspicious). Verification returns a "revoked" status instead of "valid".

## Where to next

- For the student journey through these concepts, start at the [students section](/docs/students.md).
- For the recruiter view, start at the [companies section](/docs/companies.md).
- For a quick start, read [Getting started](/docs/students/getting-started.md).
