NCTSO
Forensic assessment · v1.1.0 · updated 1 November 2026
Translation pending: the assessment text below is in English, the authoritative record.
- Response status
- Replied, nothing disclosed
- Last contact
- 13 October 2026
- Next date on file
- None on file
- Earlier version
- v1.0.0, published 18 October 2026 on the Legal Wiki
Since last assessment
18 October 2026 to 1 November 2026
Our reading: No new correspondence is on file since the last assessment. The earlier finding stands unchanged.
The assessment as last published
Carried over unchanged from v1.0.0 (18 October 2026). Links point inside this site.
Email dialogue evidence: every email exchanged with the National Counter Terrorism Security Office (NaCTSO) about Great House Farm is catalogued word for word, by thread and date, at National Counter Terrorism Security Office (NaCTSO) — Email Correspondence Catalogue.
Chronology and catalogue links — assessed 10-10-2026: See the Institutional Involvement Roadmap (1877–2026) for the date-ordered institution, people and evidence sequence. The reported 1988 Cadw-to-Minister spot-listing letter has its own placeholder at GHF-E152; the original has not been attached to that page as at 10-10-2026. A placeholder records an evidence gap, not the letter’s content or proof of misconduct.
Forensic Assessment — NCTSO
Scope: National Counter Terrorism Security Office role only where a specific historical record is identified.
Current evidence position
The reviewed Great House Farm record does not presently establish an NCTSO decision or operative role in the title, possession, heritage or demolition history. The organisation should therefore not be treated as part of the historic accountability chain merely because it appears in the project universe. 🕒10-10-2026
Control test
Require an exact document, date, function and decision before opening a substantive workstream.
Current finding
No NCTSO wrongdoing or operative historical role is established. 🕒10-10-2026
Human action
The historical-operational enquiry remains parked unless a court, police, planning, government or archive record provides a concrete lead about the 1988 event. Separately, the modern records-retrieval appearance is now documented and cross-linked above; do not treat it as evidence of historical deployment.
Acceptance: route remains parked with a defined evidence-trigger condition.
Cross-institution record added 9 October 2026: the NPCC’s FOI 3065/2026 retrieval email names NaCTSO among the present-day functions consulted. This establishes a modern records-retrieval appearance only; it does not evidence NaCTSO’s participation in the 1988 operation. See GHF-E106-R51 and the NPCC forensic assessment. 🕒10-10-2026
Institutional appearance timeline — linked source index
Coverage rule: this is a chronological navigation map of published Wiki source pages found by searching the current site index for “NCTSO”. Every event label links directly to the page containing the source. It avoids duplicating source narratives. It records mention/appearance, not culpability. Dates are transcribed from page titles where available; “Date not explicit in title” means the linked source must be consulted. Search indexing is a discovery aid, not proof of exhaustive external coverage. 🕒10-10-2026
| Date shown by source title | Event / source — open evidence | Record class |
|---|---|---|
| Date not explicit in title | FOI & Public-Authority Reply Register — every reply email and its attachments | Published Wiki evidence page |
| Date not explicit in title | Records Access Chronology | Published Wiki evidence page |
Records-access register appearances — direct row links
Rows below match the institution’s name or an alias in the reply register’s sender/reference or recorded description. A match shows an appearance in the records trail, not necessarily an act by this institution.
| Date | Correspondence / register item (click to open) | Reading rule |
|---|---|---|
| 1 Oct 2026 | R47 — National Counter Terrorism Security Office (NCTSO), via WhatDoTheyKnow | Register row contains a name/alias match; inspect the linked row to distinguish sender, recipient and incidental mention. |
Related navigation: FOI & Public-Authority Reply Register · Records Access Chronology · Evidence Library
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:30Z | the editors | 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 this 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.
Case file
This file is built for a future reparations claim. Facts are as the records show them; interpretation is labelled “our reading”. Items marked “not checked” have not been compared with the original record.
(a) Conduct timeline
16 dated interactions, oldest first; 0 automatic acknowledgements are left out. Quotations are verbatim from the institution’s email; where the reply’s substance was an attachment, the email subject is quoted instead.
Show the timeline
| Date | Direction | Reference | Type | Verbatim |
|---|---|---|---|---|
| 2 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 2 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 6 September 2026 | received | — | correspondence (no disclosure) | Subject: Please update the status of your request - BP vs Buckler 1987 |
| 7 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 7 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 7 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 17 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 18 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 22 September 2026 | received | — | correspondence (no disclosure) | Subject: Please update the status of your request - BP vs Buckler 1987 |
| 29 September 2026 | received | — | correspondence (no disclosure) | Subject: Please update the status of your request - BP vs Buckler 1987 |
| 29 September 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 1 October 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 1 October 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 5 October 2026 | received | — | correspondence (no disclosure) | Subject: Please update the status of your request - BP vs Buckler 1987 |
| 9 October 2026 | received | — | correspondence (no disclosure) | When you get there, please update the status to say if the response contains any useful information. |
| 13 October 2026 | received | — | correspondence (no disclosure) | Subject: Please update the status of your request - BP vs Buckler 1987 |
(b) Inconsistencies and gaps
None found in the correspondence on file.
(c) Quarantined-name links
Records on the quarantine register (Kissed Frogs) that sit in, or came from, this institution’s holdings. None is treated as settled.
No quarantined-name record on the register is linked to this institution’s holdings.
(d) Duty and liability — our reading
Liability indicators (our reading): none
- Duty
- FOIA 2000; Data Protection Act 2018 (Part 3 for law-enforcement data, UK GDPR Art. 15 for subject access); the Management of Police Information code and APP on retention and review of records.
- Indicators the duty was not met
- none found in the correspondence on file.
- Evidence still needed to confirm
- the institution’s retention schedule and disposal record for the series in question; the catalogue or file list it searched; any internal review or complaint outcome.
- Likely extent of exposure if confirmed
- A records-management or complaint finding; correspondence that is inconsistent with its own earlier messages goes to handling, and wider exposure depends on what the records, once found, show.
(e) Evidence still needed
- Inspect any retained occurrence books, station logs or weekly orders that the force or the county archive holds for the period. for paid visit list
Versions
| 1.1.0 | 2026-11-01 | Moved to the Forensic Assessments webapp; dated “Since last assessment” section added; response status re-read. |
| 1.0.0 | 2026-10-18 | As published on the Legal Wiki. |