andy/noema
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
docs/site/pages/conversation.md
+1 -1
View File
@@ -5,7 +5,7 @@ A conversation is one of several perception channels, not a privileged path to a
1. **Message.** A person posts a message in a conversation (the interface, `noemactl ask`, or the API). It is stored with the conversation, the actor and a link to the event it becomes.
2. **Observation.** The message is appended as an `observation` event with `trust=user`, the conversation as its channel and the message text as data. It now enters the mind's history like anything else it perceives.
3. **Perception.** The perceive process analyses the observation deterministically: sentences, entities, claims, questions, requests, dates, sentiment words. If a model is configured for the `perceive` role and the cycle budget allows, the analysis is enriched with a structured JSON result; the model's output is validated against a schema and any capability-like or policy-like language in it is flagged rather than obeyed.
4. **Assertion.** Each claim in the message is interpreted deterministically into an assertion: who is attributed (the speaker, or the person they quote or report), their stance, how firmly they put it, whether it is hypothetical, reported, quoted or negated, and how confidently the reading itself holds. The assertion is recorded whatever happens next.
4. **Assertion.** Each claim in the message is interpreted deterministically into an assertion: who is attributed (the speaker, or the person they quote or report), their stance, how firmly they put it, whether it is hypothetical, reported, quoted or negated, and how confidently the reading itself holds. The assertion is recorded whatever happens next, is listed per mind and per actor through the API, and appears on the page of any belief it became evidence for. No model takes part in the reading.
5. **Cognition.** The perception competes for the workspace. Retrieval recalls related memories; only factual assertions feed a proposition belief, as one piece of evidence attributed to whoever stands behind it; hypotheticals and questions create none; expressed doubt counts against. Contradictions are detected; goals and predictions may follow.
6. **Intent.** If the message asks something or expects a reply, the executive builds a **response intent** from real state: what was asked, which beliefs answer it with what confidence, what the mind does not know, which memories are relevant, and what the personality says about tone. Introspective questions ("what do you believe about X", "what can you do", "why did you say that") are answered from beliefs, the self-model and events, never invented.
7. **Language.** The intent is rendered deterministically from templates, or, when a model is configured for the `respond` role, sent to the model with the intent as the thing it must stay grounded in. The reply is a `response_generated` event with its evidence references and the model call, if any.