BASIC Know this term. Non-technical explanation.
INTERMEDIATE Technical background useful for workflow discussions.
ADVANCED Full depth. For bar compliance, insurance underwriting, or security review.
§1 — Demo & UI Terms
Terms you'll encounter directly in the Pre-Flight demo interface.
BASIC
Viability Score
In Pre-Flight Context
A 0–100 score estimating how well the documented record supports the plaintiff's claimed injuries. Higher = better documented. NOT a settlement value — it's a documentation completeness signal. A score of 71 means the records provide reasonable support for the injuries. A score of 34 means significant documentation gaps are undermining the case.
Use it for: Identifying which cases need more records before demanding. A low viability score tells you what to request from providers.
BASIC
Deviation Index
In Pre-Flight Context
A 0–100 score measuring how many statistically significant deviations from clinical norms appear in the case file. Higher = more deviations found. This doesn't automatically mean a worse case — some deviations (missed shoulder injury) are harmful to the case; others are manageable. The index tells you HOW MANY flags exist; you determine WHAT THEY MEAN.
BASIC
Record Quality Score
In Pre-Flight Context
A 0–100 score measuring how complete and well-documented the medical record is. A LOW score doesn't mean bad care — it means the record doesn't show what happened. Many excellent physicians document minimally. Pre-Flight flags what IS and ISN'T in the record; you determine what that means strategically.
Common causes of low scores: neuro exam recorded as "negative" without specific findings; PT notes showing "improved" without ROM measurements; referral ordered but no follow-up documented.
BASIC
Demand Letter Draft
In Pre-Flight Context
A structured draft demand letter generated from the five-layer analysis output. Generated from intake + deviation flags + damages summary. NOT written by an attorney. NOT legal advice. Every draft includes: "DRAFT — ATTORNEY REVIEW REQUIRED BEFORE USE." Includes: incident summary, treatment chronology table, deviation flag summary, special damages itemization, demand placeholder.
Primary daily utility output. Attorneys spend hours drafting demand letters. Pre-Flight generates the first structured draft in seconds. Attorney reviews, edits, finalizes.
INTERMEDIATE
RAG / Retrieval-Augmented Generation
In Pre-Flight Context
An AI architecture where the model can only cite information it has explicitly retrieved from a verified source database. It cannot generate citations from its training memory. This makes hallucination structurally impossible: the model cannot produce a citation that isn't in the verified case bank or norms baseline. Every citation comes from: (1) the WA State Verified Case Bank, or (2) the Norms Baseline. If no verified source exists, it's labeled UNVERIFIED.
Why it matters for bar compliance: Standard AI tools hallucinate — they generate fabricated citations. A PI attorney presenting a fake citation in a brief is a bar complaint and credibility disaster. Pre-Flight's RAG architecture makes this impossible.
BASIC
Confidence Level
In Pre-Flight Context
A rating (HIGH / MEDIUM / LOW) on every flag and score, indicating how much the underlying data supports the finding. HIGH = strong support — rely on it as a primary case argument. MEDIUM = probable but some uncertainty — investigate further. LOW = a lead worth checking, not a reliable case argument.
Pre-Flight is transparent about uncertainty. Attorneys are used to working with uncertain information. Pre-Flight names uncertainty explicitly so you can apply your judgment appropriately.
§2 — Clinical Terms
Medical terminology most likely to appear in PI records and Pre-Flight flag descriptions.
BASIC
Cervical Strain / Whiplash-Associated Disorder (WAD)
In Pre-Flight Context
Soft tissue injury to the neck from rapid acceleration-deceleration. The most common MVA injury. Graded WAD I (pain only), WAD II (pain + musculoskeletal signs), WAD III (pain + neurological signs). Pre-Flight's clinical norms: ER → PCP follow-up within 3–5 days → imaging within 2–6 weeks if symptoms persist → PT 2–3x/week for 4–6 weeks minimum.
Red flags Pre-Flight detects: "Whiplash" documented without WAD grade; no neurological exam; MRI ordered > 6 weeks out; no PT prescribed despite persistent symptoms.
BASIC
Radiculopathy / Cervical Radiculopathy
In Pre-Flight Context
Nerve root compression in the cervical spine causing pain/numbness/weakness radiating into the arm following a dermatomal pattern (C6 = thumb, C7 = middle finger, C8 = ring finger). When radiculopathy is documented, the case is significantly more valuable — more objective findings, surgical options. Pre-Flight flags: Was EMG/NCV ordered to confirm? Was the treatment pathway escalated appropriately?
Documentation requirements: Specific dermatomal distribution; motor strength testing by myotome; reflex testing; EMG/NCV ordered if symptoms persist > 4 weeks; MRI if red flags.
INTERMEDIATE
Disc Herniation / Cervical Disc Herniation
In Pre-Flight Context
Displacement of disc material beyond the normal disc space. Can be bulging (contained), protruded, or extruded (free fragment). Key Pre-Flight question: was the herniation at a level consistent with the trauma described? Was there pre-existing degeneration at the same level? Layer 4 (pre-existing) flags C6-C7 herniations when there's prior neck complaint history.
Defense angle: Degenerative disc disease is pre-existing; the accident simply accelerated it. Pre-Flight flags the pre-existing issue so you can address causation proactively.
BASIC
MRI Findings — Reading a Cervical Spine MRI Report
In Pre-Flight Context
MRI is the gold standard for cervical soft tissue injuries. Pre-Flight reads the report language and flags: Is the finding traumatic or degenerative? Does the level match the injury mechanism? Does severity correlate with claimed symptoms?
| Finding | What it means |
|---|
| Disc desiccation | Degenerative — not necessarily trauma-related |
| Disc bulge | May or may not be traumatic |
| Herniation / protrusion / extrusion | Traumatic if at accident level — objective evidence of significant force |
| Neural foraminal narrowing | Causes radiculopathy symptoms |
| Spinal canal stenosis | May cause myelopathy — serious |
| Cord signal abnormality | Urgent finding — requires immediate evaluation |
INTERMEDIATE
Epidural Steroid Injection (ESI)
In Pre-Flight Context
Corticosteroid injection into the epidural space to reduce nerve irritation. A treatment milestone — represents meaningful clinical investment. Pre-Flight tracks: Was ESI preceded by MRI? Was fluoroscopy used (standard of care)? How many ESIs (diminishing returns after 2–3)? Was there a surgical referral after ESI failure?
Defense angle: Multiple ESIs = patient is magnifying symptoms. Pre-Flight's Layer 3 flags incomplete neuro exam before ESI — a defense IME will find the same gap.
INTERMEDIATE
Physical Therapy (PT)
In Pre-Flight Context
Structured exercise and manual therapy. In PI cases, PT attendance is both treatment AND objective evidence of injury severity — attending PT 2–3x/week for months demonstrates the injury was functionally significant. Pre-Flight flags: Was PT initiated within expected timeframe? Was frequency appropriate? Were ROM measurements recorded? Was there a documented plateau before ESI or surgery?
The PT documentation problem: "Patient reports improvement" without specific ROM measurements is a documentation gap. Defense uses these gaps to argue the injury wasn't as serious as claimed.
BASIC
EMG / Electromyography / Nerve Conduction Study
In Pre-Flight Context
Confirms nerve root compression. EMG tests muscle electrical activity; NCS measures nerve conduction speed. Together they confirm radiculopathy and identify which nerve roots are affected. Pre-Flight flags: Was EMG/NCV ordered when radiculopathy was suspected? Absence of EMG/NCV with documented radiculopathy symptoms = deviation from standard workup.
Without EMG/NCV confirmation, radiculopathy is "unconfirmed" in the record. Defense will exploit this.
BASIC
Mild Traumatic Brain Injury / Concussion / mTBI
In Pre-Flight Context
Direct blow or acceleration-deceleration causing temporary neurological dysfunction without gross structural damage on CT. Symptoms: headache, dizziness, cognitive fog, memory problems, sensitivity. The most contested PI injury because: no objective imaging confirmation (CT/MRI typically normal); symptoms are subjective; defense IME physicians are trained to find alternative explanations.
Key documentation Pre-Flight looks for: LOC documented at scene/ER; post-traumatic amnesia (PTA) documented; neuropsychological testing administered; SCAT-5 or similar standardized assessment; graduated return-to-activity protocol; concussion specialist follow-up.
§3 — Legal & Damages Terms
WA State PI-specific terminology and Pre-Flight's use of each.
BASIC
Settlement Range / WA State Norms
In Pre-Flight Context
Documented range of settlement outcomes for PI cases of a given injury type in a given county. Based on WA State public court records, arbitrator awards, and plaintiff bar professional knowledge. Examples (DEMO VALUES — NOT FOR USE IN REAL CASES): Cervical disc herniation with radiculopathy, King County: $85K–$180K. Mild TBI with neuropsych: $75K–$200K.
Important: These are reference ranges based on public data, not guarantees. Individual case value depends on liability strength, documented injuries, carrier behavior, and jurisdiction. Pre-Flight shows where your case sits relative to the norm — it doesn't value the case.
BASIC
PIP / Personal Injury Protection
In Pre-Flight Context
No-fault auto coverage paying medical expenses and lost wages regardless of fault. In WA, PIP is optional ($10K–$35K typical). PIP exhaustion is a major strategic event — when PIP runs out, the plaintiff shifts to health insurance (potential lien) or pays out of pocket. Pre-Flight tracks: Has PIP exhausted? Is it approaching exhaustion based on documented treatment量和billing?
BASIC
UIM / Underinsured Motorist Coverage
In Pre-Flight Context
Coverage that pays when the at-fault driver has insufficient liability insurance. WA drivers must be offered UIM; many carry low limits ($25K/$50K) or reject it entirely. UIM tender (the insurer offering to pay) is a key litigation milestone. Pre-Flight's Layer 5 flags: Has UIM been tendered? Has it been exhausted? What are the policy limits? Is there a delay in tender beyond 60 days?
INTERMEDIATE
Bad Faith / Insurance Bad Faith
In Pre-Flight Context
An insurer's unreasonable or improper conduct in handling a claim — denying without basis, failing to investigate, low-balling. In WA, bad faith arises under RCW 48.01.030 and common law. Requires showing conduct was unreasonable — not just that the claim was denied.
Pre-Flight Layer 5 tracks OBSERVABLE CONDUCT PATTERNS, not bad faith conclusions. A flag means "this pattern is associated with low-ball positioning." Whether it constitutes bad faith requires separate legal analysis. Pre-Flight flags what the carrier did; you determine if it crosses the bad faith line.
High-risk patterns
Moderate-risk patterns
Low-risk patterns
BASIC
Causation / Cause-in-Fact / Proximate Causation
In Pre-Flight Context
The legal requirement that the defendant's conduct actually caused the plaintiff's injury. Two components: (1) cause-in-fact ("but for" the defendant's conduct, the injury would not have occurred), and (2) proximate cause (the injury was a foreseeable consequence of the conduct).
Wall 1 is explicit: Pre-Flight does NOT make causation conclusions. When Pre-Flight flags a deviation — missed shoulder injury, pre-existing C6-C7, care gap — it identifies a clinical or documentation pattern. Whether that pattern breaks causation is a legal determination requiring attorney analysis and expert testimony. Pre-Flight surfaces the data. You make the call.
BASIC
Statute of Limitations / SOL — Washington State
| Claim Type | Deadline | Citation |
|---|
| Motor vehicle PI | 3 years from injury date | RCW 4.16.080 |
| Wrongful death | 3 years from death date | RCW 4.16.080 |
| Government claims | 60 days notice before suit | RCW 4.96.020 |
| PIP claims | 1 year from loss date | Policy-dependent |
In Pre-Flight: Case timeline milestones are tracked against normal PI litigation benchmarks. Cases in litigation > 2 years without resolution = timeline concern flag.
INTERMEDIATE
RCW / WAC Citations
RCW = Revised Code of Washington (statutes). WAC = Washington Administrative Code (agency regulations).
| Citation | Subject | Use in Pre-Flight |
|---|
| RCW 4.16.080 | PI SOL | SOL tracking |
| RCW 48.01.030 | Insurance unfair practices | Bad faith basis |
| RCW 18.080 | UM/UIM provisions | UIM tender standards |
| WAC 284-30 | Claim handling standards | Carrier conduct violations |
| RCW 7.70 | Wrongful death/survival | Damages framework |
| RCW 18.130 | WA Medical Commission | Physician licensing discipline |
| RCW 18.36A | Naturopathy licensing | Wellness lane scope of practice |
BASIC
Special Damages / General Damages
In Pre-Flight Context
Special damages = objectively quantifiable economic losses (medical bills, lost wages, future medical costs). General damages = non-economic losses (pain and suffering, loss of enjoyment of life). Pre-Flight's demand letter draft includes a special damages itemization table extracted from intake. General damages language is drafted for attorney review. Pre-Flight does not calculate general damages.
§4 — Documentation Terms
Medical records concepts driving Pre-Flight's Layer 3 (documentation standards) analysis.
BASIC
H&P / History and Physical
In Pre-Flight Context
The initial clinical evaluation at every hospital admission or new patient encounter. Includes: chief complaint, history of present illness (HPI), past medical history, social history, family history, review of systems (ROS), physical examination, assessment/plan.
Pre-Flight flag: ER H&P without a documented neurological exam in an MVA case = documentation gap. Even if the exam was performed, if it wasn't documented, it doesn't exist in the record.
INTERMEDIATE
SOAP Note
In Pre-Flight Context
Standard clinical documentation format: Subjective (what patient reports), Objective (what examiner observes/measures), Assessment (clinical impression), Plan (treatment plan). Universal in clinical practice.
Pre-Flight flag: PT notes that only document Subjective ("patient reports pain reduction") without Objective findings (ROM measurements, strength testing) = documentation gap. "Patient reports improvement" without objective measurement doesn't prove improvement.
INTERMEDIATE
Differential Diagnosis
In Pre-Flight Context
A list of possible diagnoses ranked from most to least likely. A complete differential is required by the standard of care. A physician who fails to consider relevant diagnoses may be deviating from standard of care.
Pre-Flight flag: When a differential diagnosis was not documented = the physician may have jumped to a conclusion without considering alternatives. Defense IME will use this: "Your doctor didn't even consider other causes of your symptoms."
BASIC
Clinical Significance vs. Legal Significance
In Pre-Flight Context
Two different frameworks for evaluating the same medical finding. Clinical significance: Does this finding affect diagnosis, treatment, or prognosis? Legal significance: Does this finding affect case value, liability, or litigation strategy? These are ALWAYS separate in Pre-Flight. Every flag is labeled with BOTH.
Example: A missed shoulder MRI has clinical significance ("rotator cuff tear went undiagnosed 6 weeks, delaying treatment") and legal significance ("creates argument for additional medical expenses; weakens causation on shoulder component"). Pre-Flight surfaces both; you make the legal call.
§5 — Wellness / Biohacking Terms
Most strategically important layer for WA State PI in 2026. Defense firms are already running wellness history on every PI plaintiff. Pre-Flight gives you advance notice of what they'll find — and lets you control the narrative rather than being ambushed at deposition or IME.
BASIC
Testosterone Replacement Therapy (TRT) / Low T
In Pre-Flight Context
FDA-approved testosterone replacement for men with documented hypogonadism (low testosterone AND symptoms). Pellet therapy (compounded testosterone) widely used in wellness clinics but NOT FDA-approved.
Defense angle: "The plaintiff was already on an unregulated hormone program before the accident. His pre-accident symptoms were from low testosterone, not the accident."
Pre-Flight flags: Was testosterone prescribed with documented low-T labs AND symptoms (defensible)? Was it cash-pay without documented labs (defense weaponizes this)? Was HCT monitored during therapy (failure to monitor = clinical deviation)? Was plaintiff on testosterone at time of accident?
BASIC
BPC-157 / Peptide Therapy
In Pre-Flight Context
BPC-157 (Body Protective Compound-157) is a pentadecapeptide studied for tissue repair. NOT FDA-approved for any clinical use. Widely available through compounding pharmacies and gray-market suppliers. TB-500 similarly unapproved.
Defense angle: "The plaintiff was using experimental treatment before the accident — indicating pre-existing injury." Peptide use in fitness-oriented patients is increasingly documented in PI records. Pre-Flight flags it so you know it exists and can prepare the narrative proactively.
Regulatory status: BPC-157 is not FDA-approved. Compounded peptides occupy a gray zone — legal to prescribe but not approved for efficacy or safety.
INTERMEDIATE
503A vs. 503B Compounding Pharmacies
| 503A | 503B |
|---|
| Type | Patient-specific compounding | Bulk (office use) |
| Regulator | State boards of pharmacy | FDA-registered, cGMP required |
| Documentation | Patient-specific Rx | Full records, more defensible |
| In PI context | Common | Higher regulatory bar |
PI context: 503A dispensed = patient-specific prescription, defensible. No pharmacy documentation = gray-market supplier, significant liability gap. 503B = deeper pockets for product liability (FDA-registered, cGMP compliant).
INTERMEDIATE
Functional Medicine / Integrative Medicine
In Pre-Flight Context
A systems-biology approach addressing root causes rather than symptoms. Uses diet, lifestyle, supplements, and targeted testing. NOT part of conventional medical training or insurance-covered care. Diagnoses common in functional medicine (adrenal fatigue, chronic Lyme, leaky gut) are NOT recognized by conventional medicine.
Defense weaponizes this: These diagnoses in a plaintiff's records undermine credibility. Pre-Flight flags: Any functional/integrative encounters; any non-conventional diagnoses; any supplements prescribed; gaps between functional medicine and conventional treatment.
Wall 3 reminder: A functional medicine encounter is a flag, NOT a causation conclusion. Defense will look at it. It does not mean the treatment caused harm.
BASIC
Off-Label Prescribing
In Pre-Flight Context
Prescribing an FDA-approved medication for a use not on the FDA label. Legal and common. Examples: Gabapentin for nerve pain (approved for seizures/shingles); antidepressants for pain (approved for depression).
Pre-Flight assessment: Off-label is not inherently problematic — it's standard in many situations. Pre-Flight flags whether documented medications were used on-label or off-label and whether the off-label use has good evidence support (gabapentin for neuropathic pain = reasonable; gabapentin for anxiety = weaker).
BASIC
Wellness Flag / Documentation Risk Indicator
In Pre-Flight Context
Pre-Flight's term for any wellness/biohacking finding in the record. Every wellness flag is labeled with: (1) What was found, (2) What defense will do with it, (3) How much exposure this creates, (4) Pre-Flight's confidence level.
5 wellness intersection points (where wellness and PI collide):
- Pre-existing condition arguments (defense uses wellness history to establish pre-existing)
- Magnification / malingering arguments (wellness treatments used to argue plaintiff was already treating)
- Causation disputes (testosterone cessation post-MVA; peptide use)
- Documentation gaps (wellness providers often don't use EHR; records may not exist)
- TBI/concussion overlap (HBOT, NAD+ used by concussion patients — defense weaponizes)
§6 — Insurance Terms
BASIC
ROR / Release of Claims
In Pre-Flight Context
A legal document signed by the plaintiff releasing the at-fault insurer from further liability in exchange for a settlement payment. Pre-Flight's Layer 5 tracks: Was the ROR tendered with appropriate documentation (medical records supporting the release amount)? Or was it a bare ROR with no backup? A bare ROR = flag for low-ball positioning.
INTERMEDIATE
Carrier Conduct Patterns / WA State
| Carrier | Observable Pattern | Strategic Implication |
|---|
| Allstate | Early resolution suppression; low initial offers; INEX manipulation | Associated with below-range settlements in King/Pierce/Snohomish |
| State Farm | Stronger litigation posture; higher trial rates | More variable outcomes; more hard-fought cases |
| GEICO | Fast initial contact; aggressive early resolution push | Lower average settlements; total low-value vehicles |
| Liberty Mutual | Mid-market positioning; moderate litigation propensity | Predictable settlement range; moderate resistance |
⚠️ These are OBSERVABLE PATTERNS, not conclusions. Pre-Flight tracks whether documented behavior matches these patterns. Whether it constitutes bad faith requires separate legal analysis.
INTERMEDIATE
WAC 284-30 / Washington Insurance Regulations
In Pre-Flight Context
The WA Administrative Code regulation governing insurance claim handling practices. WAC 284-30-330 prohibits: denying claims without reasonable basis; failing to acknowledge pertinent communications; failing to promptly investigate; failing to affirm or deny coverage within applicable time limits.
Pre-Flight use: When Layer 5 flags a carrier action that violates WAC 284-30, Pre-Flight cites the specific WAC provision. This gives the attorney the regulatory citation for evaluating whether an OIC complaint is warranted.
§7 — Security & HIPAA Terms
BASIC
PHI / Protected Health Information
In Pre-Flight Context
Any information that can identify a patient combined with their health information. HIPAA's definition includes 18 identifiers: name, address, DOB, SSN, medical record number, health plan number, etc. PHI triggers HIPAA obligations.
Deployment model implications: Model A (Attorney-Local) = no PHI on Signal Loom, no HIPAA obligations for us. Model B (HIPAA Cloud) = PHI on our HIPAA-configured infrastructure, BAA required. Model C (Zero-Knowledge) = encrypted before transmission, Signal Loom cannot access, no BAA required.
INTERMEDIATE
BAA / Business Associate Agreement
In Pre-Flight Context
A legally required HIPAA contract when a covered entity shares PHI with a third party (business associate). Establishes each party's HIPAA obligations.
| Model | BAA Required? |
|---|
| A — Attorney-Local | No |
| B — HIPAA Cloud | Yes — Signal Loom provides |
| C — Zero-Knowledge | No — we can't access PHI |
BASIC
AES-256 Encryption
In Pre-Flight Context
The Advanced Encryption Standard with 256-bit key length. The strongest commonly available encryption. Used by US government agencies and financial institutions. Mathematically unbreakable with current computing — no feasible brute force attack. All data at rest on Signal Loom's servers is AES-256 encrypted. Field-level encryption means specific sensitive fields (names, dates, injury descriptions) are encrypted individually.
INTERMEDIATE
TLS 1.3
In Pre-Flight Context
Transport Layer Security version 1.3 — the current strongest protocol for encrypting data in transit over the internet. When you submit an intake form, TLS 1.3 ensures the data is scrambled between your browser and our servers. TLS 1.2 has known vulnerabilities; TLS 1.3 is faster and more secure. Pre-Flight uses TLS 1.3 exclusively.
BASIC
Zero-Knowledge Architecture
In Pre-Flight Context
An architecture where Signal Loom has zero ability to read, access, or decrypt the user's data — even in encrypted form. Data is encrypted in the browser before transmission. Signal Loom receives encrypted blobs and processes them without ever seeing the plaintext. This is Model C. Because Signal Loom cannot access the plaintext, we cannot be compelled to produce it.
Trade-off: Zero-knowledge is the most secure but has practical limitations — no full-text search across encrypted records, some features require plaintext processing. Best for highest-sensitivity cases.
BASIC
Immutable Audit Log / Append-Only
In Pre-Flight Context
An audit log where entries can only be added, never modified or deleted. Every access to case data is permanently recorded — user ID, timestamp, IP address, action, data accessed. Prevents anyone from going back and altering the record to conceal unauthorized access. Logs are retained for 6 years. In the event of a breach or dispute, the audit log provides a complete, tamper-proof record.
BASIC
Cryptographic Erasure
In Pre-Flight Context
The permanent destruction of data by destroying its encryption key — not deleting the file. When the key is destroyed, the encrypted data becomes mathematically unreadable. Even if someone recovers the physical storage media, they cannot read the data without the key.
Pre-Flight use: When an attorney deletes a case or terminates their account, cryptographic erasure is the deletion method. Key destroyed. Data gone permanently, including from backups. No way to recover it.
§8 — Technology Terms
INTERMEDIATE
RAG / Retrieval-Augmented Generation
In Pre-Flight Context
The core hallucination-prevention architecture. The AI can only cite sources it has explicitly retrieved from the verified case bank or norms baseline. It cannot generate citations from its training memory. If no verified source exists for a claim, it is labeled UNVERIFIED or ATTORNEY ANALYSIS REQUIRED. RAG architecture is the technical implementation of the "no hallucination" guarantee.
BASIC
JSON
In Pre-Flight Context
JavaScript Object Notation — a standardized text format for structuring data. All Pre-Flight intake data is submitted and processed in JSON. Human-readable structured data. Example: {"case_type": "cervical_mva", "deviations": [...]}
BASIC
API / Application Programming Interface
In Pre-Flight Context
A defined interface for one software system to communicate with another. Pre-Flight's API accepts intake JSON and returns Pre-Flight report JSON. Integration with Clio, PracticePanther, or CasePeer would use this API. For the pilot, attorneys submit intake via the web form.
INTERMEDIATE
Cloudflare Workers + D1
In Pre-Flight Context
Pre-Flight's API runs on Cloudflare Workers (serverless compute at edge locations globally — fast, scalable, pay-per-use). Case data is stored in Cloudflare D1 (distributed SQLite — extremely low latency). Cloudflare's infrastructure is SSAE SOC 2 Type II certified and offers a Business Associate Agreement for healthcare customers.
§9 — Pre-Flight Architecture Terms
BASIC
Five-Layer System
In Pre-Flight Context
Pre-Flight's analytical architecture — five independent layers, each analyzing the case from a different professional perspective. The layers don't share conclusions. A clinical deviation is NOT automatically a legal liability finding.
| Layer | Focus | Evidence Base |
|---|
| 1 — Clinical | Treatment deviations | AAOS, ACOEM, AUA guidelines |
| 2 — Legal/Damages | Settlement ranges, timeline | WA public court records, arb awards |
| 3 — Documentation | Record completeness | WA evidence rules, E&M standards |
| 4 — Wellness | Biohacking history risk | FDA categories, RCW scope of practice |
| 5 — Insurer | Carrier conduct patterns | WA OIC actions, plaintiff bar knowledge |
INTERMEDIATE
Parameter Walls
In Pre-Flight Context
Explicit architectural barriers between the five layers preventing cross-contextualization — the most dangerous type of AI error in legal analysis.
| Wall | Separates | What it prevents |
|---|
| 1 | Clinical ≠ Legal | Clinical deviation → legal liability conclusion |
| 2 | Damages ≠ Clinical | Low settlement → mild injury conclusion |
| 3 | Wellness ≠ SOC | Wellness deviation → malpractice conclusion |
| 4 | Documentation ≠ Care | Gap in record → gap in care |
| 5 | Wellness ≠ Causation | Wellness flag → causation conclusion |
| 6 | Insurer Conduct ≠ Bad Faith | Carrier pattern → bad faith conclusion |
BASIC
Norms Baseline / NORMS-BASELINE.md
In Pre-Flight Context
The foundational reference document for Pre-Flight's clinical and legal norms. Every deviation flag traces back to a specific line in this document. When Pre-Flight says "this is a HIGH deviation from the cervical strain pathway," you can open NORMS-BASELINE.md and read the specific line defining the expected pathway. Every flag is auditable.
BASIC
Deviation Flag
In Pre-Flight Context
A specific identified instance where the case file departs from a documented norm. Every flag includes: Severity (CRITICAL/HIGH/MEDIUM/LOW) + Confidence (HIGH/MEDIUM/LOW) + Source citation (specific norm line in NORMS-BASELINE.md) + Clinical significance + Legal significance + Cross-lane interactions (if any).
BASIC
Confidence Level
In Pre-Flight Context
HIGH = strong support in the data. Rely on it as a primary argument. MEDIUM = probable but some uncertainty remains — investigate further. LOW = a potential lead worth checking, not a reliable case argument.
INTERMEDIATE
Sealed Outcomes / Test Bank Isolation
In Pre-Flight Context
The test bank (SLL-001–SLL-010) uses a sealed outcome protocol: case facts built without knowing the outcome; outcome written and sealed; analysis developed against sealed outcomes. This prevents outcome contamination — the analysis can't be designed to produce a desired result because the desired result wasn't known when the analysis was built. The test bank is isolated from production.
For bar compliance: The BUILD-AUDIT-TRAIL.md document (separate) has the full sealed outcome protocol and all self-policing measures documented. Disclosure-ready for malpractice carrier review.
Required Disclaimers — On Every Pre-Flight Report
⚠️ ATTORNEY REVIEW REQUIRED
All output requires review by licensed Washington State counsel before use in any legal proceeding, demand, or filing. Pre-Flight is a case analysis tool, not legal advice, and does not substitute for attorney judgment.
⚠️ CITATIONS VERIFICATION REQUIRED
All citations must be verified against primary sources before use. Demo citations are marked [DEMO — FICTITIOUS].
⚠️ CAUSATION INDEPENDENT
Clinical deviation flags are findings for attorney and expert analysis. Causation requires separate legal determination.
⚠️ BAD FAITH INDEPENDENT
Insurer conduct flags are observable pattern indicators. Bad faith is a legal conclusion requiring separate analysis by licensed counsel.
⚠️ SETTLEMENT RANGES — REFERENCE ONLY
Documented settlement ranges are based on public WA State records and plaintiff bar professional knowledge. Reference ranges only — not valuations. Individual case value is determined by the attorney based on all case-specific factors.