Bridge Forensic Logic
Method
How the work is done. The principles, hierarchy, and procedure that govern every engagement.
Bridge Forensic Logic applies the discipline of forensic methodology to the analysis of documents. The work is documentary rather than investigative. It examines what records exist, what they say, what they omit, and what the gaps between them reveal.
The methodology was developed and proven through the Bridge Universe, a continuity-first transmedia project with documented canon governance, editorial provenance, and narrative architecture spanning thousands of pages of canonical material. The same rules that govern a multi-thousand-page canonical corpus apply to client engagements of any scale.
The core proposition is this: continuity is not a feature added at the end of creative work. It is an architectural discipline applied from the first document forward.
Governing Principles
Seven Principles
01
Source Sovereignty
The client's source material is the controlling authority. Bridge Forensic Logic never invents lore, events, characters, or relationships to fill perceived gaps.
02
Flag, Don't Fix
Contradictions are identified and surfaced — never silently resolved without the client's knowledge and consent.
03
Preserve Omissions
Gaps are preserved until the client intentionally develops them. An absence is not an error.
04
Smallest Sufficient Revision
Prefer the smallest edit that solves the problem. Never rewrite an entire passage when a local edit suffices.
05
Strict Provenance
Every claim, recommendation, and correction must trace back to a verified source document and edition.
06
Zero Canon Drift
Corrections must align with the client's established canon. No drift between what the canon says and what the correction introduces.
07
Closed-Corpus Integrity
No external or AI-derived material is introduced into a client's closed corpus unless explicitly authorized by the client.
Authority
Source-of-Truth Hierarchy
When multiple authorities exist within a corpus, a written hierarchy is established from highest to lowest authority at project kickoff. The hierarchy is client-specific and documented in the project file. The general model, adaptable per client:
- Current manuscript prose (active draft).
- Authoritative reference documents (bible, codex, master document).
- Secondary canonical references (supplementary guides, appendices).
- Earlier editions or drafts, superseded where they conflict with higher authorities.
For any active project, one designated master corpus or master document is the sole editable authority. New deliverables must descend from that master. When two versions conflict, the designated master controls.
Conflict Rule
When two authorities conflict, the conflict is flagged explicitly. One reading is never silently selected. The conflict, the authorities involved, and the edition or version of each are documented.
Procedure
The Audit Process
Taxonomy
Finding Classification
Verified Claim
A statement confirmed against the source corpus, with citation.
Unsupported Claim
A statement that cannot be traced to a verified source.
Contradiction
Two or more sources make mutually exclusive claims about the same fact.
Open Question
The source material is ambiguous or incomplete; the client must decide.
Client Decision Required
The correction path depends on the client's authorial intent and cannot be resolved without them.
Return
What an Audit Returns
Every audit returns exactly three things:
- Verified claims — statements confirmed against the source corpus.
- Unsupported claims — statements that cannot be traced to a verified source.
- Clean source list — only the documents actually used, with editions and versions cited.
No additional material is introduced. No editorial commentary is inserted into the audit findings.
Source
Content on this page is drawn from the BFL Methodology Master v1.1 (Service Lane Methodology Edition, August 7, 2026), the controlling methodology reference for the Bridge Forensic Logic service lane. Where the Master and this page differ, the Master governs.