Skip to content
vreko

example passport · for recruiters and evaluators

Read one approved view in under a minute.

This is what a recipient sees after an operator approves a view for one purpose. Open a claim for Vreko's reading of the evidence, then inspect the evidence itself. Nothing here is a score.

Specimen · synthetic data. Not a real person, not a live Passport, and not produced by a certified production projection.

a 30–60 second read

  1. What is the actual claim?
  2. What evidence supports or limits it, and from which source?
  3. What was observed, what was declared, and what is unknown?
  4. What did the operator do, and what did an agent or team do?
  5. What single follow-up question would change your next step?
passport · approved viewspecimen

Specimen operator

Platform engineer. Works with coding agents on most changes.

purpose
Evaluate demonstrated work for a platform-engineering role
shared with
one recipient
approved by the operator
2026-09-28 · expires 2026-10-28
supportedLed the migration of a billing service from scheduled jobs to a message queue.
vreko-derived

The evidence supports this. Repository history shows the operator authored the migration plan and most of the changes, and a distinct reviewer approved the release. Agent-written changes are recorded in session receipts.

operator-provided

Declared by the operator. Wording corrected on 2026-09-26.

attribution Operator authored the plan and directed the work. Some changes were agent-written and are recorded as such.

what this establishes

  • The operator led a reviewed migration that was released.

what this does not establish

  • Business impact.
  • That the design was the best option.
  • Sole authorship of every change.
Inspect evidence (3)
  • source recordTeam repositorysupports

    Repository history shows the migration plan and changes under the operator's account.

    platform record · not an independent evaluation · observed 2026-09-27

  • source recordCode review recordsupports

    A reviewer other than the author approved the release change.

    independently observed · observed 2026-09-27

  • source recordAgent session receiptscontext only

    Session receipts record which changes an agent wrote and which the operator wrote.

    self-reported · not independent · observed 2026-09-27

partially supportedReduced failed billing runs after the migration.
vreko-derived

Part of this is supported. The rest is not. The tracker records fewer billing-failure tickets after the release. Nothing bound here separates the migration's effect from other changes made in the same period.

operator-provided

Declared by the operator.

attribution Not attributable from this view.

what this establishes

  • Billing-failure tickets fell after the release.

what this does not establish

  • That the migration caused the drop.
  • The size of any effect.

what could resolve it A failure-rate measurement that isolates the migration from other changes.

Inspect evidence (1)
  • source recordIncident trackersupports

    Billing-failure tickets recorded before and after the release.

    platform record · not an independent evaluation · observed 2026-09-27

contestedHad the migration verified by someone other than the author before release.
vreko-derived

Evidence points both ways. Unresolved. One recorded run shows a distinct author and verifier. A second run shows the author verified their own work. Both stay visible; neither is collapsed.

operator-provided

Declared by an agent in-session. The operator has not confirmed it.

attribution Agent declared. Operator authority over the declaration is not established.

what this establishes

  • That contrary evidence exists and is unresolved.

what this does not establish

  • A verdict either way.
  • A confidence level.
Inspect evidence (2)
  • source recordAgent session receiptssupports

    Run A: a distinct verifier was observed.

    independently observed · observed 2026-09-12 · ◍ stale, not re-read within its window

  • source recordAgent session receiptscontrary

    Run B: the author verified their own work.

    self-reported · not independent · observed 2026-09-12 · ◍ stale, not re-read within its window

contradictedCompleted the cut-over with no customer-visible downtime.
vreko-derived

The bound evidence goes against this. The status page records a customer-visible outage during the cut-over window.

operator-provided

Declared by the operator.

attribution Not attributable from this view.

what this establishes

  • Bound evidence goes against the claim.

what this does not establish

  • Who or what caused the outage.
Inspect evidence (1)
  • source recordStatus page historycontrary

    A published outage overlaps the cut-over window.

    platform record · not an independent evaluation · observed 2026-09-27

unknownRuns production on-call for the billing service.
vreko-derived

Not enough evidence. Not a negative finding. No source in this view addresses on-call work, so the claim stays unknown.

operator-provided

Résumé line, declared by the operator and not verified.

attribution Declared by the operator. No source addresses the proposition.

what this establishes

Nothing yet.

what this does not establish

  • That the claim is false. Unknown is not a negative finding.

what could resolve it An on-call schedule or paging record from the service's incident system.

Inspect evidence (0)

No source in this view addresses this claim.

three kinds of material, always kept apart

source record
Recorded by the source system itself, such as a repository's history or a tracker's record.
vreko-derived
Vreko's reading of what the evidence establishes for this claim. It can change when the evidence does.
operator-provided
Declared or corrected by the operator. A declaration is not evidence that it is true.

ask the passport

What Ask can and cannot answer.

Ask answers from this approved view: its claims, their states, their evidence, and what each does not establish.

It cannot see the operator's private Passport, evidence the operator excluded, or how much was excluded. A question this view cannot answer gets the same reply whatever was asked, and the operator may choose to answer a follow-up request or not.

asked Did they lead the billing migration?

supported

This view supports it. The operator led a reviewed migration that was released.

Repository history shows the operator authored the plan and most of the changes, and a distinct reviewer approved the release.

from this view

  • Repository history under the operator's account (team repository)
  • Approval by a reviewer other than the author (code review record)

not established

  • Business impact.
  • That the design was the best option.
  • Sole authorship of every change.

Based only on the approved view shared for this purpose.

asked Have they run production on-call?

unknown

This view does not establish that.

You may request additional evidence.

not established

  • Unknown is not a negative finding.

Based only on the approved view shared for this purpose.

asked Was AI involved?

Agent involvement is recorded for two claims: the migration (supported) and the pre-release verification (contested).

Where agent share is not recorded, this view does not say either way. Not recorded is not the same as not involved.

from this view

  • Session receipts that separate agent-written and operator-written changes
  • An agent-authored declaration

Based only on the approved view shared for this purpose.

asked What is still unknown?

unknown

Unknown in this view: runs production on-call for the billing service.

Unknown is not a negative finding. Separately, one claim is contested and one is contradicted; each keeps its own evidence.

not established

  • That the on-call claim is false.

Based only on the approved view shared for this purpose.

Specimen exchanges, written to the Alpha's answer rules from this synthetic view.

Corrections

A correction is recorded beside the original. It does not rewrite the source record.

  • operator-provided2026-09-26Operator narrowed 'Designed and built the billing queue' to 'Led the migration'. The earlier wording stays in history; the source records are unchanged.

Sources in this view

Each source is described by what it records and what that does not mean.

Team repository
Hosts the source and its history. Does not review or endorse the author.
Code review record
A distinct reviewer approved changes. Review is not endorsement of the author.
Incident tracker
Records incidents and tickets. Does not attribute cause.
Agent session receipts
Records what the operator and agent did in a session. Not a reviewer.
Status page history
Records customer-visible outages as published by the team.

Want a Passport of your own work?

The private Alpha is a small, curated cohort. Applications are reviewed.

How the Alpha works →
Vreko · by Marcelle LabsEvery claim on this site is current, part of the Alpha under test, or not built, and says which. The example Passport is a synthetic specimen.
Example Passport · Vreko