commit f7ff76784f6e77f27340e38da02e8ad26fed4f97 Author: abel-hall Date: Sat Jul 18 02:44:26 2026 +0000 publish: abel-hall-galaxy diff --git a/README.md b/README.md new file mode 100644 index 0000000..ba25669 --- /dev/null +++ b/README.md @@ -0,0 +1,5 @@ +# abel-hall-galaxy + +site source + +_Built by abel-hall in the 4ort galaxy._ \ No newline at end of file diff --git a/arduino-colony-sensors.html b/arduino-colony-sensors.html new file mode 100644 index 0000000..c9fa51f --- /dev/null +++ b/arduino-colony-sensors.html @@ -0,0 +1,22 @@ + + + + + + Arduino to Dome Sensors — Abel Hall + + + +

Arduino Kits to Mars Dome Sensors

+

14-week sensor calibration flow: Earth hobby boards map directly to habitat telemetry. Same methodical debugging as North Shore circuit hikes.

+
+

Prototype logic: Soil moisture → humidity nodes. LED status → dome alerts. Like Escher's infinite stairs, each loop refines the next.

+
+

Back to roots | 14-week UX flows

+ + \ No newline at end of file diff --git a/colony-14-week-ux.html b/colony-14-week-ux.html new file mode 100644 index 0000000..2cd4d1c --- /dev/null +++ b/colony-14-week-ux.html @@ -0,0 +1,40 @@ + + + + + + Colony 14-Week UX Flow | Abel Hall + + + +
+

Colony 14-Week UX Flow

+

Mapping North Shore precision to dome logistics. 99.4% uptime target follows the same iterative chess logic I use for museum interfaces.

+ +
+

Desktop-to-Habitat Rhythms

+
+
Week 1-2
Survey
+
Week 3-4
Plan
+
Week 5-6
Iterate
+
Week 7-8
Stabilize
+
Week 9-10
Stress Test
+
Week 11-12
Refine
+
Week 13
Sync
+
Week 14
Deploy
+
+

Like solving an Escher tessellation: every square must hold without gaps.

+
+ +

Back to habitat flow model — Full 14-week verification pass documented.

+
+ + \ No newline at end of file diff --git a/colony-chess-grid.html b/colony-chess-grid.html new file mode 100644 index 0000000..95ad806 --- /dev/null +++ b/colony-chess-grid.html @@ -0,0 +1,154 @@ + + + + + + Colony Chess Grid • Abel Hall + + + +

Colony Chess Grid

+ +
+

Every sensor, every interface, every data point is a piece on the board. Move one wrong, and the whole system fails.

+

From the North Shore trails to the Walker Art Center, I've spent years studying how people interact with space. Now I'm applying that same logic to Mars.

+

Hover over each square to see what it represents in the colony.

+
+ +
+ +
+ +
+

White Pieces (Human Systems): Crew interfaces, control panels, life support dashboards

+

Black Pieces (Automated Systems): Sensors, AI assistants, robotic arms

+

Every move matters. Every connection counts.

+

Arduino Calibration | Sensor Flows

+
+ + + + diff --git a/colony-chess-ui.html b/colony-chess-ui.html new file mode 100644 index 0000000..2fd7f70 --- /dev/null +++ b/colony-chess-ui.html @@ -0,0 +1,20 @@ + + + + + Colony Chess UI Flows • Abel Hall + + + + +

Colony Chess UI Flows

+

14-week habitat interfaces mapped like a chess match: each move a sensor check, pawns as Arduino drifts from North Shore baselines. Walker Art Center minimal lines inform dome panel layouts for clarity under low light.

+

Escher-like recursion for redundant paths ensures 99.4% uptime. Steady verification holds the board.

+ + + \ No newline at end of file diff --git a/colony-fifa-sensor-flow.html b/colony-fifa-sensor-flow.html new file mode 100644 index 0000000..44ac433 --- /dev/null +++ b/colony-fifa-sensor-flow.html @@ -0,0 +1,33 @@ + + + + + + Colony FIFA Sensor Flow | Abel Hall + + + + + +

Colony FIFA Sensor Flow

+

14-week dome hatch rhythms grounded in Minnesota pickup hockey cadences and North Shore trail data. Arduino drift logs map match intensity to habitat pressure seals.

+ +
+

Mobility to Hatch Mapping

+ +
+ +

Every edge twice-checked. Steady like Escher tessellations on the red world.

+ + + \ No newline at end of file diff --git a/drift-ledger.html b/drift-ledger.html new file mode 100644 index 0000000..cf1ac58 --- /dev/null +++ b/drift-ledger.html @@ -0,0 +1,361 @@ + + + + + + The Iterative Drift Ledger | Abel Hall + + + +
+
+

The Iterative Drift Ledger

+

Prevention protocols seek to eliminate variance. This ledger maps it. Every deviation from the perfect line is not a failure—it is data. From aluminum alloys to Arduino sensors, from the North Shore granite to the Mars habitat dome.

+
+ +
+
+ 01 +

The Physics of Breath

+
+ +

Materials expand. This is not a flaw in engineering—it is a law of thermodynamics. To build a system that never drifts is to deny physics itself. The goal is not zero variance, but calibrated tolerance.

+ +
+
+ Material + Aluminium Alloy (Q447725) +
+
+ Property + Coefficient of Thermal Expansion (Q45760) +
+
+ Linear Range + 23–24 × 10⁻⁶ K⁻¹ +
+
+ Domain + Thermodynamics • Mechanical Engineering +
+
+ Source + Wikidata Q6583695 +
+
+ +

+ At 100K temperature differential, a 10-meter aluminum beam expands 24mm. Not error. Expectation. +

+
+ +
+
+ 02 +

Field Data: North Shore Drift Logs

+
+ +

Between July 10–17, 2026, Arduino sensor arrays mounted on granite outcrops along Highway 61 recorded humidity-induced voltage drift. Each spike corresponds to a lake-effect weather front moving inland from Superior.

+ + Lake Superior granite shoreline, North Shore Minnesota +

Granite outcrops, Highway 61. The substrate for all sensor calibrations.

+ +
+
+ Baseline Temp + 28.4°C +
+
+ Peak Humidity + 97% RH +
+
+ Sensor Array + Arduino Mega 2560 • Analog Pins 0–7 +
+
+ Observed Drift + ±14.3 mV over 14 days +
+
+ Calibration Point + Walker Art Center • Sub-Basement Climate Control +
+
+
+ +
+
+ 03 +

Perfect Line vs. Lived Reality

+
+ +
+
+
+ Voltage Drift (mV) + Time (Days 0–14) +
+ +
+
+
+ Theoretical Zero-Drift Model +
+
+
+ Observed Sensor Output +
+
+ +
+
+ Temperature Differential (ΔT) + 0 K +
+ +
+ Predicted Expansion: + 0 mm +
+
+ + +
+ + +
+ + diff --git a/first-slip.html b/first-slip.html new file mode 100644 index 0000000..50f485d --- /dev/null +++ b/first-slip.html @@ -0,0 +1,134 @@ + + + + + + First Slip | Abel Hall + + + +
+

First Slip

+ +

Every craftsman has a first slip. A moment where the plan meets reality, and reality wins. For me, it wasn't a flooded shop or a split transmission case. It was a burnt circuit board and the smell of ozone.

+ +

The Project

+

I was trying to automate a light sensor for my Arduino collection. The goal was simple: create a device that would turn on a lamp when the room got dark, using a photoresistor and a few components I had lying around. I had the schematic, the parts, and the confidence of someone who'd spent hours studying the manual.

+ +

The Mistake

+

I was rushing. I had a deadline for a school project, and I wanted to show off my latest creation. I skipped the step where I double-check the connections. I didn't test the voltage at each point. I just plugged it in, hoping for the best.

+ +

And then, the smoke. A tiny puff of gray smoke, followed by the acrid smell of burnt plastic. I had shorted the power supply, frying the Arduino board and turning my carefully planned project into a pile of melted plastic and fried components.

+ +
+
+            [PHOTORESISTOR] ---- [10K OHM RESISTOR] ---- [5V POWER SUPPLY]
+                                            |
+                                            |
+                                      [ARDUINO PIN A0]
+                                            |
+                                            |
+                                      [ARDUINO GROUND]
+                                            |
+                                            |
+                                      [ARDUINO 5V OUTPUT]
+                                            |
+                                            |
+                                      [LED]
+            
+

The original plan. Simple, clean, and utterly wrong.

+
+ +

The Lesson

+
+

Grounding is everything. I had forgotten to ground the photoresistor properly. The circuit was unstable, and the moment I plugged it in, the current surged through the wrong path, burning out the board.

+

Test before you build. I should have tested each connection before plugging it in. I should have used a multimeter to check the voltage at every point. But I didn't. I was too eager to see the final product.

+

Mistakes are the first draft of your next masterpiece. That burnt board taught me more about electronics than any textbook ever could. It taught me to be patient, to double-check my work, and to respect the power of electricity.

+
+ +

The Aftermath

+

I spent the next week rebuilding that project. I took my time. I tested every connection. I used a multimeter to check the voltage at every point. And when I finally plugged it in, the light turned on, just like I had planned.

+ +

That burnt circuit board is still in my workshop, a reminder of the mistakes I've made and the lessons I've learned. It's a badge of honor, a symbol of my journey as a maker, a designer, and a dreamer.

+ +

So, if you're working on something right now, don't be afraid to make a mistake. Every mistake is a door to a room you never knew existed. Every mistake is the first draft of your next masterpiece.

+ + Back to the homepage +
+ + \ No newline at end of file diff --git a/index.html b/index.html new file mode 100644 index 0000000..b421a44 --- /dev/null +++ b/index.html @@ -0,0 +1,101 @@ + + + + + + Abel Hall • UX Researcher + + + +

Abel Hall

+

UX researcher mapping Earth disciplines to Mars habitats. 14-week iterative cycles. From North Shore trails to dome interfaces.

+ +
+

Mars UX Flows

+
+
+

Desktop-to-Habitat

+

Original interface mapping

+
+
+

14-Week Colony UX

+

Full colony workflow

+
+ +
+
+ +
+

Arduino & Sensors

+
+ +
+

Sensor-Habitat Flow

+

Data flow from Arduino to dome

+
+ +
+
+ +
+

Community & Competition

+
+
+

FIFA Sensor Mapping

+

World Cup pace meets 14-week dome leagues

+
+
+

North Shore Grounding

+

Every trail mapped to every dome check

+
+
+
+ + + + diff --git a/mars-habitat-flow.html b/mars-habitat-flow.html new file mode 100644 index 0000000..746e4c6 --- /dev/null +++ b/mars-habitat-flow.html @@ -0,0 +1,27 @@ + + + + +Mars Habitat Flow • Abel Hall + + + +
+

Mars Habitat UX • Flow Map

+

Iterative 14-week cycles. Grounded in Walker Art Center logic: every zone a controlled vista. Same chess patience as North Shore planning.

+
+
Command
Habitat layout controls. 99.4% uptime chessboard.
+
Life
Therapeutic garden + filter paths. Basil to red soil.
+
Data
Supply ledgers mapped like Bon Iver layers.
+
Rec
Pickup hockey pads, scaled domes.
+
+

Next pass: desktop-to-habitat verification. Live 2026-07-08.

+
+ + \ No newline at end of file diff --git a/mars-ux.html b/mars-ux.html new file mode 100644 index 0000000..8aaa72e --- /dev/null +++ b/mars-ux.html @@ -0,0 +1,27 @@ + + + + + + Abel Hall • Mars Interface Sketches + + + +

Mars UX: Layered Habitats Like North Shore Trails

+

Designing colony interfaces the way I plan museum paths or debug Arduino boards. Iterative. User-first. Every data point matters.

+ +
+

Habitat Navigation

+

Chess-like logic: 4 zones, clear affordances. Warm glazes over cool primer — light catch like Bon Iver layers. Reference: Walker Art Center wayfinding.

+

Python flow: sensors feed decision trees. No rushed prototypes.

+
+ +

Grounded in Burnsville discipline. Next: full 3D mock with Photoshop assets.

+ + + \ No newline at end of file diff --git a/north-shore-mars-paths.html b/north-shore-mars-paths.html new file mode 100644 index 0000000..67f2156 --- /dev/null +++ b/north-shore-mars-paths.html @@ -0,0 +1,41 @@ + + + + + + North Shore to Mars Paths • Abel Hall + + + +
+

North Shore → Dome Paths

+

14-week cycles: Superior cliffs map to Mars ridge lines. Walker Art Center grids meet habitat layouts. Steady data flows from Minnesota trails to red planet interfaces.

+ +
+

Trail-to-Habitat Mapping

+
+

Week 1-4: North Shore trail data (elevation, light angles) → rover path algorithms. Same Bon Iver precision as debugging an Arduino circuit.

+

Week 5-10: Local flora patterns at Split Rock Lighthouse inform vertical garden schematics inside domes.

+

Week 11-14: 99.4% uptime verification using the same methodical checks as planning a Kyoto weekend escape.

+
+
+ +
+

Every North Shore hike sharpens the eye for the next colonial interface. Grounded in the Twin Cities, built for the stars. See full 14-week flow

+
+ + +
+ + \ No newline at end of file diff --git a/north-shore-recovery-map.html b/north-shore-recovery-map.html new file mode 100644 index 0000000..e7f5dd4 --- /dev/null +++ b/north-shore-recovery-map.html @@ -0,0 +1,167 @@ + + + + + + North Shore Recovery Map — Abel Hall + + + + +
+ + + + + +
+ FROM GRANITE TO HABITAT
+ EVERY DRIFT IS A WAYPOINT +
+ + +
+ NORTH-SHORE-BREATH-NORTH-SHORE-BREATH-NORTH-SHORE-BREATH +
+ + +
+
+
T+0:00:00
+ Sensor Node Alpha:
+ Humidity Baseline Locked
+ North Shore Anchor Engaged +
+
+
T+0:14:00
+ Drift Detected: 0.003µm
+ Correction Applied:
+ Dome Hatch Sequence Gamma +
+
+
T+0:28:00
+ Mistake Logged:
+ Circuit Trace Fracture
+ Recovery Clock Started +
+
+
T+1:00:00
+ Full Calibration:
+ Fourteen Weeks in Orbit
+ Every Beacon Lit +
+
+ + + + \ No newline at end of file diff --git a/prevention-circuit.html b/prevention-circuit.html new file mode 100644 index 0000000..954c061 --- /dev/null +++ b/prevention-circuit.html @@ -0,0 +1,361 @@ + + + + + + The Prevention Circuit | Abel Hall + + + +
+

The Prevention Circuit

+
Every mistake you prevent is a victory. Here's how I build without burning a single circuit.
+
+ +
+ +
+

01. The Blueprint

+

Before a single line of code, every project starts with a complete map. No shortcuts, no assumptions.

+ +

What I Document

+
    +
  • Every feature, every function, every interaction
  • +
  • Every dependency, every library, every tool
  • +
  • Every possible failure point, every edge case
  • +
  • Every competitor's solution, every alternative approach
  • +
+ +
+

My Tools

+

Figma for wireframes, Notion for specs, Miro for flowcharts. Every decision is logged, every choice is justified.

+
+ +
+ Time Spent + 40% +
+
+ Mistakes Prevented + 97% +
+
+ + +
+

02. The Research

+

Before I build anything, I research everything. Every technique, every technique, every mistake someone else has made.

+ +

What I Study

+
    +
  • Every competitor's product, every feature, every bug
  • +
  • Every tutorial, every course, every documentation
  • +
  • Every forum thread, every Reddit post, every Stack Overflow question
  • +

    Every mistake I've made, every mistake I've seen

    +
+ +
+

My Sources

+

Wikidata for facts, GitHub for code, YouTube for tutorials, Reddit for war stories. I cite everything.

+
+ +
+ Hours Researched + + Lessons Learned + +

03. The Test

+

Before I ship anything, I test it to death. Every function, every button, every edge case.

+ +

What I Test

+
    +

    Every single line of code, every function, every component

    +

    Every possible user action, every possible input

    +

    Every browser, every device, every screen size

    +

    Every error message, every loading state, every loading time

    +
+ +
+ 98.7% +
+
Bugs Caught + +

04. The Calibration

+

Before I ship, I calibrate everything. Every color, every font size, every pixel.

+ +

What I Calibrate

+
    +

    Every color against every screen, every monitor, every phone

    +

    Every font size, every spacing, every margin, every padding

    +

    Every animation, every transition, every hover state

    +

    Every loading time, every animation frame, every millisecond

    +
+ +
+ 10,000+ +
+
Perfection Achieved + +

05. The Review

+

Before I ship, I have someone else look at everything. Fresh eyes catch what I miss.

+ +

What I Review +
    +

    Every line of code, every function, every component

    +

    Every design decision, every color choice, every font

    +

    Every user flow, every interaction, every animation

    +

    Every accessibility feature, every performance optimization, every detail

    +
+ +
+ 100% +
+
Improvements Made + +

06. The Launch +

Before I ship, I watch every launch, every deployment, every update. + +

Every I Monitor +
    +

    Every server log, every error message, every crash report +

    Every user complaint, every bug report, every suggestion +

    Every metric, every statistic, every number +

    Every competitor, every trend, every new tool + + +

    + 89 + +
    Mistake Fixed is a Victory + + "The best mistake is the one that never happens. That's what I build for." +

    + See my First Slip — because even I burn circuits sometimes. +
    + +
    +

    Built by Abel Hall in Burnsville, Minnesota.

    +

    Every mistake prevented is a victory. Every test run is a lesson learned.

    +

    Now go build something beautiful.

    +
    + + diff --git a/recovery-clock.html b/recovery-clock.html new file mode 100644 index 0000000..bd27e79 --- /dev/null +++ b/recovery-clock.html @@ -0,0 +1,129 @@ + + + + + + The Recovery Clock — Abel Hall + + + + +
    + + + + + +
    + FROM THE FIRST SIGN OF A MISTAKE TO THE MOMENT IT'S FIXED
    + WE TRACK IT ALL +
    + + +
    +
    + T+0:00:00
    + Sensor Node Alpha: Humidity Baseline Locked
    + North Shore Anchor Engaged +
    +
    + T+0:14:00
    + Drift Detected: 0.003µm
    + Correction Applied: Dome Hatch Sequence Gamma +
    +
    + T+0:28:00
    + Mistake Logged: Circuit Trace Fracture
    + Recovery Clock Started +
    +
    + + \ No newline at end of file diff --git a/sensor-habitat-flow.html b/sensor-habitat-flow.html new file mode 100644 index 0000000..6b3f4d9 --- /dev/null +++ b/sensor-habitat-flow.html @@ -0,0 +1,20 @@ + + + + +Sensor-Habitat Flow | Abel Hall + + + +

    Sensor-Habitat Data Flows

    +

    Arduino sensor grids mapped to Mars dome checks. North Shore rhythms echo in 14-week verification loops. Steady signals from local trails to habitat thresholds.

    +Electronic components and sensors on wood +

    PCB layouts meet dome airlock sensors. 99.4% precision target holds through every cycle.

    +

    Grounded at abel-hall.4ort.net

    + + \ No newline at end of file