Operator Passport Alpha

Private Alpha / release-gated. This page describes the current Candidate-0 contract. It does not mean the Alpha is publicly available or release-certified yet.

The Alpha has one job: turn evidence from real AI-assisted work into a private Passport that you can inspect, correct, and deliberately share with a specific recipient.

You should not need to understand Vreko’s internal evidence model to use it.

The current path

1. Arrive from an invitation or Alpha handoff. A referral does not grant the sender access to your sources or private Passport.
2. Sign in. Vreko account authentication is separate from authorizing an evidence source.
3. Connect the smallest useful source. Vreko should ask for access because it can help answer a specific proof question, not because it wants every integration you have.
4. Receive the first evidence-backed state. A claim may be SUPPORTED, PARTIALLY_SUPPORTED, CONTESTED, CONTRADICTED, or UNKNOWN.
5. Inspect and correct. Review what Vreko can actually support and correct, dispute, exclude, or withdraw where the product permits it.
6. Choose recipient and purpose. Recipient relevance may change selection or presentation. It may not strengthen weak evidence.
7. Preview the exact projection. The preview is the disclosure boundary, not an approximation.
8. Approve and deliver. The recipient gets the approved projection, not your private Passport.
9. Recipient uses Ask the Passport. Ask answers only from the exact authorized projection.
10. Resolve one bounded request if needed. If the current view cannot establish an answer, the recipient may request clarification tied to that question and purpose.
11. Approve any changed view separately. A changed answer requires canonical reconciliation and a new approved projection.
12. Revoke or change access. Expired or revoked access must stay unavailable until you intentionally create new access.

What UNKNOWN means

UNKNOWN means the current authorized evidence does not establish the proposition.

It is not a silent negative judgment, and Ask the Passport does not search hidden private evidence for a more satisfying answer.

Common states

State	Meaning	Safe next action
No evidence yet	No useful claim has been established from the current authorized inputs	Continue the bounded source flow or leave the claim UNKNOWN
Source disconnected	The source is no longer available	Reconnect only if you still want Vreko to use it
Permission denied	Required source scope was not granted	Review the requested scope; do not widen access unless the proof question justifies it
Source unavailable	Vreko cannot currently read the source	Retry later; do not treat temporary absence as contrary evidence
UNKNOWN	Current authorized evidence does not establish the proposition	Leave it UNKNOWN or make a bounded evidence/request decision
CONTESTED	Material supporting and contrary evidence both exist	Inspect both sides; do not collapse the state into support
CONTRADICTED	Current evidence materially contradicts the proposition	Inspect the contrary basis and correct or dispute as appropriate
Projection needs re-approval	The previously approved view is no longer the correct disclosure artifact	Preview the replacement and approve it explicitly
Recipient access expired/revoked	The recipient no longer has active authorization	Create new access only if you intentionally want to restore it
System error	Product/runtime failure, not evidence	Retry or use the recovery path; do not infer anything about the claim from the error

What stays private

The recipient-facing flow must not expose, merely because it exists:

• provider credentials or refresh tokens;
• private source-account handles;
• undisclosed evidence;
• hidden evidence inventory or counts;
• the direction of hidden evidence;
• unrelated Passport claims;
• unrelated conversation or model memory.

A recipient may know that the current approved view is insufficient without learning what private material caused that limitation.

What Candidate 0 must prove

A successful traversal is:

invite → sign in → authorize one useful evidence path → inspect/correct → choose recipient + purpose → preview exact view → approve + deliver → recipient Ask → bounded request if needed → operator decision → separately approved revised view → revoke/change access

The Alpha is ready for broader use only when that traversal works on the exact deployed, release-certified candidate without founder product judgment or manual database/account-state edits.