# v0.12.0 Bidirectional Glossary-to-Research Validation
<a id="v0120-bidirectional-glossary-to-research-validation"></a>

[Implementation history](../implementation-history/2026-08-10-bidirectional-glossary-research-discovery.md#2026-08-10--bidirectional-glossary-to-research-discovery) · [Current architecture](../architecture/current-site.md#current-site-architecture)

## Scope

This record captures repository-local completion-gate evidence for the v0.12.0 bidirectional glossary/research discovery refinement. It does not prove live deployment, production indexing, legal status, external scientific/legal claims, or independently verifiable machine-execution provenance.

## Feature verification

- All 20 glossary term pages render a visible **Research using this concept** module.
- All 20 glossary concepts have at least one exact configured term/alias occurrence in the 25-report curated corpus.
- The 20 term pages render **112** bounded research backlinks in total; no term page renders more than six.
- Every rendered backlink equals the deterministic ranking produced by the shared detector: exact occurrence count descending, then report title.
- Every rendered backlink was rechecked against the target curated report body and had a positive exact configured match count.
- `/glossary/` renders corpus-coverage summary text plus report/mention counts for all 20 glossary cards.
- The reciprocal report-reader **Concepts in this report** bridge remains present on all 25 report pages.
- `glossary_terms()` output was compared with v0.11.0 and is unchanged; accepted glossary definitions were not altered by this pass.
- No report body changed: all 25 curated SHA-256 values still match the manifest.
- Detector output remains absent from `DefinedTerm` structured data as a purported curated semantic relationship.

## Runtime / route verification

- **95/95 PHP files** pass `php -l`.
- Native JavaScript passes `node --check`.
- **76/76 canonical sitemap routes** return HTTP 200 locally.
- All 76 routes retain exactly one H1, non-empty unique titles and descriptions, self-referential canonical URLs, and parseable JSON-LD.
- **136** distinct rendered local page/asset targets resolve or normalize successfully.
- **165** clean-URL redirect assertions passed across missing-slash variants, explicit route `/index.php` variants, homepage `/index.php`, and legacy root PHP endpoints.
- Public route count and sitemap canonical set remain unchanged from v0.11.0.

## Research / durable-memory verification

- `report-manifest.json` contains exactly **25** supplied-report records.
- **25/25 original source attachment hashes** match the identities recorded in the manifest.
- **25/25 curated report hashes** match durable file bytes.
- Every supplied report retains stable `#curation-boundary` and `#research-body` destinations.
- **187** relative Markdown links were resolved.
- **199** mechanically checkable UAIX/repository path references were resolved.
- The exact wizard update URL remains unchanged in the required front-door/handoff records.
- Active handoff buckets contain only inert placeholders.

## Taboo / credential hygiene

- Active TABOO-001 leakage outside its owning record: **0**.
- No raw secret-marker files were detected by the completion scan.
- The curated report corpus was not rewritten in this release, so the accepted curation/language boundary from prior releases remains intact and hash-verifiable.

## Authority boundary

The exact-match bridge is a discovery tool. A lexical occurrence does not prove that a report endorses a concept, cites the glossary, agrees with the site's preferred terminology, or uses the term in precisely the same sense as the glossary definition. The detector does not modify research bodies, glossary definitions, or legal/scientific truth status.

## Completion result

The versioned root archive was clean-extracted and revalidated. The packaged copy retained 95 lint-clean PHP files, all 76 canonical routes, all 25 curated report hashes, all 20 glossary coverage entries, the reciprocal glossary/research modules, representative clean redirects, root-level archive shape, and zero active TABOO-001 leakage outside its owning record. No live deployment was performed or authorized.