docs(site): document the review pass on the published site

Two new chapters (epistemic honesty, privacy) and updates across
concepts, beliefs, conversation, cognition, graph, replay, providers,
security, decisions, development, glossary, API, interface tour and the
landing page. Rebuilt into dixon.cx (website commit d541bc9).
This commit is contained in:
Andy Dixon
2026-08-29 20:02:09 +01:00
parent d63404b358
commit 0840a6c00a
17 changed files with 157 additions and 36 deletions
+1 -1
View File
@@ -6,7 +6,7 @@ An entity has a kind (person, system, service, host, project, organisation, plac
## Relationships
Edges are typed (works_on, owns, runs_on, part_of, depends_on, talks_about, located_in and others), weighted by how often and how credibly they were observed, and each carries evidence references to events. Co-occurrence within one observation creates weak edges; repeated co-occurrence strengthens them; an explicit statement ("db-primary is the new name for server-3") creates a strong one.
Edges carry a relation from one shared vocabulary, a confidence and evidence references to events, and are weighted by how often and how credibly they were observed. The vocabulary keeps association and causation apart. `co_occurs_with` and `temporally_precedes` record what was seen together or in order; co-mention within one observation writes nothing stronger. `possibly_caused_by` is a hypothesis: the association process proposes it for notable events close in time, always as a hypothesis belief with the alternatives "coincidence" and "a third factor caused both", and a prediction that the effect should recur. `caused_by` is reserved for established causes stated by an operator or recorded as a correction; nothing automatic writes it. `asserted_by` links a proposition to the person who put it forward. An explicit statement ("db-primary is the new name for server-3") still creates a strong edge of the kind it states.
## Corrections