evidence for AI-assisted professional work
Evidence for the work you actually did with AI.
Vreko helps AI-heavy engineers and builders assemble inspectable evidence for specific claims about their work: what happened, who or what contributed, what was independently observed, and what is still unknown. In the private Alpha, that becomes a Passport you control. A recipient sees only the view you approve for them.
Private Alpha. Applications are reviewed and onboarding is curated. No instant install. Nothing is published.
Specimen operator
Platform engineer. Works with coding agents on most changes.
- purpose
- Evaluate demonstrated work for a platform-engineering role
- shared with
- one hiring reader
- 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.
The evidence supports this. Repository history shows the operator authored the migration plan and most of the changes, and a reviewer other than the author approved the release. Agent-written changes are recorded in session receipts.
Declared by the operator. Wording corrected on 2026-09-26.
attribution · who did the work
operator · known / agent or team · partial
Operator authored the plan and directed the work. Some changes were agent-written and are recorded as the agent's.
what this view establishes
- The operator led a reviewed migration that was released.
what it does not establish
- Business impact.
- That the design was the best option.
- Sole personal implementation 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 · work by operator · observed 2026-09-27
- source recordCode review recordsupports
A reviewer other than the author approved the release change.
independently observed · work by operator · 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 · work by agent · observed 2026-09-27
unknownRuns production on-call for the billing service.
Not enough evidence. Not a negative finding. No source in this view addresses on-call work, so the claim stays unknown.
Résumé line, declared by the operator and not verified.
attribution · who did the work
operator · unknown / agent or team · unknown
Declared by the operator. No source in this view addresses the proposition.
what this view establishes
Nothing yet.
what it 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.
the problem
AI makes the work easier to produce. It does not make it easier to account for.
When an engineer works with agents, output arrives faster than the record of how it was made. The answers to five ordinary questions end up scattered across repositories, chat logs and tool histories, and are easy to overstate in either direction.
- Who or what contributed?
- What responsibility did the engineer carry?
- What actually happened?
- What did anyone other than the author observe?
- What is still unresolved?
This is not an argument against working with AI. It is about being able to show what you did with it.
how vreko works
From one specific claim to one approved view.
- claim
A specific claim
Start from something consequential and specific, such as “led the migration of the billing service to a message queue.”
- evidence
Evidence with different authority
A repository records history. A reviewer's approval is someone else's act. Your own statement is a declaration. Vreko keeps them apart, along with who or what did the work.
- state
A state for each claim
Supported, partially supported, contested, contradicted, or unknown. Unknown means the evidence does not establish the claim. It does not mean the claim is false.
- private passport
A private Passport
Claims, evidence and states stay in your Passport. A correction is recorded alongside the original; it does not rewrite the source record.
- approved view
One approved view
You choose a recipient and a purpose, preview exactly what they will see, and approve it. Nothing else in the Passport goes with it.
the passport · specimen
A Passport is a view you approved, not a profile.
Each claim carries its own state, its evidence, and what that evidence does not establish. There is no overall score, rank or badge, because a person is not a claim.
- Artifact
- Ask the Passport
- answer bound to this view
- Inspect evidence
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, corrected or disputed by the operator. A declaration is not evidence that it is true.
Origin says where material on the page came from. It does not say who did the work: attribution (operator, agent, team or unknown) is shown separately, and neither changes a claim's state.
ask the passport · specimen exchanges
Ask answers from the approved view, and only from it.
A recipient can ask the Passport a question. The answer comes from the view the operator approved for that recipient and purpose. It does not consult the private Passport. When the view cannot answer, it says so, and shows what it does establish nearby.
asked Did they lead the billing-service migration?
This view supports it. The operator led a reviewed migration that was released.
Unknowns and limits stay attached to the answer.
what this view establishes
- Repository history shows the plan and changes under the operator's account (team repository).
- A reviewer other than the author approved the release (code review record).
what it does not establish
- Business impact.
- That the design was the best option.
Based only on the view approved for one hiring reader, to evaluate demonstrated work for a platform-engineering role.
asked Did they personally implement the whole billing-service migration?
This view does not establish that.
Unknown is not false. Leading the migration is narrower than implementing every part of it, and agent work stays the agent's. You may request additional evidence.
what this view establishes
- The operator authored the migration plan and directed the work (team repository).
- Some changes were written by an agent and are recorded as the agent's (agent session receipts).
- A reviewer other than the author approved the release (code review record).
what it does not establish
- Sole personal implementation of every part of the migration.
Based only on the view approved for one hiring reader, to evaluate demonstrated work for a platform-engineering role.
when the view cannot answer · alpha contract
Asking is not requesting. Only a submitted request reaches the operator.
- askThe recipient asks the viewAsk answers from the approved view only. An ordinary question is not passed to the operator as a request.
- insufficient viewThe view cannot answer“This view does not establish that.” Unknown is not a negative finding.
- submit requestThe recipient may submit one bounded requestAn explicit request names the exact question, the purpose and who is asking. Only a submitted request reaches the operator. Submitting it reveals nothing beyond the approved view and shares nothing new.
- operator decidesThe operator decidesStop, refuse, narrow, authorize a source, or provide evidence.
- separate approvalAnything new is approved separatelyIf what the recipient can see would change, it is prepared as a new version of the view. The operator previews exactly what changes and approves it separately. Only then does the recipient see it.
operator decisions
- STOP
- Closes the exchange. Nothing new is shared.
- REFUSE
- Declines the request. Nothing new is shared.
- NARROW
- Prepares a narrower answer. The recipient sees it only after a separate approval.
- AUTHORIZE / PROVIDE
- Connects a source or adds evidence. A changed view still needs a separate approval, and needing to gather evidence shares nothing by itself.
Neither stop nor refuse says anything about whether the claim is true. A request exists because the approved view was not enough, not because anything private was found.
Alpha contract, shown as a specimen. Not a live request interface.
Specimen exchanges, written to the Alpha's answer rules from the synthetic example. Ask is part of what the Alpha is testing.
what you control · the alpha contract
Connecting a source is not sharing it.
These are the terms of the Alpha contract, which is what the Alpha is testing. Which of them run in code, are recorded as metadata, or are operated by hand is under independent review before the Alpha opens.
data in · sources
What Vreko has permission to read.
- You connect the smallest source that could help resolve a specific claim, and you see which claim before you authorize it.
- Connecting a source does not publish or share anything.
- Reading a source and keeping evidence from it are separate decisions. Raw source content is not kept by default.
- Disconnecting a source stops future reads. It does not by itself withdraw a view you already approved; that is a separate control.
data out · shared views
What another person has explicitly been allowed to see.
- A shared view is one approved projection, for one recipient and one purpose. You preview it before you approve it.
- Evidence you excluded is not in the view. Neither is how much was excluded, or that anything was.
- Revoking a shared view is its own control, separate from disconnecting a source. Revoking does not delete evidence from your sources or your Passport.
- A recruiter who referred you gets nothing from the referral itself: no access to your sources or your Passport.
- Changing a claim does not silently change a view you already approved. A changed view needs a new approval, and nothing can recall what a recipient has already read or saved.
- OBSERVE
Vreko may read the named source, within the stated scope, for the stated claim.
- DERIVE
Vreko may compute an evidence result for that claim. Unrelated claims are not derived.
- RETAIN
Vreko may keep the normalised evidence. Raw source content is not kept by default.
- DISCLOSE
You approve one bounded view for one purpose after seeing exactly what leaves.
private alpha · applications open
Build a private Passport from work you already did.
for builders · private alpha
A small, curated cohort of AI-heavy engineers and builders.
Bring a real claim or a target role. Connect the smallest source that could support it. Review what Vreko derives, correct it, and decide whether anything is shared. Applications are reviewed and onboarding is guided.
How the Alpha works →what exists · what is being tested · what is not built
Nothing moves left without evidence.
current
- Receipts have been produced, in recorded runs, from real AI-assisted work on more than one execution host, through one shared emitter, without duplicate provider credentials.
- In those runs each receipt records who authored a change and whether a verifier other than the author was observed. When none was, the receipt says NOT OBSERVED.
- A private Alpha. Applications open, onboarding curated, no public install.
testing
- A Passport that holds evidence and is not published. It is the object under test in the Alpha; no hosted Passport is live today.
- Ask the Passport, answering only from a view the operator approved.
- Whether a hiring reader can read a Passport view in under a minute and name what is still unknown.
- Whether a hiring reader will legitimately rely on Vreko's proposition-specific authority state for a consequential decision without reconstructing every underlying source.
- Whether people grant a narrow permission when they see the exact claim it serves and exactly what would leave.
- Whether a small Alpha cohort completes the loop without founder help.
not built
- Public profiles, search, or any recruiter directory.
- Certificates, achievements, scores, rankings, or Vreko acting as an authority on anyone's ability.
- Matching, a job board, or a marketplace.
- Automatic planning of what evidence to gather next. Today that is a person's judgement.