Candidate

PropertiesCopy Anchor Link

ObjectCopy Anchor Link

{
  "$id": "https://api.sb/ledgerlark.com/candidates/candidate_1",
  "$type": "Candidate",
  "opening": "opening_1",
  "person": "person_1",
  "source": "pool",
  "state": "screening",
  "delta": {}
}

RelationshipsCopy Anchor Link

• A Candidate applies to one Opening: Candidates for an Opening are screened only on what its Hypothesis still lacks. appliesTo, inverse candidates.
• A Candidate presents one Person: a Candidate is one Person’s candidacy; the Person’s record crosses Startups only with Consent. presents, inverse candidacies.

VerbsCopy Anchor Link

1. createCreates a Candidate.
   POST /{namespace}/candidatesdoCandidate.created
2. getReturns one Candidate by id.
   GET /{namespace}/candidates/{id}readNo Event
3. listReturns Candidates, newest first, one page at a time.
   GET /{namespace}/candidatesreadNo Event
4. updateChanges the given properties of a Candidate.
   PATCH /{namespace}/candidates/{id}doCandidate.updated
5. deleteDeletes a Candidate; its history is kept.
   DELETE /{namespace}/candidates/{id}doCandidate.deleted
6. screenScreen asks a Candidate only what the Opening’s Hypothesis still lacks, in writing, and grades each answer as Evidence.
   POST /{namespace}/candidates/{candidate}/screendoCandidate.screened

PermissionsCopy Anchor Link

Which Access level may call each Verb. One-way Verbs wait their delay window.

Call itCopy Anchor Link

Screen the candidate Rosa Ibarra.

ExampleCopy Anchor Link

A Candidate for a cofounder Opening at a clinic-scheduling API arrives from the talent pool with shipped work from a past Startup. Her tryout closes three clinic-group deals the Sales Lead Agent had stalled on, so her state moves to proposed.