Disclosure Boundary
These pages define what BlockSkunk will say in public about Cleared Counterparty. They answer how you interoperate (states, shapes, gate signals, auth). They do not answer how Cleared reaches a pass, fail, or refer conclusion.
Maturity: Early Access (v0.1). Contract-preview until surfaces are marked Live on Integration Surfaces.
Purpose
Cleared is an eligibility fact product for quote and settle gates. The unit of record is the eligibility record: a sealed decision bound to policy_version with action allowances the venue can read fail-closed. Vault preimages and judgment engines stay off the public contract.
We publish
- Product identity: Cleared = eligibility fact for gate. Stratum = sealed SoR for the fact. Arbiter = assessor pack surface when labeled
- Lifecycle states a case / eligibility record can be in (names and transitions at the interface)
- Record shapes partners and venues consume (
case_id,allows[],policy_version,stratum_record_id, gate allow/deny) - Actor boundaries: ops onboard, venue gate-read, examiner pack-read — no vault via pack or public prove
- What a seal or pack proves at the interface (presence of a decided, versioned fact; consumption event) — not that Cleared’s internal screens were “correct”
- Demo public ledger receipts for
public_demonetworks only (Demo ledger) — digests and decision metadata, never vault bytes - Public error categories and synthetic request/response examples
- Auth model:
clr_Bearer keys, scopes as issued to partners - Maturity labels: Live / by arrangement / contract-preview
We do not publish
- Gate admission criteria, scoring models, or bureau waterfall rules
- Internal review reasoning, prompts, or provenance construction details
- Real client data, vault contents, or production subject identifiers beyond synthetic examples
- Proprietary risk / sanctions engines or list-source commercial names on the customer MSA
- Kill criteria, COGS internals, or Early Access commercial terms as if they were API contract
- Seals from private networks on the public demo ledger
- A full peer/block explorer as if it were the Cleared product
Three-line test
Before shipping any public page:
- Describes the interface an actor interacts with, not how conclusions are reached.
- Names states and signals, not the rules for admission or blocking.
- Explains verification of seals or packs, not production judgment processes.
Vocabulary
| Use | Avoid as hero framing |
|---|---|
| Eligibility fact / cleared pass | “KYB platform,” “we verify your customers” as the product category |
| Fail-closed gate | Fail-open, soft-allow on timeout |
policy_version bound seal | Undated “cleared forever” claims |
| Assessor pack without vault bytes | Dumping screening artifacts to the examiner |
| Stratum as quote SoR | Requiring outsider prove for every quote |
| Demo public ledger | “Public chain explorer,” commercial networks as public |
Forwarding
This page and the docs set are written to be forwarded to security, legal, and examiners without editing. If a question requires judgment logic, the answer is: not in the public contract — use private arrangement channels. See Access Model and Integration Surfaces.