Pattern framework · v1.1 · living

The Framework

A custom framework for proving the pattern, not the person. Every claim must be provable from a primary-source document — a date, a filing, a return, an order, a statute, a study. Never from motive.

The principle

The record is the battlefield. The case moves on the face of the transaction. What can be proven can't be denied.

Section 2

The four questions

Apply to both the machine and the case. Answer with documents, not theory.

QuestionThe machine (the fraud)Our case (the response)
TargetThe accounting — the value (securities, estate, trust corpus); the family is the vehicleThe false record — the paper that says "nothing happened here"
RecipientState + county (per-diem + adoption bonuses), private providers, court-appointed economy, the dependent-claimant (a signed name)The children first; then every mother behind us, via an issue-precluded record
GoalConvert family into inventory + paper; manufacture justification; strip the means to contestMake the record say what happened; convert the pattern into locked, undeniable fact
Outcome intendedInvisibility — "no fraud on paper"Visibility — "no deniability on paper"
Section 3

The six cracks

Each crack is a verifiable structural feature — exploitable without any single named actor. A crack is a design feature on paper, not an allegation about a person.

Section 4

The mapping

Each crack → the document that proves it → the doctrine it triggers → the case that carries it.

CrackEvidence (document)DoctrineCase (anchor)
Funding architectureTitle IV-E, ASFA, state/county contractsMonell policy/custom; RICO enterpriseMonell, 436 U.S. 658
One-way stayCOVID stay order, docket datesMonell policy; fraud on the courtHazel-Atlas, 322 U.S. 238
Dependent-claim fraudRejected return, IRS transcriptRICO tax-fraud predicate; fraud on the courtSedima, 473 U.S. 479
Staged texts / fabricated recordMessages, phone, forensic imageFraud on the court; wire-fraud predicateHazel-Atlas, 322 U.S. 238
SpoliationDrive, email lockout, surgeAdverse inference; obstructionChambers, 501 U.S. 32
Pattern continuityFull docket history, funding docsRICO pattern (relatedness + continuity)H.J. Inc., 492 U.S. 229
Section 5

The doctrines

Pattern-based mechanisms — each wins on the pattern, with no named person.

Fraud on the court

The process itself is the target; no statute of limitations. (Hazel-Atlas; Chambers)

Monell §1983

The entity answers for the policy or custom, not the officer. (Monell v. Dep't of Social Services)

RICO

The enterprise's pattern of predicate acts. (Sedima; H.J. Inc.)

Res ipsa loquitur

The thing speaks for itself. (Byrne v. Boadle)

Adverse inference

Destruction of evidence is itself the proof.

Issue preclusion

Once proven, it can't be denied. Collateral estoppel.

Section 6

The harm evidence

The third pillar: proven, measured harm to the child. The science that rebuts "best interest of the child." See the full harm evidence page.

Scope

Developmental effects before and after removal; long-term adult outcomes; hidden abuse within placements, through puberty and into adulthood.

Gate — proven results only

Peer-reviewed, longitudinal or controlled, replicated, with reported outcomes. No single-study, no unpublished, no anecdote.

Section 7 · 8

The process & the rules

The process

1. Identify a crack (or harm category).
2. Pull the primary-source document.
3. Verify — word-for-word, holding-for-holding.
4. Map: crack/harm → document → doctrine → case.
5. Lock the verified fact (issue preclusion).
6. Update the framework.

The rules (non-negotiable)

1. Dates and registration, not motive.
2. No fabricated citations — verified or removed.
3. No person named unless their signature is on a document.
4. What can be proven can't be denied.
5. The record is the battlefield.