Bridge Forensic Logic
Method Services Boundaries Case Structure Resources About Contact
Narrowlight Press
Overview Books The First Fracture Bridge Universe White Papers Essays All Publications Downloads Future Releases
The Archive
Overview Bridge Universe Creator's Bible Continuity Records Character References Timelines Causal Chains Fleet Mobility Research Ledgers Development History Public Archive
Material Culture
Overview

Bridge Forensic Logic

Case Structure

How an engagement is organised, from intake through delivery.

Every engagement follows the same structure regardless of scale. The structure exists so that the provenance of every finding remains traceable from the final deliverable back to the source document it came from.

Four things are fixed at intake and recorded in the project file: the designated master, the source-of-truth hierarchy, the scope of the corpus under examination, and the format of the return.

Sequence

Stages of an Engagement

Stage 1  Intake All source documents are received and inventoried. Filenames, formats, word counts, and edition labels are recorded. The corpus boundary is set: material outside the designated scope is not consulted during the audit.
Stage 2  Master Designation One master corpus or master document is designated as the sole editable authority. All deliverables descend from that master. The designation is documented in the project file.
Stage 3  Hierarchy The source-of-truth hierarchy is established in writing, from highest to lowest authority. The hierarchy is client-specific.
Stage 4  Examination Text, structure, and metadata are extracted programmatically. Contradictions, timeline conflicts, character inconsistencies, terminology drift, and unresolved gaps are searched for by automated and manual methods.
Stage 5  Verification Every finding is verified against the source document before it is recorded. No finding is reported from memory.
Stage 6  Classification Each verified finding is classified as a verified claim, unsupported claim, contradiction, open question, or client decision required.
Stage 7  Return The audit report is delivered with correction tables and source-verified recommendations, together with a clean list of the documents actually used.

Controls

Change Control

The following rules govern every edit, correction, and revision made to client material.

  • No reconstruction. A client corpus is never rebuilt from prior versions, component files, or superseded drafts.
  • No silent substitution. Earlier versions are never silently substituted when editing a designated master.
  • No imported prose. Prose is never imported from any source other than the designated master.
  • Version lineage. Every change is tracked with its source edition, date, and reason. A revision ledger is maintained for the project.
  • Explain before presenting. Significant changes are explained before revised text is shown.
  • When uncertain, ask. Uncertain changes are not made without client input.

If the client replaces the designated master during an engagement, the supersession is recorded with date, reason, and acknowledgment.

Editorial

Standards Applied to Prose

Where an engagement includes editorial work, the client's prose voice is preserved. A different style is not imposed. Sustained paragraphs that carry thought, perception, movement, and consequence are favoured over screenplay cadence, and dialogue emerges from prose and returns to prose.

Ambiguity is preserved where it is intentional. Character motivations and emotions are not overexplained. Characterisation is inferred from established canon rather than from stereotype, and characters are not made more articulate, emotional, humorous, or dramatic than the text supports.

Prose improvements the client did not request are not made. Nothing is inferred, normalised, or silently corrected that the client did not ask to have corrected.

Delivery

Quality Control Before Release

Before any file is delivered, the following are confirmed: the file is non-empty and opens without error; all source citations are present and traceable; no unauthorised material has been introduced; front matter is complete; the filename follows the naming convention; and the deliverable descends from the designated master only.

Deliverables are saved to disk immediately upon production. For multi-format batches, files are produced and saved one at a time, and each write is confirmed before the next begins.

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.