Read the Docs

The wiki organises historical records, correspondence, archival references, planning and heritage material, chronology, and analysis relating to Great House Farm. Its purpose is to make underlying evidence traceable and help readers distinguish what a source records from what someone infers from it.

Look for the source or evidence item first, then its description, context and any interpretation. A named person’s testimony, an allegation, a hypothesis, an inference and a formal finding are different kinds of statement and must not be treated as interchangeable.

Individual records and artefacts support evidence pages; evidence pages support chronologies and topic groupings; higher-level analysis links back to underlying evidence. A claim should be traceable to its source wherever one exists. This is the intended information architecture, not a claim that every existing page already follows it perfectly.

An evidence page records a particular document, image, map, register entry, correspondence item or other artefact. Identify the source and provenance, describe what is actually visible or recorded, transcribe accurately where appropriate, and link to the original or catalogue reference when available. Keep interpretation distinct from the source description. Do not fill gaps by inventing missing content.

A forensic assessment examines a defined question against identified evidence. It should move directly into the assessment: scope and question, evidence reviewed, findings or observations, competing explanations, limitations, confidence and next evidential steps. It is not a declaration that wrongdoing occurred. Separate documented facts, family evidence, allegations, inference and unanswered questions; cite the supporting records at the point of use.

Catalogues and registers are finding aids: they organise records, identifiers, dates, custodians, status and links. They should make material easier to locate rather than repeat long explanations of the overall project. Preserve stable identifiers and distinguish confirmed entries from leads or placeholders.

Chronologies arrange events by date and link each material entry to its source. Record date precision and uncertainty honestly, distinguish contemporaneous records from later recollection, and flag conflicts rather than silently harmonising them.

Analysis pages connect evidence to a defined issue or argument. Show the reasoning chain and the evidence that supports or contradicts it. Distinguish court findings and documented procedural history from legal arguments, disputed allegations and hypotheses. Attribute contested claims and do not present a theory as judicially established unless the judgment actually establishes it.

Index of every evidence item: EV ID, date, title, type, status, repository/reference, old GHF-E ID. Evidence Register.

One page per evidence item, under the Evidence Register. Fixed table: EV ID, date, type, evidence label, repository/reference, status (HELD with scan link, or PENDING), provenance, proves, does not prove, claims that rely on it.

Ranked list of records known to exist but not held: holder/reference, how to obtain, cost, who can obtain it. Pending Evidence.

Older evidence-library entries (GHF-E###): one record or event per page with type, date, holder and evidence status. The Evidence Register gives each one’s EV ID.

One proposition per page. Each statement cites its evidence (EV or GHF-E ID) or is marked PENDING or HYPOTHESIS. Family positions are attributed as such.

Working theories, not findings. State what would confirm or refute them, and the counter-evidence.

Emails and replies reproduced unaltered. Wording inside them is the correspondent’s, not the wiki’s. A correction sits in a short note beside the email, with its source.

Navigation only (Start Here, Agent index, registers). Not evidence.

Rules for editors and agents: Editing Protocol, Site Agent Operating Rules, Brand & Developer Guidelines.

Central record of material edits: date, page, before, after, reason/source. Master Change Log.

Each head of loss: legal basis, method, sourced inputs, low / central / high in today’s £, dependencies. Labels: QUANTIFIED, ESTIMATE, CONDITIONAL, PENDING, TBC. Damages page.

Lists the project’s management products and their state.

The client’s instruction that starts the project: the need and the outcome wanted. Not how or when.

Defines the project from the Mandate: objectives, scope, constraints, tolerances, users, outline business case, project product and approach.

The baseline for running the project: links the definition, Business Case, roles, approaches (quality, risk, issue, communication), plan, controls and tailoring.

Why the project is worth doing: reasons, options, benefits, dis-benefits, timescale, costs and major risks. Reviewed at each gate.

Who holds each PRINCE2 role and whether it is confirmed.

Who receives what, through which channel and how often.

Stages, dated schedule with dependencies, critical path, assumptions and the cost table.

The current stage in detail and the next stage in outline.

The products the project must deliver, and for each: purpose, composition, derivation, format, quality criteria, quality method and responsibilities.

Agreed parcels of work: products, owner, dates, tolerances, dependencies and acceptance.

Risk, issue, quality, daily log, lessons and decisions, each with a unique ID and status. Records are closed, never deleted.

Log of change requests with impact and decision, and the blank request form.

The controlled items (management products and EV pages), their status, location and owner.

Periodic report to the Executive: status, work done, work next, tolerances, changes, issues, risks, lessons.

Blank Checkpoint, Exception and End Stage Reports in PRINCE2 7 composition.

Identify source creator, date, archive or catalogue reference and custody history where known. Describe what it contains before explaining significance. Preserve source links, exact quotations where needed, and material gaps or limitations. Never invent citations or provenance.

Keep what a source says separate from the author’s interpretation of it. Attribute testimony to the named person and link their Testimony page; label allegations, inference and hypotheses accordingly; mark a statement with no document and no identified speaker SOURCE PENDING. State uncertainty where it changes the conclusion and include credible counter-evidence or alternative explanations.

Use consistent names, dates, identifiers and terminology. Where evidence pages have versions, explain what changed and preserve traceability to the source material and prior versions.

One page per family member who has said or written anything on record, under Testimony. Each page lists only real sources, with date and reference: affidavits, witness statements, court records, letters, emails and newspaper quotes. Words in quotation marks are verbatim from the record held; a search snippet or OCR text is marked as such. A person with nothing on file has a page that says “No affidavit or recorded statement on file yet”. Other pages cite a document where one exists, attribute a family member’s words to that person with a link to their page, and mark anything with neither as SOURCE PENDING. Where a court ruled otherwise, the evidence is shown first and the court’s words are quoted and sourced.

PRIMARY DOCUMENT HELD: copy or scan of the original held. PRESS REPORT: newspaper report, not the original. CATALOGUE ENTRY ONLY: archive catalogue entry; document not yet read. TESTIMONY: a named family member’s recorded statement (affidavit, witness statement, letter, email or newspaper quote), cited with its date and linked to their Testimony page. SOURCE PENDING: no document and no identified speaker yet. HYPOTHESIS: working theory, not a finding.

The site uses explicitly authored native HTML disclosure elements, with a short summary label readers can open. Long text is not automatically converted into expandable sections site-wide. Use concise labels and collapse substantial secondary explanation where that improves scanning, but never hide essential findings or remove source material merely to shorten a page.

Use clear, restrained third-person writing for public-facing case material. Do not explain a page’s purpose or repeat what it is about in the page body. Use one link sentence only: What this page is about → Read the Docs, linked to the closest matching anchor in this guide (for example, evidence pages, catalogues and registers, forensic assessments, chronologies, or analysis pages). Do not add a “Purpose” paragraph, generic introduction, or AI-written overview. Keep the body for substantive records, provenance, necessary caveats, scope tests, source descriptions and analysis; when removing redundant page-description text, preserve all evidence, links, quoted material and case-specific caveats.

Header: Page ID · Title · Evidence status · Version. Footer, where present: “Page version & change log” table — version (MAJOR.MINOR.PATCH), date (UTC), editor, change, source; newest first.

Before changing the site, read the Brand & Developer Guidelines. Inspect the actual page before editing; preserve evidence, links, media and hierarchy; test representative changes; and report exactly what changed and what was verified. Never claim a site-wide implementation from a single-page test.