What this example demonstrates
This is an AI-assisted demonstration prepared for Boundev. It uses three original synthetic snippets, not customer code or named model outputs. No independent human reviewers have completed this example. It demonstrates the structure of a judgment, not measured reviewer agreement or a model-performance benchmark.
The question is deliberately narrow: does the supplied function follow a defined session-validity contract? The example does not assess a complete authentication system.
The contract
Input validation, token verification, storage consistency, user authorization, clock synchronization, and concurrency are outside this exercise. These assumptions must travel with any exported judgment.
- Return false when the session is missing.
- Return false when revokedAt is not null, including the value zero.
- expiresAt and now are finite numeric timestamps in the same units.
- A session is valid only when expiresAt is strictly greater than now. Equality means expired.
- Return a boolean and leave the input unchanged.
Three supplied variants
// A: expiry is never checked
const validA = (session, now) => !!session && session.revokedAt == null;
// B: matches the stated contract
const validB = (session, now) => !!session && session.revokedAt == null && session.expiresAt > now;
// C: accepts equality at the expiry boundary
const validC = (session, now) => !!session && session.revokedAt == null && session.expiresAt >= now;Item-level findings
| Artifact | Illustrative outcome | Evidence and limit |
|---|---|---|
| A | Revise | At now=100, expiresAt=99 and revokedAt=null, A returns true. It misses expiry entirely. |
| B | Meets this contract | The guard rejects a missing or revoked session and uses the required strict greater-than comparison. This is limited to the supplied contract. |
| C | Revise | At now=100 and expiresAt=100, C returns true. The equality boundary contradicts the requirement. |
How to record a disagreement
A reviewer might initially accept C because the expiry convention is unclear in another system. Here the supplied contract resolves that ambiguity: equality means expired. The final reason should cite that requirement and preserve the original reviewer judgment when real reviewers are involved.
The download contains an empty human-review worksheet for calibration. It does not contain invented reviewer names, review durations, agreement rates, or adjudication records.
What a buyer should take away
A useful record includes the exact artifact version, requirement, observed issue, outcome, evidence type, and limits. Keep execution results separate from an expert’s interpretation. Keep an example separate from evidence of service quality.
Before using this format commercially, assign the actual reviewers, calibrate on a held-out subset, agree the escalation policy, and record real delivery time. The CSV and JSONL exports are a starting schema, not a promised integration with another platform.
Use the example
Download the report, original fixtures, rubric and CSV/JSONL records. These materials are an illustrative example, not independent human-reviewed results.