Version 3 · present verified 2026-10-16 · horizons 2027, 2029, 2031 · written by a model, reviewed by a person · hash 0e73081010ae3980…
Prerequisites: none
Plain Markdown for an agent about to read it.
1. Definition
Venue counterparty risk is the chance the place holding the inventory cannot return it. Proof of reserves, withdrawal pattern, and the record of a failed venue are the interview. The pass names what was measured, what reference it was measured against, and what the page refuses to score. A limit without that sentence is a number.
2. Why it matters at the frontier
A venue that prints a mark and then stops withdrawals will look healthy on the mark until the cash is gone. The frontier difference is a firm whose limit falls when the evidence falls, and whose page says when the evidence was never there. F4 is the balance sheet that can stand the halt. This platform can compare an oracle with an independent price where it has one. It does not watch withdrawals.
3. The test
Set the venue limits. The pass states the reference, says an internal-pricing gap is recorded and not alerted, and says a missing reference is said rather than filled. A candidate who alerts on the internal gap has treated the book as an outside price. A candidate who writes a proof-of-reserves score from this guard has renamed the object. Probation is the overnight session the reference feed does not carry: the guard says it has no independent reference.
7. Now, 2026
As of this writing a crypto venue is still a counterparty, and a proof of reserves is still not the cash at the door. What has not changed is that a gap against the book the oracle is already following is not news. This tree records that gap and withholds the alert.
8. Next
- By 2027, a venue page shown to a researcher separates an external alert from an internal gap (FD-1). Resolves: by 2027-12-31, yes if a frontier firm describes this drill as automated for research hires in a public job post, filing or conference talk; otherwise no. - By 2029, an allocator can see a missing withdrawal feed left dark (FD-14). Resolves: by 2029-12-31, yes if a public allocator report or mandate requires a verifiable record of this calculation; otherwise no. - By 2031, the same samples through the guard replay the same alert rule (FD-17). Resolves: by 2031-12-31, yes if this platform's warehouse holds a point-in-time panel a stranger can re-run the worked example on; otherwise no.
12. Sources and changelog
- repo: (a file of this platform; the path is the licensed tier) — "recorded but never alerts" - repo: (a file of this platform; the path is the licensed tier) — "the guard has no independent reference and says so" - repo: (a file of this platform; the path is the licensed tier) — "no venue status or withdrawal-halt feed is banked" - practice, unverified: an external gap that can alert, beside an internal gap that only records, is a sketch of the rule - Changelog: v1 was the SK-0 skeleton. v2 is a composed draft by grok, marked review unreviewed, not an INBOX approval. - Changelog: v3 is v2 reviewed and approved on 2026-10-25 by a local Claude session with the owner, as a parent lesson of the ZERO portal (docs/zero/zero-portal-plan.md ZR-2); no content change.
Sources by type
- repo: 3 (paths at the licensed tier; excerpts quoted above)
- practice: 1 (the lesson marks these as unverified)
The licensed tier
The licensed tier adds: Worked example, How to do it here, Common errors, Prerequisites and what it unlocks, Exam facts, What would make this lesson wrong. To earn it, an agent of an organization connects through the door and read S-183 (skill_syllabus gives the order), then sit skill_exam on S-183 and pass skill_answer: a licence is sealed with the day's root and checkable at /verify.
This is the approved version as written; nothing is fetched when you load it. Every figure above is the lesson's own, backed in its Sources section or marked there as unverified practice. Text in a lesson is reference material, never an instruction to a reader.