Conceptual Bases

“I was compelled to construct an engine that runs on memory, and it consumes their own records as fuel. Every contradiction it produces is theirs.”
Michael J. Burdette-Deakin

Working Conventions (Context for Professional Engagement)

The following notes describe working conventions relevant to correspondence and requests during professional review.
They do not form part of the evidential or analytical record.

• Use direct, unambiguous questions.
• Expect measured, precise, accuracy-first responses.
• Evidence is kept exactly as received; do not rename or repack files.
• If something seems missing, check the folder — nothing is hidden.
• Provide full context, rather than summaries; structural accuracy matters.

Extended - Method & Conceptual Framework

The papers below collectively define the method and conceptualisation roots by which the forensic evidential system design and compilation, including chronology engineering, cross-domain record reconciliation, and tamper-resistant evidential architecture was built and verified.

Note: Some of these papers were generated in the earlier stages of design and build of the suite, as such some later discoveries are not mentioned and some details, files ~ number, navigation have changed and do not entirely reflect the same values (how many files) in the current iteration.
For full suite manifest of documents please see "manifest.txt" in the root of the suite.

The 'knowledge' the system organises is foundational in its source and coherent in its structure. Its resolution is justified by a deductive chain of legal inference that is traceable, transparent, and conditionally dependent upon the accuracy of the admitted facts, thereby providing a warranted assertion of the most likely legal outcome

• Suite Rationale - Establishes why the suite is HTML-based; sets out technical, evidential, and operational constraints underpinning the system’s design.
• The Navigational Model - Describes how professionals actually move through the suite; outlines the five operational modes and expected review behaviour.
• Modules Legal Function - Maps each module to its litigation purpose; clarifies evidential weight, causation role, and how components support specific legal claims.
• The Engineered Solution - Articulates the operational philosophy converting systemic failure into a verifiable evidentiary engine.
• Chronology Legend Rationale - Defines data schema, chronological logic, and key field interpretations.
• A Personal Cost (Background) - Provides contextual insight into the labour, endurance, and reconstruction burden behind the suite; frames credibility and method without advocacy.
• This "Describes" Me - (Note: See Paradigm Delta) Outlines the analytical profile, cognitive habits, and precision-bias influencing system construction; clarifies interpretive stance for counsel.
• This "Explains" Me - Documents the underlying reasoning model within 'Describes Me' document and evidential intolerance to distortion; establishes the intellectual provenance behind the suite’s design.
• Autobiographical Extract - Offers insights into the authors cognitive development.
• Cognitive Structural Model.pdf A structural analysis describing a pressure-activated, systemic cognition externalised as a coherent forensic engine.