Fit map, not method, not proof.
Purpose
EOS LUX is British Black Light's source-anchored evidence-intelligence layer for contested records, fragmented communications, omissions, provenance gaps and high-consequence decision files. This document exists to help a buyer recognise their own problem, see where EOS LUX fits alongside the tools they already use, and understand what it does not do. It does not explain the method and it does not attempt to prove it — it is a fit map, not a walkthrough.
Who It Is For
A dispute is forming around a failed project, a termination, a supplier relationship, an executive decision, or a regulatory issue. The legal team has emails, messages, meeting notes and document versions, but no clear map of what actually happened. EOS LUX produces a chronology, source anchors, missing-decision-trail questions, key custodians, a contradiction register, and review priorities before external counsel spend increases.
A client arrives with a large archive and a strong narrative, but the underlying evidence is scattered, partial and emotionally charged. EOS LUX separates facts, claims, assumptions, interpretation and omission signals, and produces an issue chronology with first-pass case-theory stress points for the team to test.
A client instructs counsel with a large, disorganised archive and a tight budget. EOS LUX cuts first-pass review time before billable hours scale, producing a solicitor-ready issue map without replacing counsel's judgment on the matter.
The eDiscovery platform can host, search, tag and produce documents, but the team still needs to know what to look for first. EOS LUX sits before or alongside that review, surfacing priority topics, source-anchor clusters, likely missing context, custodian pathways, communication gaps, and a review-question map.
A grievance, whistleblowing complaint, retaliation allegation, conduct concern or workplace conflict depends on months of Slack, Teams, email or WhatsApp history. EOS LUX maps the chronology, pressure points, exclusion or silence windows, role and influence patterns, and consistency across accounts, leaving unresolved questions for fair human review. It does not decide the grievance.
A control has failed, a policy exception has repeated, an approval trail is unclear, or a regulator may ask what the organisation knew and when. EOS LUX produces a source register, an exception chronology, missing-authority questions, record-reconciliation indicators, and an evidence pack for audit or regulator-response preparation.
A board must approve, defend or revisit a high-consequence decision, but the evidence base is dispersed across board packs, emails, advice notes and informal conversations. EOS LUX shows what evidence supported the decision, what assumptions were treated as facts, what uncertainty remained, where dissent or missing context appears, and what should be clarified before the decision is relied on further.
A deal looks commercially attractive, but informal communications, founder behaviour, customer concentration, operational claims or diligence answers create uncertainty. EOS LUX maps diligence gaps, assumption drift, informal influence, divergence between the public and private narrative, founder or key-person risk indicators, and post-deal dispute exposure.
An internal investigation needs a first map of the record before interviews harden a narrative. EOS LUX structures the file into chronology, source anchors, omissions, contradictions and follow-up questions. It does not determine misconduct.
A founder suspects supplier fraud, contractor misrepresentation, internal dishonesty or a commercial breakdown, but cannot yet justify expensive legal escalation. EOS LUX creates a first-pass evidence pack, a timeline, source anchors, missing-document questions, negotiation-preparation notes, and a solicitor-ready issue summary.
A business or platform depends on customer reviews, complaints, ratings or marketplace reputation, but coordinated activity, suppression, fake reviews or provenance gaps may be distorting the picture. EOS LUX identifies review-burst patterns, linguistic similarity, missing purchase-verification signals, suspicious timing, and coordinated praise or complaint clusters, producing an evidence pack for internal or regulatory review. It does not declare fraud.
A review project involves months of staff communications. Before analysis begins, the DPO needs assurance on lawful basis, minimisation, retention and record boundary. EOS LUX supports this through a defined-record-boundary statement and an audit trail of what was processed and why — a matter of data-handling discipline, not a product screen.
A suspicious claim chronology, broker or intermediary communications, missing explanations, or a dispute about sequence. EOS LUX produces a source-anchored chronology with visible omission and gap markers, so a claims reviewer can see what the record shows and where it is incomplete. EOS LUX does not decide the claim.
Hotline submissions, retaliation-pattern review, internal escalation chronology, or a need to establish what the communications record contains before disclosure. EOS LUX gives a documented, source-anchored starting point. It does not decide whether to disclose, or whether retaliation occurred.
Use Cases By Function
Building a defensible chronology and issue map before manual review costs escalate.
Structuring a communications record into chronology, source anchors and follow-up questions ahead of interviews.
Mapping conduct-adjacent communications for fair, evidence-anchored review.
Testing whether the narrative behind a deal survives contact with the underlying record.
Reconstructing the evidence base behind a high-consequence decision before it is relied on again.
Reconciling records and exceptions ahead of an audit or regulator response.
Establishing a defined, lawful record boundary before any analysis begins.
Structuring public-interest records without converting uncertainty into accusation.
Identifying pattern indicators in reviews, ratings and reputational signals.
Establishing what a record supports, what it does not, and what needs corroboration.
Mapping communications and record gaps around a reputational exposure.
Producing a first-pass evidence pack before legal escalation.
Anchoring a disputed claim's chronology to its source record.
Establishing a documented starting point for a disclosure decision.
Automotive and multi-site network review sits as also-relevant colour under platform trust and review integrity, not as a core sourced function in its own right.
Use Cases By Industry
A firm facing a document-heavy dispute gets a faster first map of the record before manual review becomes expensive and unfocused.
A structured evidence base speeds the path from raw record to defensible first map.
A conduct or disclosure question is separated into what was known, claimed, documented, and unsupported.
A contested claim's chronology is anchored to source, with gaps made visible rather than assumed.
High-volume digital records, AI-generated content and unstable information get a controlled first structure.
Reputational signals get a defensible evidence pack without claiming fraud as a conclusion.
A workplace record gets a fair, reviewable structure ahead of a human decision.
A sensitive record is reconstructed while preserving uncertainty and avoiding premature blame.
A fair, reviewable map of facts, claims, gaps and next questions supports a safeguarding process.
Public-interest records get structure without converting uncertainty into accusation.
Decisions, warnings, instructions and missing approvals get located within a sprawling project record.
The gap between operational reality, formal reporting and decision records becomes visible.
Review-integrity questions get a defensible evidence pack without asserting fraud.
A deal narrative gets tested against the record it claims to rest on.
Internal conduct or client-dispute records get the same source-anchored structure applied elsewhere.
A record's support for a claim, its limits, and what still needs corroboration get made explicit before publication.
Also relevant, though not sourced as validated deployment: manufacturing and logistics, charities and NGOs, and franchise or multi-site networks.
The named industries above are the Product Brief's intended fit map, not a claim that EOS LUX has been deployed or validated in each sector. The "also relevant" items are reasonable extensions of the same capability, not case-study evidence.
What EOS LUX Does Not Do
EOS LUX does not provide legal advice, determine guilt, prove fraud, decide who is lying, diagnose people, determine admissibility, or replace professional judgment. It helps responsible reviewers see what the record contains, what it omits, and what should be examined first. It does not replace lawyers, investigators, HR teams, compliance officers, or boards. It is not a truth detector, an autonomous forensic system, or a psychological profiling tool.
Every output requires qualified human review before any action, allegation or decision relies on it. Analysis proceeds only on a defined record set, with agreed scope and data-handling terms, including lawful basis where personal data is involved.
CTA
Confidential briefing → scoped engagement → evidence pack for human review.
Request a Confidential Briefing