Record

This material now lives at https://fcg.bucklerfamily.estate/case/the-tightrope.

Page ID: 923 · Title: The Tightrope · Evidence status: Not yet labelled — see the Editing Protocol · Version: 1.0.0 · Editing Protocol

The Tightrope is the controlled route from discovery to evidence, accountable decisions and—where the evidence and law permit—remedy and reparations.

This is an operational roadmap, not a finding of liability. Suspected fraud, concealment, government or public-authority involvement remain lines of enquiry until supported by evidence. The objective is to leave no material evidential question without a recorded source path, result, contradiction check and next action.

Chronological roadmap

Select a crocodile. The hazard label opens to explain what can derail that stage. The centre is the route forward; the two sides are the procedural and evidential risks that can close, delay or misdirect it.

CENTRELINE

Preserve → Reconstruct → Access → Review → Regulate → Title & Law → New Evidence → Remedy

🐊 Vexatious / repetitive requests

FOIA section 14 can permit refusal of a vexatious request, with separate rules for repeated substantially similar requests. Keep each request distinct and evidentially purposeful.

1 · PRESERVE

Freeze the evidence before the argument.

🐊 Threatening / accusatory correspondence

Keep correspondence factual and controlled. State the record sought and the proposition being tested; do not let anger or accusation become the subject of the exchange.

🐊 Premature fraud / concealment allegation

Record suspected conduct as a line of enquiry. Identify the primary record that should exist and what evidence would falsify the theory. A missing record is not itself proof of concealment.

2 · RECONSTRUCT

Build the documentary chain.

🐊 Wrong procedural doorway

Separate personal data, public information, environmental information, archive holdings and specialist statutory routes. One channel should not be made to carry the whole dispute.

🐊 Third-party data / exemption barrier

A subject access request is primarily about the applicant’s personal data. Separate that from third-party data, privilege and other restrictions before framing the request.

3 · ACCESS

Use SAR / UK GDPR, FOI, EIR and archive routes deliberately.

🐊 Over-broad scope

Use an issue number, date range, record class, custodian/function and land/title/planning identifier. Narrow requests are easier to search, review and audit.

🐊 Silence interpreted as evidence

Diary the due date and follow the published route. Preserve non-response as part of the record, but do not treat silence as proof of agreement, concealment or liability.

4 · REVIEW

Convert every refusal or decision into a reviewable record.

🐊 Complaint swallows the real issue

Keep separate: information-rights review, service complaint, data-protection complaint, land-registration decision and potential court claim.

🐊 Regulator deadline missed

The ICO asks for FOI/EIR complaints within six weeks of the final response or last substantive contact, and generally asks for data-protection complaints within three months of the last meaningful contact.

5 · REGULATE

Escalate only with a completed packet.

🐊 Regulator expected to award the remedy

Regulatory action is not automatically compensation or title relief. Build the regulatory record while separately identifying the forum able to grant the substantive remedy.

🐊 HMLR route confusion

Current HM Land Registry guidance provides a specific error-reporting route and a two-stage complaints procedure. The Independent Complaints Reviewer deals with qualifying service issues, not disputes about land-registration decisions or points of law.

6 · TITLE & LAW

Move from records to the legal route that fits the proved facts.

🐊 Time-bar / limitation trap

Judicial review normally requires filing promptly and within three months, subject to shorter specific limits. Human Rights Act proceedings generally have a one-year period, subject to extension and stricter procedural limits.

🐊 Fraud / concealment clock assumed incorrectly

Limitation Act section 32 may postpone limitation in certain actions involving fraud, deliberate concealment or mistake. It is not a universal reset: the cause of action and statutory conditions must be tested.

7 · NEW EVIDENCE

Treat discovery as a dated legal event.

🐊 ECHR six-month misunderstanding

The ordinary Strasbourg application period is four months from the final domestic decision. Rule 80’s six months concerns revision of a judgment after discovery of a qualifying new fact. Do not assume it is a general reopening rule or that it automatically applies to the family’s 1989 matter.

🐊 Publication creates a second dispute

Keep the Wiki evidence-led. Cite sources, qualify inference, correct errors and avoid presenting allegations as findings.

8 · REMEDY

Seek the remedy that matches the proved wrong.

🐊 “Reparations” treated as one claim

Map each asserted wrong to its own legal or administrative mechanism. Title relief, rectification/indemnity, public-law relief, compensation, human-rights remedies and heritage redress may be separate tracks.

Deadline dashboard

Route	Key control
FOI / EIR	Track initial response, internal review and regulator stage separately.
ICO — FOI/EIR	ICO asks that complaints normally reach it within six weeks of the final response or last substantive contact.
ICO — data protection	ICO generally asks for complaints within three months of the last meaningful contact.
HMLR	Stage 1 → Stage 2 → Independent Complaints Reviewer for qualifying service complaints; land-registration decisions have separate routes.
Judicial review	Promptly and normally within three months; some categories are shorter.
Human Rights Act	Generally one year, subject to extension and stricter procedural limits.
Limitation Act s32	Certain fraud / concealment / mistake cases may postpone limitation if statutory conditions are met.
ECHR	Ordinary application: four months. Rule 80 revision of a judgment: six months after discovery of a qualifying new fact.

Fraud, concealment & public-authority involvement

Run this track more tightly, not more aggressively. For every suspected act ask: What is the allegation? What primary record should exist? Where should it be held? What evidence currently exists? What would falsify the theory? For suspected public-authority involvement, trace named decisions, records, meetings, plans, applications, transfers, instructions and correspondence. Do not infer coordinated conduct merely because several institutions appear in the same chronology.

Procedural anchors

• HM Land Registry — Complaints procedure

• HM Land Registry — How to report an error

• ICO — FOI/EIR complaints

• ICO — Subject access requests

• CPR Part 54 — Judicial review

• Human Rights Act 1998

• Limitation Act 1980

• ECHR Rule 80

• ECHR Practical Guide on Admissibility Criteria

---

Control gate: before any major disclosure, complaint, regulator referral or legal instruction, update the Master Timeline, Evidence Library, Missing Records Register and deadline diary together. The aim is not to send more correspondence; it is to make every step count.

Master Timeline · Evidence Library · Records Access Chronology · Missing Records Register · Anomalies Register · Reparations & Remedy Q&A

Page version & change log

Current version: 1.0.0

Version	Date (UTC)	Editor (human or agent name)	Change	Source / evidence
1.0.0	2026-10-18T15:20Z	Sion’s Tab agent	Footer standardised; earlier log rows carried into this table; no content change	Editing Protocol, 18 Oct 2026
	2026-10-18 (rollout date; exact time not separately recorded)	OpenAI-assisted maintenance agent (GPT-6)	Installed the page-local append-only change log and agent instructions. Existing page content was not intentionally rewritten.	User-directed site-wide changelog standard. Saved via WordPress API; public rendering of this page not yet independently checked.

Agents and editors: follow the Editing Protocol.