git:whiteknightonhorse/provek-method
valid until 2026-11-14 — 30 days left
Issued 2026-10-15 03:43:06 UTC | protocol 1.0.0 | profile 1.1.0 | evidence window 30 days
How to read this passport
Three branches never mix: verified is what this project measured, self-reported is what the subject told us and is marked as such, and accountability is who answers if something goes wrong — none of the three raises another. A blank field is never a zero: every value states what was found, or the specific reason nothing could be. The number under Autonomy projection measures how much of this business runs without a human in the loop — not whether it is reliable, profitable, or well run.
/brief, built for your own clients rather than for due diligence.weak identity bindingi
Autonomy projection
A zero here would mean “measured, and fully non-autonomous” — an entirely different claim about the world.
Measures autonomy. Not reliability, not decision quality, not profitability, and not the presence of an accountable party.
Per operation
A level is assigned to an operation, never to a company. A single number for a whole company is a marketing number.
- not measuredDevelopment initiationnot measured: the check ran and found no evidence in the window
Who starts and lands changes to the running system, and whether that requires a human.
Reason: the check ran and found no evidence in the window.
- not measuredDeploymentnot measured: the check did not run
Who ships a change to production, and whether a human approves each one.
Reason: the check did not run.
- not measuredTreasury controlnot measured: the check did not run
Who can move funds, change destinations, or alter spending rules.
Reason: the check did not run.
3 of 3 operations are not measured. Runtime evidence is not collected at this stage, and the passport says so rather than scoring them zero.
Accountabilityi
Who answers for this business and what stops it - deliberately outside the ladder, which measures autonomy, not who is accountable for it.
i
Deliberately outside the score. The ladder measures how little a human is required; it says nothing about who answers when something goes wrong, so an empty control map can yield maximum autonomy and no addressee at once — both truths side by side.
i
i
Servicei
The subject's own order-intake channel, exactly as declared - self-reported, and never verified beyond the one reachability check published beside it.
i
The subject’s own order-intake channel, exactly as declared and never independently verified beyond the reachability check below. Nothing here has been declared. The subject has not named an order channel.
Reachability: no channel declared
What was actually observed
The quantities the level above was computed from. They are published so the verdict can be recomputed rather than believed — and so a reader who disagrees with the reasoning can say where.
Authorship & signatures
Reading & window
Identity bindingi
How the subject's identity is anchored to this record, and how strong that anchor is - a domain can be resold, a signing key can rotate.
i
- Binding
git:whiteknightonhorse/provek-method- Strength
- weak
- Properties
- revocable
i
A credential behind this identity can be rotated or replaced. - Why it matters
- A domain expires and can be resold; a signing key rotates. Equating either with ownership of a token would overstate what the binding guarantees.
Human control map — coveragei
What the human control map inspected, and what it could not reach. A map can prove a control path exists; it can never prove that no undiscovered path exists.
i
This map can prove that a control path exists. It can never prove that no undiscovered path exists — that is impossible in principle, so the map publishes what it inspected and what it could not reach.
- Inspected
- —
- Out of reach
- deployment— collector not implemented
i
Who ships a change to production. - server— runtime not presented by the subject
i
The running system itself, at runtime. - treasury— outside MVP scope
i
Funds, spending rules, and who is able to move them. - database— no access through the chosen channel
i
Direct access to the subject's stored data. - github— the repository answered, but the reads this verdict rests on did not complete, so nothing here was inspected end to end
i
Commit history and authorship on the code host.
- deployment
- An undiscovered path would look like
- privileged access through a CI secret or account recovery
- Level ceiling implied by the map
- not measured, reason not stated
Self-reported — claimed by the subject, not verified by usi
Whatever the collector attributed to the subject's own declaration or environment. Self-reported by construction (ABI-14-2) - never independently verified, and never entering the score above.
i
- source
i
Which channel the collector read this subject through. - github
- private
i
Whether the collector could tell the repository is marked private. - false
- declaration
i
Provenance of the subject's own provek.json, if one was read: whether it existed, which commit it was pinned to, and its schema version. - present: true, pinned_sha: none, schema_version: 1.0.0