Explanation on factgraph

Append-only ledger and provenance

Mon, 01 Jan 0001 00:00:00 +0000

About the append-only ledger and provenance#

factgraph never overwrites a fact and never deletes one. Every write you make through the SDK lands as a new row in an append-only ledger, and “removing” a fact is itself a new row that points back at the one being removed. This page explains why the store is shaped that way, how retraction works as a revocation rather than a delete, and how provenance metadata rides along with each assertion. The mechanism lives in factgraph.core.store.ledger.Ledger and in the write protocol that drives it.

Reasoning, evaluation, and evidence

Mon, 01 Jan 0001 00:00:00 +0000

Reasoning, evaluation, and evidence#

When you evaluate a rule against a factgraph, you do not just get back a set of answers. You get back answers that can each explain themselves, condition by condition, in a way that replays to the same result every time. This page discusses how a rule turns into result rows, why each row can carry its own proof, and what makes that proof deterministic. It is the conceptual companion to Evaluation and explanation, which lists the precise types and signatures.

Auditability

Mon, 01 Jan 0001 00:00:00 +0000

Auditability#

Auditability in factgraph is not a feature you switch on. It is a consequence of how the graph stores facts and how it explains conclusions. Because the ledger is append-only, every assertion carries its own provenance, and every evaluated conclusion comes back with an evidence structure that names the rule and the supporting facts, you can always trace a conclusion to its inputs. This page discusses why that is structural rather than a logging mode, and how the three pieces fit together.