Define the boundary
Use approved datasets, views, fields, filters, and time ranges aligned to a specific investigation purpose.
This page describes the intake model we are building, not a connector you can switch on. No database provider is supported yet. If a specific system matters to your investigations, tell us — that input shapes what gets built first.
ReturnValue should know which records were requested, under what authority, from which schema version, and at what point in time before database evidence supports a financial finding.
Use approved datasets, views, fields, filters, and time ranges aligned to a specific investigation purpose.
Check types, keys, coverage, duplication, freshness, and unexpected schema changes before analysis.
Record the source, query or extraction definition, snapshot time, and transformation path behind every accepted result.
Database connectors are in active development with design partners, and this page describes what is being built and how to influence the order. None are available yet, and none can be switched on today; this reflects what is in development, not what is shipped. If your team would benefit from one of these sources, we want to know, because demand from real teams sets the order.
Relational sources are first, and the connector design will extend to similarly shaped sources afterwards. Connectors will be read-oriented at the schema level to help prevent accidental source mutation, and connection credentials will be scoped to the smallest privilege the workflow needs. Tables and columns will land as first-class sources, with types preserved and lineage tracked.
A connector that returns rows is easy. One that holds up against schema drift, partial data, mixed encodings, and the authentication quirks of a real production warehouse is the actual work. We are doing that work with a small group of design partners before opening connectors to everyone. This page will say available when the connector clears that bar, not before.
Reviewers can understand what was queried and why without receiving unrestricted access to the operational system.
The safest useful connection is the narrowest one that can answer the financial question.
Illustrative view. Values shown are examples, not customer data.