Project Mandate & Brief — the digital estate

Estate level · version 1.0 · 20 October 2026

Mandate

Instruction from the Executive, 20 October 2026: projects.bucklerfamily.estate is to be independent and to hold PRINCE2 project planning of the overall bucklerfamily.estate resources and digital assets.

Background

The estate grew quickly: over 50 web addresses across two domains, more than 40 hosting projects, five code repositories, a hosted wiki, an e-book, films, data stores and several scheduled workflows. Much of it was built for the Great House Farm (Tŷ Mawr) evidence work. No single place recorded what exists, who owns it, whether it is live and whether it is backed up.

Project definition

  • Objective: know, run and protect every estate asset from one record.
  • Scope in: every bucklerfamily.estate and financecheque.uk site, the hosted wiki and its estate mirror, Git repositories and branches, Cloudflare Pages and Worker projects, domains and DNS, data stores, publications (e-book, files, films), and the Gmail, HubSpot, Calendar and scheduled workflows that operate them, plus their backups (Git, private exports and the Internet Archive).
  • Scope out: the evidence content itself (owned by the evidence recovery workstream); dormant sites the Executive has asked to leave alone (calls, old branches), until the Executive says otherwise.
  • Deliverables: the Asset Register; a Product Breakdown Structure; Risk, Issue and Quality registers; stage plans; a communication plan; highlight reports; a lessons log.
  • Constraints: free hosting plans where possible; privacy first (no personal contact data on public pages); reversible, logged changes; no Git history rewrite without the Executive.
  • Assumptions: the Executive keeps control of the GitHub, Cloudflare, WordPress and Google accounts; Tab operates them within standing authority.

Outline business case

See Business Case.

Project approach

Inventory first, then independence, then resilience, then publishing (see stage plans). Work is done in small, verified changes by Tab’s workers, each built locally, checked live and logged.

Acceptance criteria

  • Every live asset is in the register with platform, repo, owner role, status and backup status.
  • No estate site depends on the hosted wiki to work; this site carries no link to it.
  • Every public site passes the privacy check.
  • Every Git-built site can be rebuilt from its branch; every data store has a recorded export.
  • The campus shows a building for every live public site.