Read the equation
This relation defines Match in the source section “2. The one engine, three tools principle”. 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 Match 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
clock, no randomness, all arithmetic in `shopspring/decimal` so the same inputs always yield byte identical
scores and explanations (the AEDT reproducibility asset). It reads no demographic field, by type.
```
Match = Clearance*0.25 + Skills*0.25 + Certifications*0.15 + CustomerExperience*0.15
+ Experience*0.10 + LocationAvailability*0.10 (weights frozen, sum to 1.00)
Bands: Green >= 90 (Proposal Ready) · Yellow 75 to 89 (Potential) · Red < 75 (Recruiting)
Skills: exact match first, then SEMANTIC over stored bge HNSW vectors at cosine >= 0.62 (v1.1.0)
Output: per component trace + human readable rationale + gap summary + ModelVersion stamp
```
`screenMATCH`, `slateMATCH`, and `missionMATCH` are thin HTTP namespaces that mount the same
`matching.Handler` (`ScreenRoutes`, `SlateRoutes`, `ReadRoutes`, `IntelRoutes`, `MissionRoutes`), so the same
candidate against the same requirement shows the same number in all three. `commandcenter` and `staffing`
read the frozen `candidate_evaluations` the engine persists; they never recompute. A frozen contract test
pins the weights, bands, threshold, and ModelVersion so a refactor can never silently drift a number.
## 3. Request lifecycle
```mermaid
flowchart LR
R["HTTPS request"] --> N["nginx TLS"]
N --> P["RequestID, Recoverer, metrics, Timeout 60s, RateLimit/IP"]
P --> S["Session middleware: validate __Host- cookie, MFA satisfied, resolve org+principal"]
S --> C["CSRF double submit"]
C --> B["RBAC RequireCapability (CapSearchRun, CapBrainQuery, ...)"]
B --> T["RunInTenantTx: SET LOCAL app.current_org_id from the VALIDATED session"]
T --> H["handler to service to engine / brain"]
H --> A["append only audit row"]Exact original notation
Match = Clearance*0.25 + Skills*0.25 + Certifications*0.15 + CustomerExperience*0.15
+ Experience*0.10 + LocationAvailability*0.10 (weights frozen, sum to 1.00)
Bands: Green >= 90 (Proposal Ready) · Yellow 75 to 89 (Potential) · Red < 75 (Recruiting)
Skills: exact match first, then SEMANTIC over stored bge HNSW vectors at cosine >= 0.62 (v1.1.0)
Output: per component trace + human readable rationale + gap summary + ModelVersion stamp