Sources · evidence · claims · writing · review · export
Evidence Foundry is a workspace for researchers who must defend what they write. It keeps each major assertion linked to the evidence that supports it, the source that states it, or the open question that admits what is not yet known — from the first imported dataset to the exported chapter.
The loop · sources + evidence → claims → writing → rigor review → export
“Method B outperforms the baseline under low-signal conditions.”
Specimen entry — illustrative
In Evidence Foundry, every major scholarly assertion traces to one of three admissible groundings — and the workspace keeps the trace.
Evidence objects imported from your lab's own pipelines — datasets, analyses, validated results — filed with provenance and linked to the claims they support.
Citations that resolve to literature actually held in your source library — so the reference you cite is the reference you read.
When the evidence is not yet in, the claim is marked as a hypothesis or open question — visibly, in the record and in the draft.
AI may assist — draft, summarize, critique, review. It does not invent the science, and it cannot upgrade a claim's evidence status. Standing is a question of records, not rhetoric.
House rule · applies to every assistant in the workspaceThe workspace carries the work from record to manuscript without losing the thread between them.
| № | Stage | What it holds |
|---|---|---|
| 01 | Source library | The literature you actually hold — references, metadata, and the reading record behind every citation. |
| 02 | Evidence inbox | Evidence objects imported from field pipelines — data, analyses, results — retained with their provenance. |
| 03 | Claim cards | Each major assertion becomes a record: its wording, its status, and the evidence and sources that carry it. |
| 04 | Claim-linked writing | Drafts cite the record. As sections grow, the claim map grows with them. |
| 05 | Rigor review | Deterministic checks surface unsupported claims and broken links before a committee or reviewer does. |
| 06 | Export | Papers and dissertation chapters leave with a claim map and a canonical manifest of what stands on what. |
Status is computed from the links on record — not asserted by the author, and never by the assistant.
Evidence Foundry is the trunk workspace: field-specific analysis tools produce the evidence, and their outputs import here to become defensible scholarship. One early branch analyzes electrochemical biosensor data; the trunk itself is discipline-neutral.
A dissertation is years of claims. Keep every chapter's assertions tied to the record that will be examined — and know what is still open before the committee asks.
Instrument pipelines keep producing results; the workspace keeps them citable. Evidence lands with provenance and stays attached to the writing it supports.
Review a chapter by its claim map: what is grounded, what is contested, what is honestly declared open. The rigor check reads the record, not the prose.
A plain register of what is true of Evidence Foundry today.
| Item | Standing today | Status |
|---|---|---|
| Hosted workspace | Running at app.evidencefoundry.com with synthetic, non-sensitive demonstration data only. | Live |
| Institutional pilots | None yet. Early access is reviewed individually by the operator. | Open |
| Provenance receipts | Export manifests reserve the slot; cryptographic signing is not yet live, and we do not claim it. | Planned |
| Accounts & billing | Arrive with the managed-platform integration. Today, sign-in is the door to the workspace itself. | Planned |
Register revised 2026-07-06 · if a row here is wrong, write to bot@evidencefoundry.com.
Reviewed early access · individual replies
The workspace is open at app.evidencefoundry.com. Hosted accounts are granted by review — a short note about your research and what you need to defend is enough to start the conversation.
Contact · bot@evidencefoundry.com