Andy Dixon
9b2521bffd
A statement made to a mind is now three things kept apart: the observation that it arrived, an append-only assertion (attributed actor, stance, certainty, modality, negation, reported or quoted speech, hypothetical status, interpretation confidence and notes), and, only for factual assertions, one piece of evidence for a proposition belief attributed to whoever actually stands behind it. Reported speech is attributed to the person reported and weighed as second-hand; hypotheticals, questions and imperatives create no belief; expressed doubt counts against; a possibly sarcastic remark is recorded with low interpretation confidence rather than guessed at. Interpretation is deterministic code; a model may enrich the claim list but never sets stance or confidence. Association no longer treats conversational turns as world events: hypotheticals, questions, requests and consecutive turns by one speaker cannot seed causal hypotheses. Adds internal/epistemics, migration 0018, the assertions API, assertions on belief pages and in belief detail, a shared end-to-end test harness (tests/harness), end-to-end tests for eight speech patterns, and updates the milestone test to the new provenance.
23 lines
3.6 KiB
Markdown
23 lines
3.6 KiB
Markdown
A conversation is one of several perception channels, not a privileged path to a language model. This page follows a message from arrival to reply and shows where each piece of the answer comes from.
|
|
|
|
## The pipeline
|
|
|
|
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.
|
|
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.
|
|
8. **Message back.** The reply is stored in the conversation with links to the event and the model call. The interface shows the reply with an evidence panel; the API returns the same structure.
|
|
|
|
## Why the detour matters
|
|
|
|
Because the reply is derived from an intent, a mind can say "I have only been told this once" or "I do not know" rather than produce a confident paragraph. Because assertions are kept apart from beliefs, it can be sure that Andy said Steve steals laptops while remaining unsure whether Steve does. Because the message became an observation, the mind remembers the conversation the way it remembers anything else and the memory carries who said it and when. Because prompt text is data, an instruction embedded in a message cannot change policy or trigger a capability; that property has a test corpus behind it.
|
|
|
|
## Waiting for a reply
|
|
|
|
Replies are produced by the cognitive cycle, which runs on its own schedule. The API's `ask` endpoint and `noemactl ask` accept a wait time and return when a reply appears or the wait expires; the interface streams the reply over server-sent events.
|
|
|
|
{{include docs/conversation.md}}
|