Read the equation
This relation defines same live candidate set (rm_cand), so identified >= screened >= submitted >= approved alwa in the source section “dto”. It specifies the displayed relationship between the named quantities or parameters. Its interpretation depends on the source’s stated variables and conditions; this record does not assign an unprovided physical or cognitive meaning to them.
Terms & definitions
The recovered passage does not supply a separate symbol table. Read the source context for the notation used in this version; familiar letters may carry different meanings in other builds.
How it works
Read same live candidate set (rm_cand), so identified >= screened >= submitted >= approved alwa as the quantity being defined or updated by this relation.
Substitute the source-defined variables or recorded values and follow the displayed arithmetic and indexing exactly.
Use this version’s variable definitions and update order. The same symbol may be assigned a different meaning in another build.
Assumptions & limits
This source expression was recovered from the pinned code revision. Its presence does not establish that the associated program was built, run, or scientifically validated.
Original context
Read the surrounding source passage
// Package recruitmatch is the recruitMATCH tool: the recruiting operations rollup over the SAME tables // screenMATCH and slateMATCH already write. It owns no tables, so every number it shows equals what the // other tools show for the same candidate. // // Two invariants govern this package. // // First, the funnel is monotonic by construction. Every stage counts DISTINCT candidates drawn from the // same live candidate set (rm_cand), so identified >= screened >= submitted >= approved always holds. // Counting evaluation or slate membership ROWS instead would let a stage exceed the bench, because // candidate_evaluations carries one row per candidate and requirement pair and slate_members carries one // row per slate and candidate pair. A candidate screened against five requirements is five rows and one // person. Screened is a count of people. // // Second, this package emits no color and no band. Color is presentation and belongs to the frontend. // Bands belong to the frozen engine, which already stamped candidate_evaluations.band at write time, so // recruitMATCH reports the stored band and never recomputes one. Applying engine band thresholds to a // conversion percentage would conflate two different scales. package recruitmatch
Exact original notation
same live candidate set (rm_cand), so identified >= screened >= submitted >= approved always holds.