---
title: "Frameworks — The Riverman Methodologies"
description: "The complete portfolio of methodologies originated by River Caudle: SHIP, SECURE, RIVER, STREAM, Schema on Read, OT Stability Doctrine, plus the Industrial Independence Architecture."
canonical: "https://rivercaudle.com/frameworks/"
author: "River Caudle"
keywords:
  - Riverman frameworks
  - OT methodologies
  - industrial networking frameworks
  - SHIP
  - SECURE
  - RIVER
  - STREAM
  - Schema on Read
  - OT Stability
  - IEC 62443
  - industrial independence
  - River Caudle
  - Riverman
robots: index, follow
license: Riverman Fair License v2.0
---

# Frameworks

**The Riverman methodologies for industrial networks.**

> Six small named frameworks, each addressing a different problem on the plant floor. Free to plant operators and industrial workers, forever. Commercial use under the [Riverman Fair License v2.0](https://rivercaudle.com/license/).

Originated by [River Caudle](https://rivercaudle.com/).

---

## At a glance

| ID    | Framework                                                | Domain               | Tagline                                                          |
|-------|----------------------------------------------------------|----------------------|------------------------------------------------------------------|
| F.01  | [SHIP Framework™](https://rivercaudle.com/ship/)         | Network design       | One protocol to rule them all                                    |
| F.02  | [SECURE Method™](https://rivercaudle.com/secure-method/) | Cybersecurity        | IEC 62443 simplified for industrial networks                     |
| F.03  | [RIVER Method™](https://rivercaudle.com/river/)          | Troubleshooting · linear | When in doubt, follow the RIVER                              |
| F.04  | [STREAM Method™](https://rivercaudle.com/stream/)        | Troubleshooting · cyclic | Follow the STREAM in cycles                                  |
| F.05  | [Schema on Read vs Write™](https://rivercaudle.com/schema-on-read/) | Knowledge transfer | Teaching the framework, not the facts                  |
| F.06  | [OT Stability Doctrine](https://rivercaudle.com/ot-stability/)      | Change management  | In OT, change is risk. Stability is security.        |
| F.07  | [Industrial Independence Architecture](https://industrialindependence.org/) | Architecture | One unit per zone; only scope changes.                  |

---

## F.01 — SHIP Framework™

**Domain:** industrial network design

Four steps for designing networks that actually serve the people who depend on them. *Standardize · Harden · Isolate · Protect.* If you can't explain your network on one page, it's too complex.

→ <https://rivercaudle.com/ship/>

---

## F.02 — SECURE Method™

**Domain:** OT cybersecurity

Six steps that turn IEC 62443 into a sequence operators can actually follow. *Segment · Establish · Control · Update · Respond · Evaluate.* Making industrial cybersecurity standards actually usable in the real world.

→ <https://rivercaudle.com/secure-method/>

---

## F.03 — RIVER Method™

**Domain:** troubleshooting · linear

Five-step Layer-1-up troubleshooting for the technician on shift. *Reboot · Inspect · Verify · Examine · Replace.* Physical first, because 80% of problems are physical.

→ <https://rivercaudle.com/river/>

---

## F.04 — STREAM Method™

**Domain:** troubleshooting · cyclic

Six-step cyclic troubleshooting for intermittent, remote, and multi-system problems. *Scope · Test · Replicate · Execute · Assess · Mitigate.* Execute → Assess → Execute → Assess until you reach the solution.

→ <https://rivercaudle.com/stream/>

---

## F.05 — Schema on Read vs Write™

**Domain:** training and knowledge transfer

A training framework that builds on what skilled trades already know — flow systems, feedback loops, hierarchical organization — instead of replacing it. *Teaching the framework, not the facts.*

→ <https://rivercaudle.com/schema-on-read/>

---

## F.06 — OT Stability Doctrine

**Domain:** change management

In OT, change is risk and stability is security. Firmware longevity is a feature, not a flaw. The doctrine behind every refusal to patch on a Friday afternoon.

→ <https://rivercaudle.com/ot-stability/>

---

## F.07 — Industrial Independence Architecture *(external)*

**Domain:** architecture · sovereign-per-zone

One self-contained unit at every zone of an industrial network. Identical at every level. Scope is the only thing that changes. The fractal doesn't collapse at the top.

→ <https://industrialindependence.org/>

---

## How they fit together

The stack is small and they stack:

1. **SHIP** first — without a designed network, the rest is renovation on rotted wood.
2. **SECURE** second — apply IEC 62443 against the network you just built.
3. **RIVER** in the badge pocket — for daily troubleshooting at the cabinet.
4. **STREAM** on the desk — for the cases RIVER can't catch.
5. **Schema on Read** when you hire — so trade expertise becomes network expertise faster.
6. **OT Stability Doctrine** as your defense — when IT shows up Friday afternoon demanding you patch.

The **Industrial Independence Architecture** is the lens through which they all line up.

---

## License

All frameworks are released under the [Riverman Fair License v2.0](https://rivercaudle.com/license/) — forever free to plant operators and industrial workers; commercial use requires licensing.

---

*Document — Frameworks Index · Originator — R. Caudle · Rev. 01 · Issued Houston, Texas, 2026.05.11*