From a3fa16ef74a3a3c9aec98ec62d44623c6270a760 Mon Sep 17 00:00:00 2001 From: thrialectics <203729272+thrialectics@users.noreply.github.com> Date: Tue, 12 May 2026 16:48:03 -0400 Subject: [PATCH] docs(readme): drop self-referential "observations" in Conclusions bullet The Conclusions definition shouldn't define itself in terms of "observations." Per Plastic's positioning, "conclusions" is the documentation-facing name for what the Deriver produces; "observations" remains the internal code symbol. The README's two remaining "observations" references (inside the
Internal storage block and the Storage primitives block) are explicit code-internal framing and stay. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d32f4f48..94abe792 100644 --- a/README.md +++ b/README.md @@ -199,7 +199,7 @@ Honcho organises everything around **peers** — humans and AI agents alike are What you query out of Honcho: -- **Conclusions** — observations Honcho has extracted about a peer (deductive and inductive). Exposed via the [conclusions API](https://docs.honcho.dev/v3/api-reference/introduction). +- **Conclusions** — what Honcho has extracted about a peer (deductive and inductive). Exposed via the [conclusions API](https://docs.honcho.dev/v3/api-reference/introduction). - **Representations** — static, low-latency snapshots of what Honcho knows about a peer (optionally session-scoped). - **Peer Cards** — compact identity summaries. - **Session context / summaries** — prompt-ready bundles for long-running conversations.