Method · v1 · frozen
How a verdict is reached
before capital moves.
This is the operating method for every engagement. It is fixed so a buyer can audit the process, not just the conclusion — and so a signed GO or KILL means the same thing next month as it does today.
Recompute what the venue owes. Diff it against what it did. Score the gap. If you cannot verify a cell, mark it UNKNOWN — never invent a clean zero.
The through-line · fail-closed reconciliation
The four moves
Every Scan runs the same spine.
01
Name the kill-criteria first
Before reading a page of marketing or a line of code, 3–5 falsifiable questions are fixed in writing. A NO on any one of them terminates the thesis. The Scan is not a tour of features — it is an attempt to kill the idea.
02
Recompute the other side
What the venue promises is never the truth-leg. Funding formulas, oracle prints, withdrawal paths, maker vs taker flow — each is reconstructed from independent inputs. If the independent leg cannot be sourced, the cell is UNKNOWN. It is never filled with zero.
03
Argue against the first draft
A research pass builds the case. A disconfirmation pass tries to break it. Tooling bugs, selection bias, and over-confident intervals are treated as first-class findings — published when they matter, not buried.
04
A person signs the verdict
The instrument gathers evidence and drafts. I reason and sign GO, GO-WITH-CONDITIONS, or KILL. No machine asserts a capital decision. The signed human verdict is the product.
Hard rules
These do not bend for a client or a narrative.
Fail closed
A failed, stale, or unverifiable value is UNKNOWN — never 0, never a silent default. A number you cannot re-run is cut from the deliverable.
Reproducible or cut
Every measured figure carries source, as-of, and method. If a buyer cannot re-run the check, it does not ship as evidence.
Paid to say no
KILL is a first-class outcome. The published sample reaches KILL on my own trading idea. That is not a marketing stunt — it is the method working as designed.
Not an audit
A Scan is a capital-safety / protocol-risk review. It complements a formal code audit; it is not a security guarantee and not investment advice.
Deliverable
What lands in your portal.
A written brief with a one-line verdict, the kill-criteria and how each closed, measured evidence with provenance, a reproduction appendix, and a SHA-256 you can check yourself. The machine drafts; I sign.
Signed, not asserted
One of these three, every time — no fourth option.
- Kill-criteria
- 3–5 · named in advance · adversarial
- Measured cells
- source · as-of · method · confidence
- Unmeasured
- UNKNOWN — never assumed safe
- Integrity
- SHA-256 on every published file
- Signer
- Skylar Sabo · named · not a bot
Scope · fail-closed
What this is. What it is not.
Is
- A capital-safety / protocol-risk review for one venue, vault, or strategy
- Independent recomputation of economic and operational promises
- A fixed-scope, fixed-price engagement with a signed verdict
- A complement to formal code audit and on-chain monitoring
Is not
- A security audit, penetration test, or formal verification
- Investment advice, a rating agency product, or a guarantee
- A machine-asserted GO/KILL without a human signer
- A claim that every risk was found — unmeasured remains UNKNOWN
Published proof
The method, applied in public.
Read a full Scan that reached KILL on my own idea — including the tooling flaws the method caught in itself. Then check the frozen artifact’s checksum if you want the integrity path.
Rysk RFQ option markdowns
Capturability, corr 0.979, hedge cost. Kill-criteria fired before days of runtime were committed.
Read the frozen sample →IntegrityVerify a report
Paste a SHA-256. Match means byte-identical to a published artifact. No match is INTEGRITY UNKNOWN — never a false pass.
Open the verifier →