codex/session 20260719 retrieval docs

[ryanportfolio]

Change identity

• Change ID: TN-CHG-2026-145
• Change type: normal
• Author: @ryanportfolio
• Target release/commit: 853b449b62b264a278799c3e55f547ae7395e8b7
• Target environment: GitHub repository main branch; no application runtime deployment
• Significant change: no
• Significant-change rationale: Terminology and maintainer-documentation correction only; no retrieval SQL, scoring, authorization, data handling, or PCI scope changes.

Purpose and scope

• Purpose: Correct false BM25 terminology so documentation and private names accurately describe the existing PostgreSQL full-text retrieval implementation.
• Affected components and data boundaries: CLAUDE.md, retrieval/ingestion/secrets references, and comments/private identifiers in retrieval, ingestion, generation, and eval code. No provider, database object, setting, request path, or data boundary changed.

Security and PCI impact

• CDE impact: none
• CDE-impact rationale: No runtime behavior, segmentation, authentication, authorization, storage, logging, or sensitive-data flow changed.
• Security impact and threat considered: Reviewed program scoping, classification filtering, citation/refusal behavior, provider boundaries, audit behavior, and sensitive-data handling; all remain unchanged because the patch is documentation and private-symbol terminology only.

PCI DSS 6.5 change controls

• 6.5.1 bespoke/custom security testing: not applicable
• 6.5.1 evidence or rationale: No bespoke/custom software behavior changed; repository-wide terminology audit, adversarial verification, and diff validation confirmed a non-functional patch.
• 6.5.2 completion revalidation: not applicable
• 6.5.2 evidence owner and plan/result: @ryanportfolio; no PCI requirement implementation was completed or modified by this documentation-only change.
• 6.5.3 pre-production separation: confirmed
• 6.5.3 evidence or rationale: Change was developed on isolated branch codex/session-20260719-retrieval-docs and submitted through PR #145 before main integration.
• 6.5.4 role/function separation: confirmed
• 6.5.4 evidence or accountability rationale: Authoring occurred through the session branch; GitHub required checks and the PR change record remain the independent merge controls, with release decision pending until checks pass.
• 6.5.5 live PAN in pre-production: no live PAN
• 6.5.5 evidence or rationale: No runtime, database, fixture, customer, payment-card, or other production data was accessed or introduced.
• 6.5.6 test data/accounts removal: not applicable
• 6.5.6 evidence owner and plan/result: No test data or accounts were created.

Verification

• Commands and results: Repository-wide BM25/IDF implementation audit completed; old private identifiers absent; git diff --check passed; two independent audits plus a fresh adversarial verifier confirmed the corrections.
• Negative/security tests: No security behavior changed. Secret scan, dependency audit/SBOM, and CodeQL checks passed on PR #145.
• Runtime/integration verification: Static checks passed. Local TypeScript check unavailable because this worktree has no node_modules; GitHub CI typecheck/build/tests will rerun after this record update.
• Evidence not collected locally: GitHub Actions owner: @ryanportfolio; target: PR #145; expected result: Typecheck, build, tests passes; evidence: PR #145 required-check receipt.

Vulnerabilities and dependencies

• Dependency/SBOM impact: None; no dependency or lockfile changes. PR #145 dependency audit and SBOM check passed.
• Finding/exception links: None: no vulnerability finding or exception was created by this non-functional correction.

Deployment and secure recovery

• Deployment/configuration/DDL steps: Merge PR #145 through protected GitHub main workflow after required checks pass; no configuration, dependency, migration, DDL, or application deployment step.
• Post-deployment verification: Owner @ryanportfolio verifies main contains commit 853b449b62b264a278799c3e55f547ae7395e8b7 through the PR merge receipt.
• Failure signal: Any required GitHub check failure or non-mergeable PR state blocks integration.
• Secure recovery procedure: Revert the merge commit through a reviewed pull request if terminology or private-name changes cause an unexpected issue.
• Incident ID: Not applicable: normal change
• Emergency authority: Not applicable: normal change
• Retrospective review due: Not applicable: normal change

Approval and closure

• Non-author reviewer: Unassigned: documentation-only change pending required checks and change-authority closure
• Review evidence: Pending: PR #145 checks and merge receipt
• Specialist approval: Not applicable: no security control, PCI scope, dependency, schema, or runtime behavior changed.
• Release/change-authority decision: pending