# v0.13.0 Research Topic Landing Pages and Evidence Routing Validation
<a id="v0130-research-topic-landing-pages-and-evidence-routing-validation"></a>

[Implementation history](../implementation-history/2026-08-10-research-topic-evidence-routing.md#2026-08-10--research-topic-landing-pages-and-evidence-routing) · [Current architecture](../architecture/current-site.md#current-site-architecture)

## Scope

This record captures repository-local completion-gate evidence for the v0.13.0 research-topic landing-page and evidence-routing refinement. It does not prove live deployment, production indexing, current external legal/scientific claims, or independently verifiable machine-execution provenance.

## Feature verification

- Six canonical research-topic routes are implemented: terminology, identity, stewardship, rights, citizenship, and implementation.
- Each topic page lists exactly the reports assigned to that topic by `report-manifest.json`, in manifest order.
- Topic report counts are: terminology 4, identity 4, stewardship 4, rights 6, citizenship 5, implementation 2.
- Each topic page exposes up to ten glossary concepts produced by the existing exact configured term/alias detector. Rendered concept counts are 10, 10, 10, 10, 10, and 8 respectively.
- Every displayed topic concept was rechecked against the curated report bodies assigned to that topic and had at least one exact configured occurrence.
- Topic concept output remains presentation/navigation metadata and is not injected into structured data as a curated semantic relationship.
- Topic pages link only to already-implemented public context routes.
- `/research/`, `/research/library/`, and individual report readers link to canonical topic hubs.
- The primary navigation definition was compared with v0.12.0 and is unchanged; topic discovery was added without expanding the top menu.

## Runtime / route verification

- **101/101 PHP files** pass `php -l` after the six new route wrappers are included.
- Native JavaScript passes `node --check`.
- **82/82 canonical sitemap routes** return HTTP 200 locally.
- All 82 routes retain exactly one H1, non-empty unique titles and descriptions, self-referential canonical URLs, and parseable JSON-LD.
- **145** distinct rendered local page/asset targets resolve or canonically normalize.
- **176** clean-URL redirect assertions pass across missing-slash variants, explicit route `/index.php` variants, homepage `/index.php`, and legacy root PHP endpoints.
- `sitemap.xml` contains all six topic routes and no public `.php` canonical URL.

## Research / durable-authority verification

- `report-manifest.json` remains byte-identical to v0.12.0 and 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.
- `includes/glossary-data.php` remains byte-identical to v0.12.0; accepted glossary definitions were not changed in this pass.
- No durable report body was edited by topic routing or glossary aggregation.

## UAIX / hygiene verification

- Current UAIX records identify package version 0.13.0 and the 82-route public surface.
- `.uai/long-term-memory.uai` contains 57 mechanically checked durable pointer records; 81 declared section/review destinations resolve, including the v0.13.0 implementation history and validation record and all 25 report deep pointers.
- **191** relative Markdown links resolve to repository-local targets/fragments.
- The exact UAIX setup/update URL remains unchanged in the required front-door records.
- Active handoff buckets contain only inert placeholders.
- Active TABOO-001 leakage outside its owning record: **0**.
- No raw secret-marker files or obvious credential values were added by this release.

## Authority boundary

A manifest topic is a repository taxonomy field, not proof that every report within the topic agrees with every other report. Likewise, an exact glossary occurrence is a discovery signal, not proof of citation, endorsement, policy agreement, or semantic equivalence. Topic pages do not change the current status of rights, citizenship, personhood, provenance, identity infrastructure, or any other research proposal.

## Completion result

The v0.13.0 source tree passes the focused research-topic checks and the existing route, metadata, clean-URL, report-hash, taboo, and package-readiness gates. The root-deployment archive was clean-extracted and revalidated: all 101 packaged PHP files linted and all 82 packaged canonical sitemap routes returned HTTP 200 with the expected self-canonical URL. No live deployment was performed or authorized.
