open/llm-ingestion-pipeline-security
1
0
Fork 0
Code Issues Releases 4 Activity

docs(readme): lead with write-time trust-boundary; feature shipped OKF adapter

Browse source 
Rewrite the README value proposition to make the necessity land on mechanism,
not adjectives: write-time ingestion is the trust boundary query-time guardrails
structurally cannot see; an OKF/LLM-wiki has no format-level authenticity, so the
ingestion pipeline IS the trust boundary. Add a first-class 'OKF / LLM-wiki
support (shipped)' section for import_bundle mode-b (per-concept gates). Fix stale
test badge (357 -> 522) and drop the brittle module count. Tighten prose; retain
all honest-limitations items (a shipped control). Every symbol/preset/command
verified against v0.2 code.
This commit is contained in:
Kjell Tore Guttormsen 2026-07-15 18:58:21 +02:00
commit d73cfc882f
2 changed files with 160 additions and 117 deletions
Download patch file Download diff file Expand all files Collapse all files

12
CHANGELOG.md
View file

@ -26,6 +26,18 @@ not. Two consumers of the same source of truth:
This is the real-case validation gate ahead of a v1.0 freeze.
### Documentation — consumer adoption + README value proposition
- `docs/ADOPTION-BRIEF.md` — a self-contained brief a consumer repo (OKF
second-brain / LLM wiki) can plan an inclusion from: the write-time trust-boundary
argument, the two bookends + 8-step contract, the shipped OKF adapter
(`import_bundle` mode-b), how to verify (coverage matrix), how to depend
(stdlib-only core), and a checklist for *when/where* to wire it.
- README rewritten to lead with the write-time trust-boundary framing, add a
first-class **OKF / LLM-wiki support (shipped)** section for `import_bundle`, and
correct the test badge (357 → 522). Every claim verified against the code; all
honest-limitations items retained.
## [0.2.0] — 2026-07-06
### Added — OKF adapter (stream 1)