WP-DIG-NOM-02 · Sourced name-origin articles and site-wide wiki links
The Project Office › Master programme plan › WP-DIG-NOM-01 › WP-DIG-NOM-02
WP-DIG-NOM-02 · Sourced name-origin articles and site-wide wiki links
- Change ID CR-DIG-2026-10-31-01
- Product PROD-DIG-NOM-02 — Cedwyn Nomenclature Wiki Layer
- Control model PRINCE2 7, tailored · cross-cutting work package
- Raised 31 October 2026
- Status AMBER In progress; live acceptance open
- Budget tolerance £0 external spend
Extend Cedwyn’s source-aware name register into a connected encyclopaedia. Important names and concepts should lead to dedicated pages explaining their meanings, histories, usages and source trails. Each page must distinguish recorded forms from scholarly hypotheses, later folk explanations and unresolved search spellings. A shared lexicon and predictable linking rules make the pages discoverable across Cedwyn rather than leaving isolated lists.
Programme boundary: this is a cross-cutting product/work package, not a fifth project. It supports existing research and evidence products and does not change the programme structure, title/ownership positions or any legal gate.
Product description and scope
Sourced articles · one index · cross-theme hyperlinks
| Attribute | Definition / acceptance evidence |
|---|---|
| Product ID | PROD-DIG-NOM-02 — origin-aware nomenclature articles, a canonical term lexicon, A–Z/search navigation, cited source trails and cross-theme links. |
| First article | Leckwith (Lecwydd). Includes standard Welsh/English forms, historical-form index, proposed Helygwydd derivation, separate Llechwedd folk etymology and visible source limits. The historical index’s earliest form is Leckwith (c.1179); the later 1700 form is also indexed as Leckwith. |
| Coverage baseline | 25 existing nomenclature concepts already have dedicated register pages; Leckwith becomes concept 26. Extend each existing concept page with a sourced origin/history explanation where evidence permits. Where no etymology is supportable, state that it is not established and list the next source needed. |
| Canonical data | Use the nomenclature lexicon for concept IDs, names, variants, page URLs and link terms. Keep central data/nomenclature.json and data/glossary.json aligned with the independent nomenclature lexicon so all themes resolve consistently. |
| Article standard | State standard/current forms; dated historical spellings with document locators; etymological and alternative explanations; evidence status and limits; inline references; related internal articles. Identify indexes and summaries as secondary sources where underlying primary records have not been checked directly. |
| Hyperlink rule | First meaningful occurrence of a curated name or concept becomes a real, keyboard-accessible internal link. Use longest-match precedence and skip existing links, headings, navigation, forms, buttons, code, scripts and expressly excluded content. Keep dotted underline/focus treatment restrained and consistent. |
| Build routes | Main Cedwyn build: existing build-time tools/wikilinks.py consumes central nomenclature/glossary data. Independent nomenclature pages retain their existing lexicon-powered term modal. Shared header and Projects build additionally load the lexicon-backed direct-link runtime. Other distinct deployment branches must be listed and checked individually. |
| Non-goals | No automatic inference of ownership, boundaries, legal effect or geographic identity from a shared name; no unsupported etymologies; no external spend; no replacement of WP-DIG-NOM-01 or other PRINCE2 baselines. |
Acceptance gates
A commit is not deployment or live acceptance
| Gate | Pass condition | Required evidence |
|---|---|---|
| G1 · Source and editorial integrity | Leckwith article, lexicon and A–Z/search entry agree. Every indexed form has a date and source locator; unverified variants are labelled. The Helygwydd account remains attributed/probable; Pierce’s relevant book pages have a visible direct-check caveat. | Git SHAs; JSON validation; reference/link check; editorial review of source statuses and uncertainty labels. |
| G2 · Build and branch integration | Main build produces glossary/name links; the Projects build injects the runtime once per eligible page; CORS works; manual links remain usable when JavaScript is unavailable; no nested anchors or broken internal targets. | Successful build logs, deployment identities, CORS response, automated link scan and a theme/branch coverage matrix. |
| G3 · Live acceptance and monitoring | Public Leckwith route works; A–Z and search find Leckwith/Lecwydd; sampled concepts link to the correct article across each published branch; keyboard focus works. | Timestamped production URL checks; counts of pages and linked concepts; broken-link count; pass/fail/untested status per branch; residual actions in the next highlight report. |
| G4 · Origin/history coverage | All 26 concepts have been individually reviewed. Each has a sourced origin/history explanation where possible; unknown origins are openly marked as not established, with a research gap recorded. | Concept-by-concept coverage matrix and article/source references. One first article does not pass G4. |
Current position: G1 is in progress; G2 and G3 are not yet evidenced by a successful build and live checks; G4 remains open until all 26 concepts have been individually assessed.
Tasks and monitoring
Release checkpoints and outputs
| Task | Output | Completion evidence |
|---|---|---|
| NOM-02.01 · Leckwith article | Origin/history article with references, historical forms and uncertainty notes. | Public page, valid citations and exact spelling checks. |
| NOM-02.02 · Canonical lexicon and A–Z/search | Consistent concept ID, aliases, link terms and article URLs. | Valid JSON; index and search smoke test. |
| NOM-02.03 · Central linker | Existing static linker resolves the expanded central concept/glossary data. | Successful main build and link counts. |
| NOM-02.04 · Independent-theme linker | Shared-header runtime and Projects build integration, then coverage checks of each other separate deployment. | Theme-by-theme matrix and sample links on production URLs. |
| NOM-02.05 · Origin/history coverage | Review all existing concept articles and expand them source by source. | 26-row coverage matrix; unsupported origins explicitly marked. |
| NOM-02.06 · Quality and reporting | Automated link checks, keyboard/accessibility check and live deployment follow-up. | Each release records linked concepts/pages, broken links, missing origins, deployment status and next review date. |
| Review cadence | At every nomenclature/site-wide release and in each following programme highlight report until all gates are discharged. | Branch, revision, build/deployment identity, sample URLs and remaining issues. |
RAID and dependencies
Source quality · ambiguity · deployment
| ID / type | Entry | Control |
|---|---|---|
| DEP-NOM-02-01 | WP-DIG-NOM-01 searchable register and its existing concept pages. | Preserve its baseline; this work package extends it rather than replacing it. |
| RISK-NOM-02-01 | Search forms can be mistaken for attested forms or etymons. | Require a source locator/date/status; keep unsupported search leads separate. |
| RISK-NOM-02-02 | Overlapping phrases can create incorrect or nested links. | Longest match first, one occurrence per concept, skip pre-linked and non-prose elements; test overlaps such as “Leckwith” and “Leckwith Woods”. |
| RISK-NOM-02-03 | Not every independent deployment may use the common loader. | Inventory all published themes and prove coverage separately; leave untested branches explicitly open. |
| RISK-NOM-02-04 | Runtime fetch, CORS or cache errors can silently remove linking. | Version the script, serve lexicon CORS headers, retain no-JS direct links and schedule live checks. |
| ISS-NOM-02-01 | Pierce’s 1968 pages 49–52 and the underlying medieval/early-modern documents have not yet been inspected directly for this entry. | Keep visible caveat and a direct-source verification follow-up. |
| Decision constraint | No change to title conclusions, parcel boundaries, legal assertions, project count or external budget. | Use the programme change-control route for any such proposed change. |
Control mirror: create/associate the matching HubSpot task only after CRM object association is confirmed. Do not report the package as complete based on source commits alone.
‹ Master highlight report · WP-DIG-NOM-01 · Master programme plan · Project log