Project Initiation Documentation

1. Brief and PID

• Project Brief
• Project Initiation Documentation (this page)
• Business Case
• Project Product Description

2. Plans

• Project Plan
• Stage Plan S0 / S1
• Work Packages
• Product Descriptions
• Trigger-event SOPpreserve, verify, advise, file in time
• Side project: reopen the caseSP-REOPEN, standby until a trigger

3. Registers and logs

• Issue Register
• Decisions awaiting the Executive
• Risk Register
• Quality Register
• Lessons Log
• Daily Log
• Product Register

4. Reports

• Highlight Reports
• Checkpoint Report CR-2026-10-21
• End Stage Report S0 (interim)
• Issue Report I-032
• Issue Report I-077 — consistency and provenance audit
• Prospective fraud triggers to reopen the case

5. Archive

• Superseded pages and the former Legal Wiki PRINCE2 pages

As the Project Brief: background, objectives, desired outcomes, scope and exclusions, constraints and assumptions, users and interfaces.

• Free routes first: requests, follow-ups, reviews and complaints before any paid copy or visit.
• Every item obtained is catalogued, provenance-checked and verified.
• Court steps only after written legal advice.

Business Case: option 1 selected; £0 spent; reviewed at G0.

A one-person Project Board: the Executive also holds the Senior User role. The Project Manager (AI agent) reports to the Project Board; AI workers act as Team Managers, one per work package.

Standard: every statement linked to its evidence page or marked PENDING / HYPOTHESIS / SOURCE PENDING. Methods: line-by-line check against the opened source; statement audit; Executive review. Records: Quality Register.

Quality criteria by product class

Issue types: request for change; off-specification; problem/concern. Record: Issue Register, with an issue report where needed. Authority: the Project Manager within tolerance; the Executive beyond tolerance or on any baseline change. Change budget: none.

Identify: each research cycle, each reply received, each stage boundary. Assess: probability and impact (High / Medium / Low; programme risks on 1–5 scales), and proximity. Respond: avoid, reduce, fallback, transfer, share, accept. Record: Risk Register. Escalate: any risk outside tolerance, or scoring 15 or more, or needing spending or an outward step, goes to the Executive; a forecast tolerance breach brings an Exception Report.

• One email per recipient body; no cc/bcc; UK office hours; reply in the body’s latest thread.
• Before each send: inbox checked; draft read in full; references, dates and quotes checked; no accusation as fact, threat or admission; no duplicate of a pending request.
• Items not yet checked are marked as such; sources named.
• Cadence changes only with the Executive’s agreement (L-007).
• No contact details or subject access replies on public pages.

Benefits B-01 to B-05 are listed in the Business Case with their measures and timing. Benefit owners, baseline measures and post-project review are not yet set.

No suppliers engaged. Paid copies (HM Land Registry OC2, archive copies) are bought only with the Executive’s approval, at published fees or quotes held (Project Plan, budgets). Solicitors: none engaged.

Public record: the wiki and the bucklerfamily.estate sites. Private execution ledger: the task and contact system (CH-001). Source files in Git; Cloudflare changes add-only and reversible. Personal data and subject access replies are not published; privacy checks on every public page.

Not yet set.

Not applicable: the project does not change an organisation’s ways of working.

Project Plan (draft; baselined at G0) and the current Stage Plan.

Tolerances: not yet agreed by the Project Board; proposed figures are in the Project Brief.

• Highlight report each reporting period (Highlight Reports).
• Exception Report if a tolerance is forecast to be exceeded (first trigger: HM Land Registry copies not held by 6 Nov).
• End Stage Report and next Stage Plan at each stage boundary; G0 on 18 Dec 2026.
• Daily Log, registers and Product Register kept current.

• Executive and Senior User combined.
• Checkpoints are the 6-hourly research cycle reports.
• Checkpoint Report CR-2026-10-21 is published as a dated snapshot; approval is not recorded. It lists 16 packages while the Work Packages register lists 17; reconcile under I-077. No Exception Report is listed as issued.
• Management products are published as web pages; the order and headings follow the PRINCE2 7 outlines.