open/portfolio-optimiser-commons
1
0
Fork 0
Code Issues Releases Activity

docs(plan): guard adoption plan pins no version — v0.2 header was stale

Browse source 
The plan header named 'v0.2 alpha' as reportage of the ecosystem, not as a
choice. llm-ingestion-guard has since cut v0.3.0, and consumers now disagree
on pinning: the guard recommends v0.3.0, llm-ingestion-okf deliberately holds
>=0.2,<0.3 because the new active:* findings could quarantine ordinary
documents under its Door B preset.

Commons has no wiring, no tests and no dependency declaration, so it pins
nothing. Naming no version is more accurate than trading one stale number
for another. §3.2:90-91 already prescribed allow_reserved=True for a whole
received bundle, which is what v0.3.0 made the default.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XYkLsRfSBBUjULS219Fy8X
This commit is contained in:
Kjell Tore Guttormsen 2026-07-25 15:06:07 +02:00
commit 381d9e5399
1 changed files with 2 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/plan/2026-07-16-llm-ingestion-guard-adoption.md
View file

@ -1,7 +1,8 @@
# Adoption plan — `llm-ingestion-guard` at the ingest persist gate
> **Status:** plan only. This document decides *when* and *where* the write-time
> ingestion guard (`llm-ingestion-guard`, v0.2 alpha) earns its place in the
> ingestion guard (`llm-ingestion-guard`, alpha — this plan pins no version; see
> §3.2 for the `allow_reserved` default, which the guard changed in v0.3.0) earns its place in the
> architecture this commons specifies. **It does NOT wire the guard in** — the
> executable wiring lands in the two reference implementations; this document is
> the framework-neutral contract they build to, same as [method-spec.md](../../method-spec.md)