# Reliable Context > A system of record for fused private and public information: one record per real thing, a cited, dated source behind every value, any past state reproducible. Reliable Context makes one product: a system of record for organizations that must defend every value they act on, run inside their own perimeter. Demonstration records on this site are fictional and labelled as such. Contact: hello@reliablecontext.com. Read the linked page before quoting it; this file is a discovery aid. Canonical origin: https://reliablecontext.com. ## Product - [Home](https://reliablecontext.com/): A system of record for fused private and public information: one record per real thing, a cited, dated source behind every value, any past state reproducible. - [Product](https://reliablecontext.com/product): The record as a reader meets it: one record per real thing, a dated source behind every value, declared negatives, and an export carrying its chain of custody. - [The four guarantees](https://reliablecontext.com/guarantees): One canonical record per real thing; a cited, dated source behind every value; unknowns declared; any past state reproducible. What each guarantee rules out. - [The problem](https://reliablecontext.com/problem): Private and public information are fused by a person, in a document, and provenance dies at the fusion. Three failure stories, and what a record emits instead. - [Inside your perimeter](https://reliablecontext.com/perimeter): Runs inside your infrastructure, one database per organization. Sources, model routing, reader clearance, retention and audit export are your policies. - [Demonstration](https://reliablecontext.com/demonstration): Five fictional records, read as a person acting on them would: the sentence behind each value, its source and date, and the record replayed to an earlier date. - [Evidence and changelog](https://reliablecontext.com/evidence): The two factual claims this site makes, each with its counting rule and what would falsify it, plus our publication policy and a dated changelog. ## Sectors - [Sectors](https://reliablecontext.com/sectors): One kernel for pharma, financial services, government, legal, insurance and supply-chain compliance, each with two worked cases and its recordkeeping rules. - [Pharmaceuticals](https://reliablecontext.com/sectors/pharma): Competitive intelligence that survives the question a portfolio committee always asks: where did that come from, and when. - [Financial services](https://reliablecontext.com/sectors/financial-services): Onboarding and counterparty files where every element of the decision can be shown to a supervisor with its source attached. - [Government](https://reliablecontext.com/sectors/government): A basis of action that can be reconstructed years later, from retained sources, by someone who was not there and who is entitled to disagree. - [Legal](https://reliablecontext.com/sectors/legal): Diligence and investigation memoranda in which every assertion is already authenticated, because it never existed without its source. - [Insurance](https://reliablecontext.com/sectors/insurance): Underwriting and reserving inputs that can be traced to the document they came from, including the ones that were not used. - [Supply-chain compliance](https://reliablecontext.com/sectors/supply-chain): Supplier and shipment files that hold together across tiers, transliterations and a supplier list that changes every quarter. ## Working with us - [Company](https://reliablecontext.com/company): Reliable Context makes one product: a system of record for organizations that must defend every value they act on, run inside their own perimeter. - [How an engagement works](https://reliablecontext.com/engagement): Scope one disputed entity, deploy inside your perimeter, read the first record together, then decide whether to widen the work. - [Request access](https://reliablecontext.com/request-access): Bring one entity you already argue about internally. We build the record inside a boundary you control and you try to break it. What a first record contains. - [Work with us](https://reliablecontext.com/work-with-us): Three ways to work with Reliable Context: research collaboration under a data agreement, building the kernel itself, and deploying it inside your organization. - [Security and data handling](https://reliablecontext.com/trust): The deployment runs inside your infrastructure. Review source, model, access, retention and export policies for your engagement. - [Security overview](https://reliablecontext.com/security): Architecture, data flows, deployment in your perimeter, model routing and the security-review process. No certification claim. - [Frequently asked questions](https://reliablecontext.com/faq): Answers about records, deployment, data, model routing, engagement and research at Reliable Context, from what a record is to how to challenge a claim here. - [Contact](https://reliablecontext.com/contact): Write to Reliable Context about a first record, research collaboration or a security review. One email channel and a clear next step. ## Research - [Research program](https://reliablecontext.com/research): Eight open problems in identity, declared absence, source decay, source disagreement and evaluating fused records, plus a twelve-entry annotated reading list. - [Position paper: a kernel of truth](https://reliablecontext.com/paper): Position paper, version 0.1, 21 September 2026: fusion and provenance, identity, declared negatives, replayability, and what a system of record owes its reader. PDF: https://reliablecontext.com/paper.pdf - [Research library](https://reliablecontext.com/library): Every article on reliablecontext.com, by subject: identity, provenance and time, ontologies, truth discovery and knowledge fusion, and LLM evaluation. - [Article catalog](https://reliablecontext.com/articles/llms.txt): Generated list of the published articles under /articles. ## Reference - [Reference](https://reliablecontext.com/reference): A field reference to truth discovery, knowledge fusion, provenance and context engineering: terms, comparisons, methods and standards. - [Glossary](https://reliablecontext.com/glossary): Definitions for truth discovery, knowledge fusion, identity, provenance, time, context engineering, evaluation and governance. - [Comparisons](https://reliablecontext.com/compare): Side-by-side distinctions between approaches to evidence, records and context, with criteria for when each is useful and how the two combine. - [Methods](https://reliablecontext.com/methods): Methods for assessing evidence and maintaining defensible context, each with its steps, the checks a reader can run afterwards and the pitfalls that recur. - [Standards](https://reliablecontext.com/standards): A directory of public identifiers, vocabularies, data models, formats, regulations and registries relevant to defensible records. ## Optional - [Corrections](https://reliablecontext.com/corrections): What counts as an error on this site, how to report one with the page and sentence, and the public dated log of retractions and source additions. - [Legal notice](https://reliablecontext.com/legal): Legal notice for the Reliable Context website, including contracting details, informational content and fictional demonstrations. - [Privacy](https://reliablecontext.com/privacy): The main site sets no cookies and loads no analytics. How connection data, article page views, forms and email are handled, and how to ask for deletion. - [Terms of use](https://reliablecontext.com/terms): Plain-language terms for reading, quoting and linking to the Reliable Context website: no warranty from a public page, and every demonstration is fictional. - [Sitemap](https://reliablecontext.com/sitemap.xml): Every page, including each glossary term, comparison, method and standard.