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 <details> Internal storage block and the Storage primitives block) are explicit code-internal framing and stay.
This commit is contained in:
parent
65d807626b
commit
a3fa16ef74
|
|
@ -199,7 +199,7 @@ Honcho organises everything around **peers** — humans and AI agents alike are
|
||||||
|
|
||||||
What you query out of Honcho:
|
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).
|
- **Representations** — static, low-latency snapshots of what Honcho knows about a peer (optionally session-scoped).
|
||||||
- **Peer Cards** — compact identity summaries.
|
- **Peer Cards** — compact identity summaries.
|
||||||
- **Session context / summaries** — prompt-ready bundles for long-running conversations.
|
- **Session context / summaries** — prompt-ready bundles for long-running conversations.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue