linkedparticles-core 1.132.1__tar.gz

linkedparticles_core-1.132.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

linkedparticles_core-1.132.1/NOTICE

@@ -0,0 +1,18 @@
+Particles
+Copyright 2026 The Particles authors
+
+This product includes software developed by the Particles project
+(https://github.com/LinkedParticles/particles-core-py).
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file.
+
+"Particles" is the name of this project and standard. The name and any
+conformance claims ("Particles-compatible", "conforms to the Particles
+standard") are reserved by the project and are not granted by the code
+license above. Use of the code is permitted under Apache-2.0; use of the
+name to describe a derivative or competing product is not.
+
+The standard's prose — the documents under docs/spec/ (whitepaper,
+technical specification) — is licensed under Creative Commons
+Attribution 4.0 International (CC-BY-4.0), not Apache-2.0. See
+docs/spec/LICENSE.

linkedparticles_core-1.132.1/PKG-INFO

@@ -0,0 +1,94 @@
+Metadata-Version: 2.5
+Name: linkedparticles-core
+Version: 1.132.1
+Summary: Client layer of the Particles reference implementation — store-free schema, extraction, and interchange
+Project-URL: Homepage, https://github.com/LinkedParticles/particles-core-py
+Project-URL: Repository, https://github.com/LinkedParticles/particles-core-py
+Project-URL: Issues, https://github.com/LinkedParticles/particles-core-py/issues
+Author: The Particles authors
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agents,beliefs,citations,epistemic,knowledge-graph,knowledge-management,llm,provenance,psum,rag,uncertainty
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: anthropic>=0.28
+Requires-Dist: html2text>=2024.2
+Requires-Dist: httpx>=0.27
+Requires-Dist: jsonschema>=4.22
+Requires-Dist: lxml-stubs>=0.5.1
+Requires-Dist: numpy>=1.26
+Requires-Dist: opentelemetry-api>=1.27
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyld<4,>=2.0
+Requires-Dist: pypdf>=6.15.0
+Requires-Dist: pyshacl<0.32,>=0.26
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rdflib<8,>=7.0
+Requires-Dist: scipy>=1.13
+Requires-Dist: sentence-transformers>=2.7
+Requires-Dist: sqlalchemy>=2.0
+Requires-Dist: torch
+Provides-Extra: vision
+Requires-Dist: pypdfium2>=4.30; extra == 'vision'
+Description-Content-Type: text/markdown
+
+# linkedparticles-core
+
+> **Particles is shared memory for humans and AI agents.** Each particle is one
+> claim, plus what you need to judge it: who said it, where, when, and how
+> confident they were. Facts, opinions, and memories are all claims, recorded
+> the same way as particles. Particles are not edited or deleted. Particles are
+> superseded, retracted, or disputed in the open. How much to trust it is a
+> perspective applied at query time, never baked into the record.
+
+The store-free **Client layer** of the Particles reference implementation — the
+substrate for defining, validating, serializing, and producing candidate
+particles without a graph or a store. This package holds the pieces that never
+touch persistent state:
+
+- the schema models and their invariants (immutable confidence, the status
+  machine, the Core/Extension split);
+- the extraction layer that turns source bytes into candidate particles with
+  unresolved subject names;
+- confidence math, the completion-provider port, embeddings, conformance
+  validation, and the pure interchange codec.
+
+Holding or reasoning over accumulated state — reconciliation, subject
+resolution, querying, linting — lives in the **engine** package
+(`linkedparticles`), which depends on this one.
+
+## Install
+
+```bash
+pip install linkedparticles-core
+```
+
+## The three repositories
+
+| Repo | What it is |
+|---|---|
+| [`particles-standard`](https://github.com/LinkedParticles/particles-standard) | The standard: whitepaper, technical specification, normative schema + SHACL artifacts, conformance fixtures |
+| [`particles-core-py`](https://github.com/LinkedParticles/particles-core-py) | **This repo** — the Python Client layer (`linkedparticles-core`) |
+| [`particles-engine-py`](https://github.com/LinkedParticles/particles-engine-py) | The Python Engine layer + surfaces (`linkedparticles`) |
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) and [ARCHITECTURE.md](ARCHITECTURE.md).
+Contributions are accepted under a Developer Certificate of Origin sign-off —
+there is no CLA.

linkedparticles_core-1.132.1/README.md

@@ -0,0 +1,48 @@
+# linkedparticles-core
+
+> **Particles is shared memory for humans and AI agents.** Each particle is one
+> claim, plus what you need to judge it: who said it, where, when, and how
+> confident they were. Facts, opinions, and memories are all claims, recorded
+> the same way as particles. Particles are not edited or deleted. Particles are
+> superseded, retracted, or disputed in the open. How much to trust it is a
+> perspective applied at query time, never baked into the record.
+
+The store-free **Client layer** of the Particles reference implementation — the
+substrate for defining, validating, serializing, and producing candidate
+particles without a graph or a store. This package holds the pieces that never
+touch persistent state:
+
+- the schema models and their invariants (immutable confidence, the status
+  machine, the Core/Extension split);
+- the extraction layer that turns source bytes into candidate particles with
+  unresolved subject names;
+- confidence math, the completion-provider port, embeddings, conformance
+  validation, and the pure interchange codec.
+
+Holding or reasoning over accumulated state — reconciliation, subject
+resolution, querying, linting — lives in the **engine** package
+(`linkedparticles`), which depends on this one.
+
+## Install
+
+```bash
+pip install linkedparticles-core
+```
+
+## The three repositories
+
+| Repo | What it is |
+|---|---|
+| [`particles-standard`](https://github.com/LinkedParticles/particles-standard) | The standard: whitepaper, technical specification, normative schema + SHACL artifacts, conformance fixtures |
+| [`particles-core-py`](https://github.com/LinkedParticles/particles-core-py) | **This repo** — the Python Client layer (`linkedparticles-core`) |
+| [`particles-engine-py`](https://github.com/LinkedParticles/particles-engine-py) | The Python Engine layer + surfaces (`linkedparticles`) |
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) and [ARCHITECTURE.md](ARCHITECTURE.md).
+Contributions are accepted under a Developer Certificate of Origin sign-off —
+there is no CLA.

linkedparticles_core-1.132.1/artifacts/conformance/README.md

@@ -0,0 +1,171 @@
+# Particles conformance artifacts
+
+This directory holds the **behavioural / quantitative** conformance surface of
+the Particles standard — the ground truth a second implementation must match to
+reproduce our numbers and decisions, complementing the **structural** artifacts
+under `artifacts/schemas/` (JSON Schema, JSON-LD `@context`, SHACL shapes).
+
+| File | Role | Governing ADR |
+|---|---|---|
+| `profile.yaml` | The **Conformance Profile** companion: constants, formulas, decay table, float tolerance, embedding profile, and deterministic test vectors. The single machine-readable source of truth for `docs/spec/conformance-profile.md`. | Profile |
+| `similarity_vectors.json` | The frozen **embedding-similarity** test-vector set (band + top-k membership cases) — the portability instrument for the similarity substrate. | Profile |
+
+The reference SDK self-certifies against both with `particles conformance check`
+(L2 over `profile.yaml`'s vectors; L3 over `similarity_vectors.json`).
+
+---
+
+## `profile.yaml` — the Conformance Profile companion
+
+Mirrors `docs/spec/conformance-profile.md`:
+
+- **Constants** (§2) mostly carry a `config_path` — the dotted attribute on the
+  SDK's `get_config()` they restate. A drift-guard test
+  (`tests/test_conformance_profile.py`) asserts every published `value` still
+  equals the live default at that path, so the artifact never silently lags
+  `particles/config.py`. A few are **code-level** (`config_path: null`) — module
+  constants rather than config knobs, notably the §2.6 / §13.3 benchmark
+  match-semantics constants; those are drift-checked against the live
+  code default directly rather than via `config_path`.
+- **Formulas** (§4) — `effective_confidence`, `recency_factor`, the calibration
+  apply transform, and the §6.9 noisy-OR co-evidential merge.
+- **`embedding_profile`** — the reference `{model, dim, normalization}`, and a
+  `similarity_vectors_ref` pointer to the file below.
+- **`test_vectors`** — the canonical input → expected cases the L2 runner
+  recomputes, covering both the §4 formulas and the §5 deterministic algorithms.
+
+`profile_version` carries the artifact's own stamp; bump it when a default is
+re-tuned. The loader/validator is `particles/conformance/profile.py`; the runner
+is `particles/conformance/runner.py`.
+
+### The `test_vectors` block
+
+Seven families, in two kinds. The **numeric** families are the §4 formulas and
+conform within `float_tolerance` (`1e-9` absolute); the **categorical** families
+are the §5 algorithms, whose outputs are a verdict, a digest, a boolean and a
+count — those must match *exactly*, since there is nothing to round.
+
+| Family | Pins | Comparison |
+|---|---|---|
+| `effective_confidence` | §4 read-time product, incl. the `> 1.0` clamp | `float_tolerance` |
+| `recency_factor` | §2.3 decay, incl. the floor and the `age ≤ 0` case | `float_tolerance` |
+| `calibration_apply` | §4 `clamp(raw/T, 0, 1)`, incl. `T < 1` saturation | `float_tolerance` |
+| `noisy_or_merge` | §6.9 co-evidential merge with the `1/k` within-source discount | `float_tolerance` |
+| `conflict_ladder` | §6.4 **rung ordering** | exact |
+| `context_fingerprint` | §16.1 procedure | exact |
+| `cascade_gate` / `cascade_cap` | §15.1 policy gate (N ≥ 3) and per-run cap | exact |
+
+**Every vector input is plain data** — scalars, strings, and flat records, never
+a serialized SDK object. That is the portability contract: the ladder and
+fingerprint families take *structured* inputs, so each one publishes only the
+fields the algorithm actually reads, and a second implementation materialises
+its own types from them.
+
+- `conflict_ladder` carries two particle stubs of exactly two fields —
+  `assertion_modality` (the §1.7 truth-apt gate; truth-apt iff `FALSIFIABLE`)
+  and `uncertainty_nature` (the §1 `ALEATORY` exclusion) — plus the
+  caller-resolved inputs (the replacement signal, the two supersession
+  directions, both trust scores, the differential threshold, and whether the
+  store has a single trust order). Omitted keys take the documented defaults.
+  Because the family is about *ordering*, the vectors deliberately set up rungs
+  to compete: an `ALEATORY` pair with both a supersession edge and a decisive
+  trust gap must still come out `INCONSISTENT`.
+- `context_fingerprint` carries `(id, status)` rows rather than a bare id list,
+  so all three steps are pinned: the ACTIVE-only filter (step 1), the
+  lexicographic sort (step 2 — one vector supplies its ids out of order), and
+  the delimiter-free SHA-256 (step 3). The ids are fixed literals; the expected
+  digest is a function of those exact strings, so they must be ported verbatim.
+
+Boundary vectors state inclusive comparisons (`N ≥ 3`, `|Δ| ≥ threshold`, a
+batch exactly at the cap). Where such a boundary would otherwise hinge on
+decimal-to-binary rounding, the vector overrides the input to exactly
+representable values and says so in a comment — the case is about the
+comparison operator, not about float representation.
+
+---
+
+## `similarity_vectors.json` — embedding-similarity vectors
+
+The frozen test-vector set that is the portability instrument for the standard's
+similarity substrate. It is the concrete, language-agnostic answer to "does a
+second implementation reproduce our similarity behaviour?" — the question
+this Profile makes answerable.
+
+### What is pinned
+
+Per the technical specification (§8.5, *Embedding & Similarity Contract*):
+
+- **Similarity** is **cosine over L2-normalized embedding vectors, clamped to
+  `[0, 1]`** (negatives → 0). Every similarity threshold in the standard is
+  expressed on this normalized scale.
+- An implementation records a structured **`embedding_profile = {model, dim,
+  normalization}`** in store metadata. A profile change requires re-embedding.
+- The **reference profile** is
+  `{model: all-MiniLM-L6-v2, dim: 384, normalization: l2}` — declared in the
+  `profile` block of `similarity_vectors.json`.
+
+### File format
+
+```jsonc
+{
+  "profile":  { "model": "...", "dim": 384, "normalization": "l2" },
+  "pairs": [
+    { "id": "equiv-01", "category": "clear-equivalent",
+      "text_a": "...", "text_b": "...", "band": [lo, hi] }
+  ],
+  "topk": [
+    { "id": "topk-01", "query": "...",
+      "corpus": [ { "id": "c1", "text": "..." }, ... ],
+      "k": 2, "expected_topk": ["c1", "c3"] }
+  ]
+}
+```
+
+### Bands are the conformance semantics
+
+Each `pairs` entry declares a closed band `[lo, hi]`. A backend is
+**profile-conformant** on that vector when, embedding `text_a` and `text_b`
+under the declared profile and applying the pinned metric, the resulting
+similarity lands in `[lo, hi]` **inclusive**.
+
+Bands — **not** an `|Δ| ≤ ε` tolerance against a recorded float — are the
+contract (resolved open question 2). They are chosen to *comfortably
+bracket* the reference model's score with margin on both sides, so the band is a
+real cross-implementation contract rather than an overfit to one backend's
+floating-point output. A different conformant encoder may legitimately score
+anywhere inside the band.
+
+The `category` field is descriptive only (it documents what each pair probes:
+`clear-equivalent`, `clear-unrelated`, `near-threshold`, `cross-domain`); the
+band is what is asserted.
+
+### Top-k cases are membership, not ordering
+
+Each `topk` entry asserts that, ranking `corpus` by similarity to `query`, the
+top `k` results **contain** every id in `expected_topk` (set membership, ⊇).
+This is the deliberately weaker guarantee that layer 4 establishes: exact
+top-k *ordering* across profiles is implementation-defined and **non-normative**.
+The cases pin the strong, reproducible part (the clearly-relevant documents make
+the cut) without over-claiming a total order.
+
+### Running the vectors as a conformance check
+
+The reference SDK exercises this file in
+`tests/test_conformance_similarity_vectors.py` (marked
+`@pytest.mark.integration`, since it needs the real embedding model) and via the
+L3 path of `particles conformance check`. Both load the JSON, encode every pair
+with the reference encoder, and assert each score falls in its band and each
+top-k membership holds. A second implementation runs the equivalent check in its
+own language against this same frozen file.
+
+---
+
+## Maintenance
+
+Both files are **frozen** contracts. Changing a band, a constant, a formula, or
+the reference profile alters the conformance contract — it rides an ADR or an
+explicit spec revision, never a silent edit. When a config default is re-tuned,
+update `profile.yaml`'s matching constant in the same change (the drift-guard
+test enforces this). When the *reference embedding profile* changes, re-author
+the `similarity_vectors.json` bands against the new model and update its
+`profile` block in the same change.