Skip to content

docs: enrich Tech stack table and align README with code state - #6

Merged
adel-saoud merged 1 commit into
mainfrom
feat/readme-stack-explainer
Jun 17, 2026
Merged

docs: enrich Tech stack table and align README with code state#6
adel-saoud merged 1 commit into
mainfrom
feat/readme-stack-explainer

Conversation

@adel-saoud

@adel-saoud adel-saoud commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Summary

  • README Tech stack table: Role column becomes What it does. Niche libraries (GLiNER, DeBERTa zero-shot, BM25, hierarchical chunking) get one sentence that explains what they are and the differentiator. Universal tools stay terse.
  • Fix the literal <measured> placeholder that scripts/eval.py was printing and the README was quoting. Now both say N/A (informational, requires Ollama).
  • Coverage badge corrected to 93%.
  • X-Guardian-Faithfulness: header annotated as reserved / on the roadmap.
  • Companion-projects framing reworked as cost / quality / privacy axes in both the README and AGENTS.md.
  • AGENTS.md pyright-excluded list now includes retrieval/_real_backends.py for completeness.
  • context/architecture.md module map gets the matching row, and the test count / coverage line is brought up to date.

Test plan

  • uv run ruff check . clean
  • uv run pyright 0 errors / 0 warnings
  • uv run pytest 130 passed, 93.31% coverage
  • uv run python scripts/eval.py --with-gliner output matches the README block verbatim
  • CI green on the PR

The README's Tech stack table treated GLiNER and DeBERTa zero-shot the
same way as FastAPI and ruff: a one-line role tag. Reviewers from
non-ML backgrounds (and ML folks who haven't tracked span-based NER)
will skim past names they do not recognise. While in the area, a few
other stale facts needed catching up.

README:
- Replace the Tech stack `Role` column with `What it does`. Niche items
  (GLiNER, DeBERTa, BM25, hierarchical chunking) get one sentence that
  explains what they are and the differentiator. Universal tools stay
  terse. Presidio is explicitly identified as Microsoft's.
- Coverage badge 92% -> 93% to match the project number.
- Faithfulness placeholder: replace the literal `<measured>` token with
  `N/A (informational, requires Ollama)` in both the README expected
  output and the matching `scripts/eval.py` print line. Same change in
  the response-headers example for `X-Guardian-Faithfulness`, which is
  annotated as roadmap.
- Companion-projects framing: surface the three axes (cost, quality,
  privacy) as a bullet list.

AGENTS.md:
- Mirror the README's companion-projects framing.
- Add `retrieval/_real_backends.py` to the pyright-excluded list. It
  was added during the retrieval PR but the agent doc still listed only
  `pii/_real_backends.py` and `dashboard/app.py`.

context/architecture.md:
- Add `guardian_rag/retrieval/_real_backends.py` to the module map next
  to the pii one.
- Test count and coverage: 125 -> 130 tests, ~92% -> ~93%.
@adel-saoud adel-saoud self-assigned this Jun 17, 2026
@adel-saoud
adel-saoud merged commit 96de194 into main Jun 17, 2026
1 check passed
@adel-saoud adel-saoud changed the title docs: align README, AGENTS.md, and architecture.md after the build docs: enrich Tech stack table and align README with code state Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant