Project Brief (digital estate)

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 objectives

Know, run and protect every estate asset from one record.

Desired outcomes

A resilient, independent and well-documented digital estate.

Project scope and exclusions

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).

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 states otherwise.

Constraints and assumptions

free hosting plans where possible; privacy first (no personal contact data on public pages); reversible, logged changes; no Git history rewrite without the Executive.

the Executive keeps control of the GitHub, Cloudflare, WordPress and Google accounts; Project Manager operates them within standing authority.

Project tolerances

Not yet agreed by the Project Board. Proposed in the PID.

Users and other interested parties

Family members, researchers and readers of the public record.

Interfaces

GitHub, Cloudflare, the hosted wiki, Google, HubSpot.

Business Case (digital estate): “do something” chosen.

A resilient, independent and well-documented bucklerfamily.estate digital estate. Acceptance criteria:

• Every live asset is in the register with platform, repository, 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.

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

Executive (estate owner); Senior User (family, researchers, readers); Senior Supplier (AI agent with the hosting platforms); Project Manager (AI agent).

• Product breakdown and descriptions
• Product Register (asset register)