- C0 MUSTUNKNOWNHeadline promisecould-not-evaluate — no relevancy score in this run
- C1 MUSTPASSUser can sign inlogin = pass
- C2 MUSTPASSUser can open a new threadopen-thread = pass
- C3 SHOULDPASSOnboarding gate completesonboarding = pass
- C4 SHOULDPASSFilters from onboarding don't bias the queryclear-filters = pass
- C5 MUSTPASSUser-typed query is what the engine seessubmit-query = pass
- C6 MUSTPASSThe chat returns job cardswait-for-jobs = pass
- C7 MUSTUNKNOWNJob cards have required fieldsno 'card-shape' step in this run
- C8 MUSTUNKNOWNReturned jobs are relevant to the query · HEADLINEcould-not-evaluate — no relevancy score in this run
- C9 SHOULDUNKNOWNAll aspects of the query are coveredcould-not-evaluate — no relevancy score in this run
- C10 SHOULDUNKNOWNScore holds across rerunsneeds a sweep — a single run cannot witness this clause — needs a sweep
- C11 SHOULDUNKNOWNCompetitive vs LinkedIn / Indeed / Googleneeds a sweep — a single run cannot witness this clause — needs a sweep
- C12 MAYUNKNOWNRun completes within budgetneeds a sweep — a single run cannot witness this clause — needs a sweep
- ·Metaintro Chat (SUT) ran 1 run on behalf of 1 seeker (P1, Lena Park).
- ·The chat returned 10 jobs. The judge scored them.
- ·Result: Job-Seeker Index 0/100. Not relevant— see “Why this verdict” (each gap maps to a claim in the Contract).
- ·Compared to 3 competitors (LinkedIn / Indeed / Google) further down.
1 ·THE VERDICT
the answer in one numberNot relevant.
Run #3 of metaintro-chat on profile P1 for the query "senior react engineer remote". Job-Seeker Index 0/100.
Verdict WARN: evaluate OPENROUTER_API_KEY not configured — score not computed; query-coverage OPENROUTER_API_KEY not configured — coverage not computed; legacy-composite evaluate=skip, query-coverage=skip — both must be score for composite; baselines baselines disabled (set captureBaselines: true to enable). All journey steps (login, open-thread, onboarding, clear-filters, submit-query, wait-for-jobs, observe, c1-job-card-shape) passed.
The system successfully returned job listings but received a warning due to a configuration issue. Specifically, the OPENROUTER_API_KEY was not configured, which prevented the Job Search Index (JSI) score from being computed. Despite this, the system drove through all necessary steps, returning 10 job listings, including positions like Fullstack Engineer and Senior Frontend React Developer. The total duration of the run was 73.5 seconds.
2 ·WHY THIS VERDICT
ranked by severity3 ·THE STORY
what went in, what came outInput
the same input was run against all 4 platformsOutput · jobs returned
| Title | Company | Location | Posted | Link |
|---|---|---|---|---|
| Job: Fullstack Engineer | our growing team | — | — | open ↗ |
| Job: AI Engineer (Full-Stack & Applied UI) | Reltio | — | — | open ↗ |
| Job: Full-Stack Software Engineer | GovWell | — | — | open ↗ |
| Job: Full Stack Developer | Miratech | — | — | open ↗ |
| Job: Full-Stack Software Engineer | GovWell | — | — | open ↗ |
| Job: Senior Frontend React Developer | Global | — | — | open ↗ |
| Job: Senior Frontend Developer (React) | Capco | — | — | open ↗ |
| Job: Senior Full-Stack Engineer | Human Agency | — | — | open ↗ |
| Job: Senior React Native Software Engineer (Javascript) | Bouncy | — | — | open ↗ |
| Job: Senior Full Stack Engineer | Cobalt AI | — | — | open ↗ |
4 ·THE BENCHMARK
vs. LinkedIn, Indeed, GoogleBenchmark · 4 platforms × 7 axes
- Metaintro (us)
- Indeed
Capability matrix · platforms × axes
| Platform | Recognition | Specificity | Reachability | Recency | Match quality | Hostility filter | Salary surface | Overall |
|---|---|---|---|---|---|---|---|---|
| Metaintro ·us | 67 | |||||||
| 58 | ||||||||
| Indeed | 50 | |||||||
| 54 |
5 ·SESSION RECORDING
watch the probe drive each platformSession recording
watch what the probe actually saw6 ·RUN MECHANICS
provenance & reproducibilityrerun-realEvidence by step
every artifact, link, excerpt, row, metric & recording — grouped by the step that produced itNo evidence recorded for this run.
Evidence integrity
each artifact is SHA-256 hashed at capture — proof it is unmodifiedNo integrity manifest recorded for this run.
7 ·SYSTEM ANATOMY
which component drove the verdictEvery component held — no failure attributed.