Evidence Layer
Why Evidence Artifacts?
Regulated workflows increasingly require defensible documentation: what data was used, when it was observed, and where it came from. Evidence artifacts are designed to support these requirements.
Data infrastructure only. Not legal advice. No certification provided.
The Problem with PDFs and Screenshots
Many compliance, risk, and reporting workflows still rely on manual evidence collection: downloading PDFs, taking screenshots, copying data into spreadsheets. This approach creates several challenges:
- Version ambiguity: Which version of the document was actually used?
- No provenance: Where did the data come from? When was it observed?
- Reproducibility gaps: Can the same reference be retrieved later for audit?
- Manual overhead: Time spent collecting and organizing evidence instead of analyzing it.
What Evidence Artifacts Provide
An evidence artifact is a versioned data snapshot with embedded metadata designed to support reproducible references:
as_of— observation or effective timestampschema_version— versioning for deterministic interpretationsources[]— provenance links (URLs, observation timestamps)content_hash— deterministic SHA-256 hash of normalized content
These fields enable workflows to reference exactly what was known at a given point in time—supporting audit trails without claiming compliance outcomes.
Infrastructure, Not Certification
FeedOracle provides data infrastructure. We produce evidence artifacts; we do not certify compliance, make decisions, or guarantee regulatory outcomes.
This separation matters: your organization owns its controls, governance, and conclusions. We provide the underlying data layer with traceable provenance and reproducible references.
See our Language Guidelines for detailed scope definitions.
Use Cases
Evidence artifacts support a range of regulated workflows:
- Stablecoin oversight — monitoring issuer disclosures for listing governance
- Reserve attestation tracking — reproducible references for reporting workflows
- Carbon/ESG reporting context — traceable energy and carbon signals
- Treasury risk monitoring — governed inputs for exposure workflows
- Operational due diligence — evidence packs for committee reviews
- Protocol health monitoring — versioned infrastructure signals
Optional: On-Chain Anchoring
For workflows requiring independent timestamp verification, evidence artifacts can optionally include on-chain anchor references (XRPL). Anchoring is not mandatory and does not change the legal status of the data—it provides an additional layer of timestamp provenance where useful.
Next Steps
If you're evaluating how evidence artifacts might support your compliance, risk, or reporting workflows, we can map your current process to concrete deliverables and integration paths.