API engineering
Structured fact data: a provenance-first JSON design
A practical data model for claims, sources, evidence relationships, assessment history, and clearly defined uncertainty.
03 FIELDNOTES / CATEGORY
API engineering
A focused reading path through The Evidence Journal. Design the contract between a claim and its evidence. These guides cover factual APIs, claim extraction, and provenance-oriented data without implying that a JSON response is automatically a verified conclusion.
How to use this collection
Start with the Fact API fundamentals to separate record retrieval from assessment. Continue with extraction to preserve the original question, then use the structured-data guide to keep sources, passages, versions, and decisions connected. Each article includes a primary research or documentation reference and a practical implementation discussion.
Start with the Fact API guide, then follow the fieldnotes below. All examples are illustrative and each article points to its own editorial source.
API engineering
Fact extraction APIs: turn text into atomic claims
Split complex text into checkable statements without losing the qualifiers, attribution, and context that change the question.
API engineering
Fact API fundamentals: from claims to verifiable evidence
Understand what a fact API should return, where evidence fits, and how to design a response that can be inspected.
Follow the claim. Find the evidence.
Go from a better question to a clearer evidence trail—one fieldnote at a time.