← Return to examples
Public source patterns
Faultline demo packets use public-source patterns to show how decision risk can be surfaced before commitment. This page explains those patterns without publishing private materials or turning public records into accusations.
How to read this page
These notes are not legal findings, accusations, diligence memos, or claims that any named company engaged in misconduct. They describe public record categories that can help identify evidence gaps, contamination paths, operating constraints, and conditions that would change a decision.
Faultline's public examples are intentionally narrower than private diligence. They show the shape of a pre-commitment Decision Hold / No-Hold packet while keeping source framing calm, anonymized where appropriate, and tied to decision risk rather than blame.
Source Pattern Sections
Regulatory
Regulatory filings and public agency records
Agency releases, rulemaking activity, inspection histories, public dockets, warning letters, and official guidance can show whether a decision depends on unsettled requirements or public constraints.
Procurement
Procurement, bid, and certification records
Bid language, certification clauses, cost support, supplier representations, flow-down terms, and compliance attestations can reveal whether the evidence behind a signature is current and defensible.
Local record
Local board, zoning, and permitting materials
Board agendas, hearing materials, permits, rezoning packets, public comments, and meeting records can surface approval-path risk before a site or project becomes publicly locked in.
Resolved records
Litigation, enforcement, and settlement records
Public court, regulator, and settlement records can illustrate categories of representation, control, or evidence failure. They should be framed as public-record patterns, not as accusations beyond the record.
Operations
Technical standards and operating constraints
Standards, technical requirements, safety controls, capacity limits, and operating procedures can identify where a plan assumes capability before the evidence is ready.
Market signal
Public reporting and market signals
Credible public reporting, market changes, delays, cancellations, and opposition signals can help test whether a plan is relying on stale assumptions or underweighted external constraints.
Current Demo Set
Growth
PLG reallocation
Uses a pattern of attribution contamination: conversion data can record the final channel while missing earlier sales or marketing influence that shaped the decision.
GTM / Sales
Sales manager
Uses an operating-pattern diagnostic: requests for support can be real while still pointing to process, enablement, founder, sales-ops, or lead-quality constraints instead of a full-time manager.
Fundraising
Non-profit capital campaign
Uses campaign-readiness patterns: donor evidence, board commitments, grant eligibility, case-for-support feedback, and tracking systems should be proven before public goal-setting.
Infrastructure
Data center pre-hearing / power-readiness
Uses public regulatory and local-record patterns such as DOE/FERC large-load interconnection activity, rezoning and permitting materials, and reporting on power or opposition delays. It does not claim Faultline verified a specific live project.
Procurement
GovCon pre-bid certification
Uses public procurement and enforcement record categories to frame certification evidence risk. Pricing, cyber, supplier, and billing evidence should support the exact representation being signed.
Food / QA
Food supplier / label / co-packer approval
Uses FDA-style supplier verification, recall-pattern, label reconciliation, allergen-control, co-packer, and lot-traceability source categories as an operational release-gate composite.
Public Safety Notes
GovCon non-conflation note
Separate public records involving Raytheon defective-pricing matters and Raytheon/Nightwing cyber matters must not be conflated into one event, accusation, or causal chain. On public pages, they should be treated only as examples of public-record categories that can inform certification-risk patterns.
Data-center caution note
Data-center examples should remain anchored to public regulatory and local-record patterns: large-load interconnection activity, public rezoning or permitting materials, and reporting on power access or organized opposition delays. Do not describe a specific live project as verified unless that verification exists and is public-safe.