Claims are easy.
Evidence is harder.
Trace the distance between what a financial system claims, what its evidence demonstrates, and what remains unknown.
Start with an example ↘Build a disclosure ↗An autonomous settlement network is operationally resilient.
A controlled pilot does not establish production resilience.
Synthetic illustration. No documents retrieved.Choose a node above to inspect the distinction between the claim, its supplied evidence and the boundary of what can be inferred.
Disclosure editor
A rule-based inspection of publisher-supplied information. Each finding explains its trigger, what is missing and what cannot be inferred. No automated claim of truth.
The Autonomous Finance Project studies experimental financial autonomy. This workspace exposes the limits of the evidence behind individual claims — including those emerging from research.
Explore research protocols ↗Publish into your own infrastructure.
Import structured disclosures, inspect their schema, compute a content fingerprint and ship self-contained HTML or an isolated iframe. No remote runtime required.
Import an exported Transparency Layer record or validate an externally authored JSON file against the supported v1 fields. Imported content is treated as untrusted publisher input.
The JSON editor is independent of the form above until you select “Load into workbench”.
Publish a self-contained HTML disclosure or embed it as an isolated iframe. The iframe is created from the locally generated HTML and does not contact BondStats to render.
// Complete and validate the disclosure record above.
A hash detects changes to the exported JSON bytes. It does not establish who authored the record, whether its claims are true, or whether the linked sources are accessible.
Publisher-supplied data remains visibly identified. A source URL is not a verification certificate. No security or regulatory compliance claim is implied by use of this component.
Traceable conclusions. Explicit limits.
Every inspection is derived from publisher-supplied fields and visible rules. A linked source is not proof; a cryptographic fingerprint is not an authenticity certificate; a pilot is not a production deployment. Use the workbench to publish what is known and what remains open.
Research context ↗