docs: lobes embedder as the reference deployment; scores are model-relative (#10, #11)

CHANGELOG.md

@@ -5,6 +5,26 @@ All notable changes to this project will be documented in this file.
 Format follows [Keep a Changelog](https://keepachangelog.com/). This project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.1] - 2026-07-06
+
+### Added
+
+- README "Reference deployment" note (Meaning Gradient section) and a matching
+  `coherence/meaning/embed.py` docstring addition: the lobes gateway serves an
+  `embedder` role, discoverable via `GET /capabilities` (lobes-cli >= 0.38
+  advertises a client-reachable endpoint per role); consumers such as
+  colleague resolve the endpoint from lobes and inject `COHERENCE_EMBED_URL` /
+  `COHERENCE_EMBED_MODEL` when armed. Also notes that each meaning score is a
+  model-relative, anchor-defined measurement — the embedding model and
+  anchors are the score's reference frame (gauge), never universal meaning
+  (issues #10, #11). Documentation only; no defaults, code behavior, or tests
+  changed.
+
+### Fixed
+
+- `uv.lock`'s recorded `coherence-cli` version was stale at `0.4.1` while
+  `pyproject.toml`/`CHANGELOG.md` had already moved to `0.5.0`; re-synced.
+
 ## [0.5.0] - 2026-07-04
 
 ### Added

README.md

@@ -85,6 +85,18 @@ environment error — an unreachable embedding endpoint makes `score` exit `2`
 with a hint naming `COHERENCE_EMBED_URL`, while the offline diagnostics still
 run.
 
+### Reference deployment
+
+The lobes gateway serves an `embedder` role, discoverable via `GET /capabilities`
+(lobes-cli >= 0.38 advertises a client-reachable endpoint per role). Consumers
+such as colleague resolve the endpoint from lobes and inject
+`COHERENCE_EMBED_URL` / `COHERENCE_EMBED_MODEL` when armed.
+
+Each meaning score is a model-relative, anchor-defined measurement: the
+embedding model and anchors constitute the score's reference frame (gauge).
+Scores are not universal meaning — they are semantic measurements relative to the
+chosen model and anchor set (issues #10, #11).
+
 `coherence meaning score <file> --json` emits exactly:
 
 ```json

coherence/meaning/embed.py

@@ -15,6 +15,16 @@
 Transport failures (connect/timeout/transport) are wrapped in
 :class:`~coherence.meaning.EmbedUnavailable` with an actionable message that
 names both environment variables; raw ``httpx`` errors never escape.
+
+Reference deployment: the lobes gateway serves an ``embedder`` role, discoverable
+via ``GET /capabilities`` (lobes-cli >= 0.38 advertises a client-reachable endpoint
+per role). Consumers such as colleague resolve the endpoint from lobes and inject
+``COHERENCE_EMBED_URL`` / ``COHERENCE_EMBED_MODEL`` when armed.
+
+Each meaning score is a model-relative, anchor-defined measurement: the embedding
+model and anchors constitute the score's reference frame (gauge). Scores are not
+universal meaning — they are semantic measurements relative to the chosen model
+and anchor set (issues #10, #11).
 """
 
 from __future__ import annotations

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "coherence-cli"
-version = "0.5.0"
+version = "0.5.1"
 description = "Maintains information quality for agentic workflows — assesses the freshness, provenance, fidelity, and task-specific validity of claims, then refreshes or repairs degraded ones before agents consume them."
 readme = "README.md"
 license = "Apache-2.0"