Nomenclature Register Repair

Product attribute	Definition / acceptance evidence
Product ID	PROD-DIG-NOM-01 — complete current compiled nomenclature register at the existing cited route.
Source baseline	Standalone nomenclature lexicon 1.0.1, generated 24 October 2026. Keep the lexicon as the source for this display; a future harvest is a separate work item.
Coverage	25 groups and 148 wording entries in the current compiled lexicon. Five entries have no direct URL in the source data; the register must not pretend they do.
Per-row fields	Exact recorded or analytical wording, date, subject group, source/provenance, evidence/status class and any limitation. Distinguish record, catalogue, secondary, reported/OCR, identity unresolved, wiki label and source pending.
Interaction	Text search, status filtering, direct group navigation, readable small-screen fallback, and all rows still readable without JavaScript.
Route integrity	Keep the existing route and canonical URL. Preserve the legacy-host redirect. Verify the assembled production route, not just a source-branch preview.
Interpretive limit	“Cedwyn Estate” is a current working label, not a period name proven by the entries here. Similar wording, shared names or grouped variants do not prove identity of a place, parcel, title, legal person or boundary.
Acceptance owner / authority	Release acceptance is a factual checklist, not a legal opinion. Independent Project Assurance is not appointed in the programme record. No separate executive decision is implied by this page.

Gate	Pass condition	Exception trigger
G1 · Source control	Change merged into the nomenclature branch with the old route retained and counts validated against lexicon 1.0.1.	Merge conflict, changed source count or redirect/canonical regression.
G2 · Build and publish	Cedwyn assembly completes, the build commits the generated site to the served site branch, and deployment reports success.	Build fails, deployment does not start, stale source snapshot is assembled, or the main link checker rewrites/misses a required internal link.
G3 · Live acceptance	The public cited route returns the new title, displays 148 rows across 25 groups, search/status controls work, and no key source link or canonical route is broken.	Any count discrepancy, 404/redirect loop, missing body, unusable mobile layout, or unsupported evidential assertion.
Scope tolerance	Change only this register presentation and the Project Office control record, plus the main site-area description needed to trigger and describe a real build.	New evidence, changed parcel boundaries, legal or title conclusions, or a re-harvest are outside scope and require their own product/change record.
Cost / schedule tolerance	£0 external spend; complete in the current release cycle.	Any paid dependency, major redesign, missing source data or build blocker is escalated as an exception, not silently absorbed.

Do not mark G2 or G3 passed from the Git commit alone. Record deployment identity and observed live checks in the Project Office / HubSpot log before declaring final acceptance.

ID / type	Register entry	Control / response
ISS-NOM-01 · Issue	The cited Cedwyn estate entry showed only five entries, while the compiled lexicon holds 148 variants across 25 groups. It functioned as a short dictionary entry rather than the useful catalogue described in outbound correspondence.	Correct the entry into a full register while retaining the five estate-specific wordings and their individual evidence classifications.
RISK-NOM-01 · Threat	A future assemble/build can overwrite a manually edited generated output, or assemble an older mirrored theme branch.	Edit source branch first; use the standard Cedwyn build; confirm built revision and live route. Never treat a source preview as deployment proof.
RISK-NOM-02 · Threat	Grouped or near-identical names may be mistaken for proof of geographic or legal identity.	Preserve status, provenance and limitations on every row; keep the working-label warning prominent.
DEP-NOM-01 · Dependency	The current compiled lexicon is version 1.0.1 (generated 24 October 2026). It is not a claim of exhaustive capture of every name in every original document.	Keep the separate ROLE-CUR harvest task open until an actual re-harvest and difference review are completed.
DEC-NOM-01 · Decision	Use the existing cited URL and expand its content rather than force correspondence recipients to follow a new URL.	Preserve the route and canonical URL; revise external correspondence links only if live acceptance discovers a genuine link defect.

In this programme, “PRINCE2 mythology” is used deliberately for the governing story that turns work into roles, stages, products, tolerances and decisions. The model is useful only when the statements it makes can be checked against the record.

• Roles are appointments, not magic words. Writing “Executive”, “Senior User”, “Project Board” or “Independent Project Assurance” does not appoint a person. Where the programme has not recorded an appointment, this work package does not invent one.
• A green report is not a verified fact. The source merge can be proven from Git; publication can be proven from a successful build/deployment; acceptance requires observing the live URL. Each is a different claim with its own evidence.
• Tolerance is a boundary, not permission to overrun. A count mismatch, route failure, external cost or evidential overclaim triggers escalation and a recorded decision rather than a quiet scope change.
• A product description is a test, not decoration. The accepted product is the usable register with the agreed fields, coverage, navigation and limits, not simply an HTML file that exists.
• Lessons change the next stage. The practical lesson is that an outbound citation saying “all nomenclature” must lead to a register whose coverage and limitations are visible on arrival. A dictionary-style stub must not pass as a complete catalogue.

PRINCE2 status does not decide ownership, historical identity, legal cause of action or whether a court should reopen a case. Those remain evidence and legal-gate questions under the separate programme controls.

Lesson / action	Disposition
The external description of a resource must match the experience at its cited URL.	Applied here; add an explicit landing-page check to future outbound-email and website acceptance lists.
Do not confuse a page-display repair with an evidence harvest.	The lexicon still needs a separately controlled re-harvest after the 21 October Wiki scrape, followed by a differences report and review of unresolved/source-pending forms.
Names are a key/index into source artifacts; they are not independent proof of identity or title.	Retain links to underlying records and the per-row status and uncertainty notes.
HubSpot mirror	Record the change ID, merge SHA, deployment run, live acceptance result, and residual ROLE-CUR harvest task separately; do not close the harvest task just because this page was repaired.

Follow-on change control (raised 31 October 2026): WP-DIG-NOM-02 — sourced name-origin articles and site-wide wiki links. The follow-on adds origin/history content, a Leckwith first article, cross-theme linking and live-coverage acceptance tests. Preserve the original WP-DIG-NOM-01 register-repair baseline; this follow-on does not close the separate nomenclature re-harvest.

Machine/source control: GitHub change record PR #53. The final live acceptance record belongs here and in the associated HubSpot control task once verified.