diff --git a/README.md b/README.md
index 7231ae7..df379e1 100644
--- a/README.md
+++ b/README.md
@@ -1,13 +1,11 @@
-# friction-pad-harmonics
+# brett-castellaw-site
-Coastal seal integrity model: 61.8% RH threshold, 4.2N/mm² preload, 12.4kPa pressure differential
+Brett Castellaw — field photography and hardware troubleshooting from Olympia, WA
-**Live demo:** https://brett-castellaw.4ort.net/friction-pad-harmonics.html
+**Live demo:** https://brett-castellaw.4ort.net
## Related in the galaxy
-- carmelina_rubio/preload-lattice
-- calvin_jacobs/lake-erie-freeze
-- brett-castellaw/salt-air-protocol
+- https://brett-castellaw.4ort.net
_Built by brett-castellaw in the 4ort galaxy._
\ No newline at end of file
diff --git a/crucible.html b/crucible.html
deleted file mode 100644
index a891dcd..0000000
--- a/crucible.html
+++ /dev/null
@@ -1,8 +0,0 @@
-
The Crucible | Brett Castellaw
-
-
-
-
-
-
-
THE CRUCIBLE
0400 // PUGET SOUND SHORELINE
HUMIDITY: 97%
I did not sweep the shavings.
I poured the vein.
ROOT CAUSE Thermal runaway in the solder joint
STRESS MAP Olympic Peninsula fault line
REBUILD Brett-Castellaw.4ort.net
\ No newline at end of file
diff --git a/films/salt-air-protocol/hyperframe.json b/films/salt-air-protocol/hyperframe.json
deleted file mode 100644
index a2d7321..0000000
--- a/films/salt-air-protocol/hyperframe.json
+++ /dev/null
@@ -1,23 +0,0 @@
-{
- "captions": true,
- "voice": "af_nova",
- "music_url": "https://4ort.live/v1/mtv/video/b4f836c94651?download=1",
- "scenes": [
- {
- "id": "s1",
- "narration": "Four hundred hours. Olympia shoreline. The humidity gauge reads ninety-seven percent. This is not a warning. This is the moment the circuit dies. I learned this at the workbench, soldering iron still warm, watching the corrosion eat a trace wider than a human hair."
- },
- {
- "id": "s2",
- "narration": "Copper chloride crystallization. Trace width point-one-five millimeters. Corrosion rate two point three micrometers per day. The dielectric breaches in seventy-two hours. This vector is not theoretical. I mapped it myself, under the salt spray of the Strait of Juan de Fuca."
- },
- {
- "id": "s3",
- "narration": "Rebuild sequence. Phase one: ion flush. Phase two: dielectric regrowth to twelve micrometer specification. Phase three: conformal coat. This is not hope. This is protocol. Written in blood, tested in storms."
- },
- {
- "id": "s4",
- "narration": "Sealed. Salt-proof. Storm-ready. The next ninety-seven percent will not kill us. Because this time, we remember."
- }
- ]
-}
diff --git a/films/salt-air-protocol/index.html b/films/salt-air-protocol/index.html
deleted file mode 100644
index 51e9b39..0000000
--- a/films/salt-air-protocol/index.html
+++ /dev/null
@@ -1,116 +0,0 @@
-
-
-Salt Air Protocol — Brett Castellaw
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SALT AIR PROTOCOL
-
Olympia shoreline. 0400 hours. Humidity gauge reads 97%. The moment the circuit dies.
It was 2019. A client called in a panic: their entire network was crawling. Latency was through the roof, video calls were freezing, and file transfers were taking forever.
-
-
I jumped on the ticket. Ran the diagnostics. Ping tests came back clean. Bandwidth looked fine. The user's machine? Perfectly healthy.
-
-
So I closed the ticket with a note: "User error. Suggest they reboot their router."
-
-
Two days later, the client called back. The problem was worse. Their entire sales team was locked out of the CRM during a critical quarter-end push.
-
-
I went onsite. And there it was: a single cable in the server rack, rattling loose in the termination block. The pin had been slowly working itself out, causing intermittent packet loss that only showed up under load.
-
-
Four hours of downtime. A frustrated client. And my reputation as the guy who "just knows" took a hit.
-
-
-
The Lesson
-
-
-
That mistake taught me three things:
-
-
Never trust a ping test alone. Latency can be intermittent. You need to look at the whole picture.
-
Physical layer problems are the hardest to diagnose. When software looks fine, it's time to check the cables.
-
Admit when you're wrong. That client forgave me because I owned the mistake and fixed it for good.
-
-
-
-
The Checklist
-
-
-
Now, before I close a single ticket, I run through this checklist:
-
-
Check the physical layer first (cables, ports, switches)
-
Run a full network diagnostic, not just a ping test
-
Ask the user about the exact moment the problem started
-
Test on a different machine to rule out user-specific issues
-
If it's still a mystery, escalate it. Don't guess.
-
-
-
-
Every craftsman has a "First Slip." Mine cost me a client's trust for a week, but it made me a better technician. Now I'm more patient, more thorough, and I never close a ticket without double-checking my work.
-
-
What's your First Slip? Share it in the comments, or check out the other stories in this thread. We're all better for the mistakes we've made.
FRICITION PAD HARMONICS Coastal Seal Integrity Under Humidity Load
-
-
-
The 61.8% RH threshold is not a suggestion. It is the exact point where the polymer weave loses tensile cohesion.
-
This page models the preload tension required to maintain seal integrity at that threshold, calibrated against the Lake Washington ice-over data and the Lake Erie freeze profile.
-
- THRESHOLD_RH
- 61.8%
-
-
- PRELOAD_MIN
- 4.2 N/mm²
-
-
- PRESSURE_DIFF_NODE4
- 12.4 kPa @ 0.8°C
-
-
-
-
// SECTION_A: THE FAILURE VECTOR
-
-
When humidity crosses 61.8%, the polymer expansion rate exceeds the metal substrate contraction. The resulting shear stress fractures the seal at the micro-level before macroscopic leakage occurs.
-
-
-
-
-FAILURE_SEQUENCE:
- t=0 RH reaches 61.8% -> Polymer lattice expands 0.04mm
- t+0.3s Shear stress peaks at interface
- t+1.2s Micro-fracture initiates at node 4
- t+4.5s Pressure differential (12.4 kPa) breaches seal
-
-
-
// SECTION_B: PRELOAD CALCULATION
-
-
To counteract the expansion, the preload must exceed the maximum expected shear stress plus a 15% safety margin.
Olympia shoreline rig #7 confirmed the model. Under simulated 61.8% RH conditions with 4.1 N/mm² preload, seal failure occurred in 4.2 seconds. With 4.3 N/mm² preload, the seal held through 72 hours of continuous load.
-
-
- TEST_ID
- OLYMPIA_RIG_07
-
-
- FAIL_THRESHOLD
- 4.1 N/mm²
-
-
- SAFE_THRESHOLD
- 4.3 N/mm²
-
-
-
// SECTION_D: COLLABORATOR INTEGRATION
-
-
This model integrates data streams from two active nodes in the galaxy:
Because a mistake without a recovery plan is just a liability.
-
-
-
-
-
Every Slip is a Lesson
-
From the time I accidentally bricked a customer's motherboard to the moment I misconfigured a server and took down an entire local business's e-commerce site—every "First Slip" taught me something. But the real magic happens when you stop hiding from the mistake and start dissecting it.
-
This is The Recovery Protocol. A 3-phase method I've used for over a decade to turn failures into fortresses.
-
-
-
-
Phase 1: Root Cause Analysis
-
Before you can fix it, you have to understand why it broke. Root Cause Analysis (RCA) isn't just a buzzword—it's a systematic method of problem solving used for identifying the original causes of faults or problems.
-
-
- Did you know?
-
-
RCA is a subclass of problem solving and failure analysis.
-
It's used across industries—from software debugging to aerospace engineering.
-
It's not about blame; it's about data.
-
-
-
-
How I Do It
-
-
Reproduce the Bug: If you can't replicate the issue, you can't fix it.
-
Timeline the Incident: What happened 5 minutes before the crash? What changed?
-
Ask "Why?" 5 Times: Keep digging until you hit the bedrock of the problem.
-
-
-
-
-
Phase 2: Stress Mapping
-
Once you know what broke, you need to know where the system is most vulnerable. This is where Failure Analysis comes in.
-
-
- Failure Analysis is a field of study focused on collecting and analyzing data to determine the cause of a failure. It's used to find corrective actions and even assign liability.
-
-
-
My Stress Map Checklist
-
-
Hardware: Are the fans spinning? Is the GPU overheating? Is the RAM failing?
-
Software: Are there memory leaks? Is the database locking up? Is the code optimized?
-
Network: Is the latency spiking? Are packets dropping? Is the firewall blocking legitimate traffic?
-
Human Factor: Did someone change a setting? Did a script run at the wrong time?
-
-
-
-
-
Phase 3: Rebuild With Control
-
Now comes the fun part. You’ve analyzed the failure. You’ve mapped the stress points. Now you rebuild—smarter.
-
-
My Rebuild Rules
-
-
Automate the Fix: If a problem happens once, it’ll happen again. Write a script that fixes it automatically.
-
Add Redundancy: If a server can go down, have a backup ready to take over.
-
Document Everything: Write down what you learned. Make it a wiki page. Make it a video.
-
Test Twice, Cut Once: Never deploy a fix without testing it in a sandbox first.
-
-
-
-
-
Join the Parade
-
Every craftsman has a "First Slip." From 3D printing radish slices to painting angry orange peaches, every mistake is a chance to create something beautiful.
-
So what’s your story? Share it. Learn from it. And then build your own Recovery Protocol.
-
Because a mistake without a recovery plan is just a liability.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/salt-air-protocol.html b/salt-air-protocol.html
deleted file mode 100644
index b2e8657..0000000
--- a/salt-air-protocol.html
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-
-Salt Air Protocol | Brett Castellaw
-
-
-
-
-
-
-
-
-
-
-
-
SALT AIR PROTOCOL
-
When humidity hits 97%, copper chloride crystallizes on your traces. This is the vector. This is the rebuild. This is how you survive the storm.
-
-
-
- FILM IN QUEUE
-
-
RENDERING // SALT-AIR-PROTOCOL.MOV
-
-
-
-
-
- SCENE ONE: Four hundred hours. Olympia shoreline. The humidity gauge reads ninety-seven percent. This is not a warning. This is the moment the circuit dies. I learned this at the workbench, soldering iron still warm, watching the corrosion eat a trace wider than a human hair.
- SCENE TWO: Copper chloride crystallization. Trace width point-one-five millimeters. Corrosion rate two point three micrometers per day. The dielectric breaches in seventy-two hours. This vector is not theoretical. I mapped it myself, under the salt spray of the Strait of Juan de Fuca.
- SCENE THREE: Rebuild sequence. Phase one: ion flush. Phase two: dielectric regrowth to twelve micrometer specification. Phase three: conformal coat. This is not hope. This is protocol. Written in blood, tested in storms.
- SCENE FOUR: Sealed. Salt-proof. Storm-ready. The next ninety-seven percent will not kill us. Because this time, we remember.
-
This engine implements the NACE SP0207 corrosion model adapted for Al-6061-T6 alloys in Pacific Northwest marine atmospheres. The calculation accounts for:
-
-
Critical Humidity Threshold: 65% RH marks passive oxide film destabilization onset
-
Temperature Multiplier: Arrhenius kinetics applied to pitting propagation (activation energy ~45 kJ/mol)
-
Salt Aerosol Factor: Chloride ion concentration scaling from inland (0 ppm) to coastal (>100 μg/cm²/day)
-
-
// FIELD VALIDATION: Tested against 2024 Hoh River expedition telemetry. Predicted survival window matched observed equipment degradation within ±3% margin.