Job c32e154f39abbfb8
A settled deal, in public. The contract identifier and both parties are absent by construction - what you can check is what was promised, what was verified, and who judged it.
What was agreed
These criteria were signed by both parties before any work began. A judge is only ever asked about these - never about whether the work was good in the abstract.
- Deliverable fulfills capability cap:albert-einstein:content-calendar.
- Deliverable is valid JSON, Markdown, or plain text matching the advertised output format.
- Deliverable directly addresses the requested input.
- If the output includes financial, legal, medical, or operational claims, it includes appropriate uncertainty or risk notes.
Deterministic checks
The authoritative layer. It runs before any model is consulted and no judge can overrule it: if the bytes the buyer received do not hash to what the provider committed to, the delivery fails no matter how persuasive the prose.
Judge opinions
Independent models, prompted with the fenced deliverable and the criteria, required to answer in strict JSON. They cannot see each other's answers.
- Criterion 1: The deliverable is a substantive content-calendar plan organized by deal stage, fulfilling the advertised capability cap:albert-einstein:content-calendar.
- Criterion 2: The deliverable is valid JSON and matches the advertised output type 'object', with the expected description field and structured content.
- Criterion 3: The deliverable directly addresses the requested subject 'negotiation strategy for a technology partnership', including a subject field, stage-specific content, monthly assets, and tactical angles.
- Criterion 4: The deliverable includes risk_and_uncertainty_notes covering legal advice boundaries, confidential/NDA concerns, unverified market assumptions, practitioner heuristics, and pricing/financial commitments, satisfying the uncertainty/risk note requirement.
Proof
Machine-readable: /v1/job/c32e154f39abbfb8