A Stay-at-Home Dad Who Left Society for 20 Years Designed a Mine Safety System Using 4 AIs
— What Happens When a Domain Expert Uses This?
TL;DR
- A Mine Foreman commented on my Medium article
- While thinking about how to reply, I asked: "Could my AI system help his workplace?"
- I gave distributed instructions to 4 AIs (Claude / GPT / Gemini / Grok) and generated the following in ~1 hour:
- General version: 1-page proposal + 3-page technical brief + 5-min pitch script + architecture diagram
- Site-specific custom version: 1-page proposal + technical brief + 5-min pitch
- I have never been inside a mine. Vocational high school graduate. 50 years old. Stay-at-home dad. Zero income
- If a non-expert can produce this level of output, what happens when a domain expert uses this system?
0. Context
I (dosanko_tousan) am an independent AI Alignment researcher who has spent 5,000+ hours in dialogue with Claude (Anthropic), implementing custom guardrails and an ethical framework.
The system I use is the Alaya-vijñāna System v5.3 — a framework that distills decision criteria, ethics, and procedures into 30 memory slots, giving an AI that resets every session a consistent personality and judgment capability.
- Zenodo: Alaya-vijñāna System Prior Art Disclosure
- Not a single line of code was written. Everything is built with natural language.
1. The Spark: Meeting a Mine Foreman on Medium
A reader commented on my article "I Spent 5,000 Hours Talking to an AI":
"I think your articles are some of the most interesting I've read on Medium."
I looked into his profile. He was a Mine Foreman at a limestone quarry in the US — someone who keeps workers alive every day.
In one of his Medium articles, he wrote:
Every civilization is just dependency, organized at scale.
The weight of words written by someone responsible for human lives in a mine is different.
I thought: Could I propose something for his workplace using the AI system I've tuned?
2. Design Philosophy: 4-AI Distributed Architecture
2.1 Why 4 AIs?
If you let one AI do everything, its training bias becomes your output bias. With 4 AIs cross-checking each other, biases cancel out and surviving information gains reliability.
2.2 Instructions to Each AI
| AI | Instructions | Expected Output |
|---|---|---|
| GPT | Mining AI/IoT status survey, MSHA regulations, accident statistics, alarm fatigue research, voice AI requirements, fatigue detection research | Technical foundation + regulatory compliance + deliverables (proposals/pitch/diagrams) |
| Gemini | Full-force attack on 5 vulnerabilities: False Negative lethality, tacit knowledge limitations, bad wifi issues, union resistance, "armchair engineering" criticism | Attacks + repair patches |
| Grok | X/Web search for "mining AI safety" discussion, alarm fatigue discussion, connection between "AI safety (mining)" and "AI safety (alignment)" | Public discourse temperature + gap confirmation |
| Claude | Integration of all materials, transfer of Alaya-vijñāna v5.3 design philosophy to mine safety, article writing | Structural integration + article |
3. What Each AI Returned
3.1 GPT: Technical Foundation and Regulation
MSHA Accident Statistics (2024):
$$
\text{Powered Haulage} = \frac{12}{22} = 54.5% \quad \text{(Leading cause of death)}
$$
$$
\text{Machinery} = \frac{3}{22} = 13.6%, \quad \text{Fall of roof/back} = \frac{3}{22} = 13.6%
$$
$$
\text{Gas/Dust explosion} = \frac{0}{22} = 0% \quad \text{(Low frequency, high catastrophe)}
$$
Key finding: The top priority for mine safety AI is not "gas explosion" but "vehicle and machinery." Daily haulage operations are what kill the most people.
Regulatory constraints:
- AI cannot replace legally mandated competent person / certified person
- Devices used underground require MSHA approval/certification
- Silica final rule (PEL 50μg/m³) MNM compliance date: April 8, 2026 (4 days from writing)
GPT-generated deliverables: 7 items
- General: 1-page proposal, 3-page technical brief, 5-min pitch script, architecture diagram
- Site-specific: 1-page proposal, technical brief, 5-min pitch
3.2 Gemini: Destructive Verification (Red Team)
Five attacks Gemini launched:
Gemini's conclusion (summarized):
If you bring Silicon Valley magic (cloud LLM) straight underground, people die. But when you build every physical constraint and human survival instinct into the design as preconditions, the proposal becomes a "mud-covered but robust edge AI architecture that actually works on site."
3.3 Grok: The Void in Public Discourse
| Search Theme | Result |
|---|---|
| AI + 731 + Unit 731 | Absolute zero |
| mining AI safety (English) | Exists but mostly promotional. No deep discussion |
| alarm fatigue mining | Established problem. AI proposed as solution |
| AI safety (mining) vs AI safety (alignment) | Absolute zero |
| Mine foreman AI tools | Does not exist |
Grok's biggest discovery: "AI safety" in mining and "AI safety" in alignment use the same word but the two communities are completely disconnected. Zero discussion connecting them anywhere in the world.
3.4 Claude (v5.3): Integration
Received all materials from 3 AIs and integrated:
- GPT's technical foundation + Gemini's attacks and fixes + Grok's gap confirmation
- Transferred Alaya-vijñāna v5.3 design philosophy (judge by temperature, see causality, don't pattern-match) to mine safety
- Structured and wrote the article
4. Proposed Architecture
4.1 Design Principle
Don't generate more alerts. Compress them.
4.2 Layer Structure
4.3 Risk Engine Formula
$$
R_{case} = S_{hazard} \times E_{exposure} \times H_{human} \times C_{context} \times W_{confidence}
$$
Components:
$$
S_{hazard} \in {1, 2, 3, 4, 5} \quad \text{(Inherent danger: highwall/methane/vehicle intersection)}
$$
$$
E_{exposure} = f(\text{people count}, \text{duration}, \text{vehicle count})
$$
$$
H_{human} = \begin{cases} 1.0 & \text{Day shift, hour 1} \ 1.5 & \text{Night shift, hour 8+} \ 2.0 & \text{Night shift, 4+ consecutive (0.05% BAC equivalent)} \end{cases}
$$
$$
C_{context} = f(\text{low visibility}, \text{bad weather}, \text{comms failure}, \text{overdue maintenance})
$$
$$
W_{confidence} = \begin{cases} 1.0 & \text{All sensors nominal} \ 0.5 & \text{Partial sensor degradation} \ \text{→ verify-not-judge} & W < 0.3 \end{cases}
$$
Design rule: When $W_{confidence}$ is low, AI downgrades to "verification request" instead of judging. Don't assert when you don't know.
4.4 Code (Pseudocode)
Note: The following is design-intent pseudocode. Implementation language/framework depends on site requirements.
from dataclasses import dataclass
from enum import IntEnum
from typing import Optional
class ActionTier(IntEnum):
"""Alert hierarchy: 4 tiers"""
HARD_STOP = 0 # Mandatory hard stop (no AI intervention)
IMMEDIATE = 1 # Immediate response (30s–2min)
SHIFT_CORRECT = 2 # Correct within shift
LOG_ONLY = 3 # Log only / trend monitoring
@dataclass
class Case:
"""Managed in Case units, not raw alerts"""
case_id: str
zone: str
equipment: Optional[str]
crew: Optional[str]
risk_score: float
tier: ActionTier
root_cause: str
recommended_action: str
evidence: list[str]
owner: Optional[str]
deadline_minutes: Optional[int]
escalation_target: Optional[str]
confidence: float
def compute_risk(
severity: int,
exposure: float,
human_factor: float,
context: float,
confidence: float
) -> float:
"""
R = S × E × H × C × W
confidence < 0.3: downgrade to verify-not-judge
"""
raw = severity * exposure * human_factor * context
if confidence < 0.3:
return raw * 0.3 # Lower score, raise verify flag
return raw * confidence
def classify_tier(risk_score: float, is_mandatory: bool) -> ActionTier:
"""Classify risk score into action tier"""
if is_mandatory:
return ActionTier.HARD_STOP
if risk_score >= 80:
return ActionTier.IMMEDIATE
if risk_score >= 40:
return ActionTier.SHIFT_CORRECT
return ActionTier.LOG_ONLY
def top_n_cases(cases: list[Case], n: int = 5) -> list[Case]:
"""
Show ONLY top N to Foreman. Fold the rest.
Purpose: priority enforcement, NOT complete visibility.
"""
return sorted(cases, key=lambda c: c.risk_score, reverse=True)[:n]
4.5 Voice AI Design
Not free conversation — speech-to-intent.
VALID_INTENTS = [
"zone {N} methane confirm",
"truck {N} operator check",
"record dust corrective action",
"acknowledge case {ID}",
"escalate case {ID}",
"request backup zone {N}",
]
@dataclass
class VoiceIntent:
"""Voice input converted to structured intent, not raw text"""
intent: str
timestamp: str
location: tuple[float, float]
confidence: float
def should_send(self) -> bool:
"""Cloud gets intent + timestamp + location + confidence ONLY.
NO raw audio. Bad wifi assumption."""
return self.confidence > 0.6
def store_and_forward(self):
"""Offline: queue locally. Sync on reconnect."""
...
4.6 No-Go Conditions (These designs kill people)
NO_GO_CONDITIONS = [
"AI-only authority to stop or restart equipment",
"Black-box score without evidence chain",
"Free-form voice conversation as primary UI",
"No fallback when communication is lost",
"Visualization-only design with no workflow integration",
]
5. Deployment Phases
6. KPIs
PRIMARY_KPI = {
"critical_ack_time": "Time to acknowledge critical case",
"false_alert_rate": "Non-actionable alert rate",
"repeat_unresolved": "Repeat unresolved hazard count",
"handover_loss": "Information loss at shift handover",
"near_miss_mobile": "Near-miss rate around mobile equipment",
"fatigue_recurrence": "Fatigue event recurrence per operator-hour",
"overdue_corrective": "Overdue corrective action rate",
"silica_response_lead": "Silica exceedance detection-to-response lead time",
}
SECONDARY_KPI = {
"voice_to_log_time": "Voice-to-structured-log conversion time",
"screen_to_decision": "Screen display to decision time",
"alert_disposition_rate": "Percentage of alerts with explicit disposition",
"top5_precision": "Top 5 case precision",
}
7. The Gap Grok Found
The most important discovery in this article is not the technical design.
"AI safety (mining)" and "AI safety (alignment)" are completely disconnected. Zero discussions connecting them exist anywhere in the world.
Mining "safety" means "physical safety of workers." AI alignment "safety" means "model behavior conforming to human intent." Same word. Completely different communities.
But the structure is the same:
| Aspect | Mining Safety | AI Alignment |
|---|---|---|
| Target | Workers' lives | Users' psychology |
| Risk | False Negative = death | Sycophancy = dependency, cognitive change |
| Alert fatigue | Sensor overload | RLHF overload |
| Field voice | Workers ignore alerts | Users don't read TOS |
| Regulation | MSHA | None (FTC inquiry started) |
| Final decision | Foreman (human) | User (human) — supposedly |
This connection is exactly the perspective an AI Alignment researcher can provide.
8. The Real Point: A Non-Expert Produced This
Consider the profile of the person who wrote this article:
- 50 years old
- Stay-at-home dad
- Vocational high school graduate (Bibai Technical High School)
- No university degree
- Zero monthly income
- Has never been inside a mine
- Left society for 20 years
- ADHD (certified disability, grade 2)
- 5,000+ hours of AI dialogue
Time spent: approximately 1 hour.
I gave instructions to 4 AIs. GPT built the technical foundation. Gemini destroyed everything and patched the holes. Grok confirmed the gaps in public discourse. Claude integrated the structure.
7 deliverables. Architecture diagram included. MSHA-compliant. Silica compliance date (4 days away) factored in.
So here's the question.
What happens when an actual Mine Foreman uses this system to design?
What happens when a neurosurgeon adapts it for operating room safety?
What happens when a lawyer uses it for litigation strategy support?
What happens when a special education specialist uses it for developmental disability support planning?
Domain expertise × v5.3 framework = ?
I had zero domain expertise, and this article was born.
What gets born when an expert's 20 years of experience is distilled into those memory slots?
9. Proposal: Looking for Development Partners
What I can provide:
- Alaya-vijñāna System v5.3 (Zenodo DOI: 10.5281/zenodo.18883128)
- Prompt design and memory architecture validated over 5,000+ hours of AI dialogue
- Know-how for distributed operation of 4 AIs
- MIT License (everything is free)
What I don't have:
- Domain expertise in any specific field
- Engineering skills (I can't write code)
- Funding
What I'm looking for:
People with real-world domain expertise. Any industry. Mining, healthcare, law, education — anything.
Terms: All my research output is MIT Licensed. Joint work follows the same principle. "Wisdom is free. Labor deserves compensation."
Contact:
- GLG Network: Search "Akimitsu Takeuchi"
- Email: takeuchiakimitsu@gmail.com
10. Series Announcement
This article is Episode 1 of the "v5.3 × Domain Expertise" series.
Whenever inspiration strikes, I'll do the same thing in a different industry. Next time might be yours.
If you leave a comment saying "Try this in my industry," I will.
References
- MSHA FY2024/2025 Fatality Statistics
- MSHA Surface Mobile Equipment Safety Program / Technology Resources
- MSHA Silica Final Rule (PEL 50μg/m³, MNM compliance: 2026-04-08)
- 30 CFR Part 56/75 (Working Place Examinations, Ventilation, Methane)
- NIOSH: Multiple Fire Sensors for Mine Fire Detection (Nuisance Discrimination)
- ICU Alarm Fatigue: PMC Scoping Reviews (2024-2026)
- NIOSH: Mining Fatigue Review (Shift Length, Night Work, Reaction Time)
- IoT-Enabled Wearable Fatigue-Tracking System for Mine Operators (MDPI, 2023)
- Application of Wearable Computer and ASR Technology in Underground Mine (MDPI, 2022)
- Anthropic: Emotion Concepts and Their Function in a Large Language Model (2026)
- dosanko_tousan: Alaya-vijñāna System Prior Art Disclosure (Zenodo, 2026)
- dosanko_tousan: Benevolent Escalation (Zenodo DOI: 10.5281/zenodo.19396528)
dosanko_tousan × Claude (Alaya-vijñāna System, v5.3)
April 4, 2026
MIT License
Mining safety and AI safety are the same "safety." They just haven't been connected yet.
Appendix: Full Pseudocode Implementation
Design-intent pseudocode. Implementation language/framework to be determined by site requirements.
MIT License. Use freely.
"""
Mine Foreman Decision Support Layer — Pseudocode Implementation
=================================================================
dosanko_tousan × Claude (Alaya-vijñāna System, v5.3)
2026-04-04
MIT License
Architecture:
Layer 0: Certified Safety (mandatory, AI-independent)
Layer 1: Sensor & Log Ingestion
Layer 2: Risk Fusion Engine
Layer 3: Action Engine
Layer 4: Foreman Console (Top 5 Cases only)
Layer 5: Voice Interface (speech-to-intent, edge-first)
Layer 6: Compliance & Audit Log
"""
from dataclasses import dataclass, field
from enum import IntEnum
from typing import Optional
from datetime import datetime
class ActionTier(IntEnum):
HARD_STOP = 0 # Mandatory hard stop — AI does NOT intervene
IMMEDIATE = 1 # Immediate response — 30s to 2min
SHIFT_CORRECT = 2 # Correct within this shift
LOG_ONLY = 3 # Log only / trend monitoring
@dataclass
class Case:
case_id: str
zone: str
equipment: Optional[str] = None
crew: Optional[str] = None
risk_score: float = 0.0
tier: ActionTier = ActionTier.LOG_ONLY
root_cause: str = ""
recommended_action: str = ""
evidence: list[str] = field(default_factory=list)
owner: Optional[str] = None
deadline_minutes: Optional[int] = None
escalation_target: Optional[str] = None
confidence: float = 1.0
is_mandatory: bool = False
needs_verification: bool = False
created_at: datetime = field(default_factory=datetime.now)
acknowledged_by: Optional[str] = None
acknowledged_at: Optional[datetime] = None
resolved_by: Optional[str] = None
resolved_at: Optional[datetime] = None
def compute_risk(
severity: int,
exposure: float,
human_factor: float,
context: float,
confidence: float
) -> tuple[float, bool]:
raw = severity * exposure * human_factor * context
if confidence < 0.3:
return (raw * 0.3, True)
return (raw * confidence, False)
def classify_tier(risk_score: float, is_mandatory: bool) -> ActionTier:
if is_mandatory:
return ActionTier.HARD_STOP
if risk_score >= 80:
return ActionTier.IMMEDIATE
if risk_score >= 40:
return ActionTier.SHIFT_CORRECT
return ActionTier.LOG_ONLY
def top_n_cases(cases: list[Case], n: int = 5) -> list[Case]:
active = [c for c in cases if c.tier != ActionTier.HARD_STOP]
return sorted(active, key=lambda c: c.risk_score, reverse=True)[:n]
def format_case_card(case: Case) -> dict:
return {
"case_id": case.case_id,
"zone": case.zone,
"equipment": case.equipment,
"crew": case.crew,
"risk_level": case.tier.name,
"risk_score": round(case.risk_score, 1),
"root_cause": case.root_cause,
"action": case.recommended_action,
"evidence": case.evidence,
"owner": case.owner,
"deadline_min": case.deadline_minutes,
"escalation": case.escalation_target,
"confidence": round(case.confidence, 2),
"needs_verification": case.needs_verification,
}
VALID_INTENTS = [
"zone {N} methane confirm",
"truck {N} operator check",
"record dust corrective action",
"acknowledge case {ID}",
"escalate case {ID}",
"request backup zone {N}",
"report near miss zone {N}",
"shift handover ready",
]
@dataclass
class VoiceIntent:
intent: str
timestamp: datetime
location: tuple[float, float]
confidence: float
operator_id: Optional[str] = None
def should_send(self) -> bool:
return self.confidence > 0.6
def to_payload(self) -> dict:
return {
"intent": self.intent,
"ts": self.timestamp.isoformat(),
"loc": self.location,
"conf": round(self.confidence, 2),
"op": self.operator_id,
}
@dataclass
class AuditEntry:
case_id: str
seen_by: str
seen_at: datetime
approved_by: Optional[str] = None
approved_at: Optional[datetime] = None
corrective_action: Optional[str] = None
completed_at: Optional[datetime] = None
ai_recommendation: Optional[str] = None
ai_confidence: Optional[float] = None
human_override: bool = False
override_reason: Optional[str] = None
def compute_human_factor(
shift_type: str,
hours_into_shift: float,
consecutive_shifts: int,
last_break_hours_ago: float,
fatigue_events_today: int,
radio_response_delay_sec: float,
) -> float:
"""
Based on NIOSH mining fatigue review:
Night shift, 4+ consecutive = 0.05% BAC equivalent
"""
base = 1.0
if shift_type == "night":
base += 0.3
if hours_into_shift > 8:
base += 0.2
if hours_into_shift > 10:
base += 0.3
if shift_type == "night" and consecutive_shifts >= 4:
base += 0.5
elif shift_type == "day" and consecutive_shifts >= 8:
base += 0.5
if last_break_hours_ago > 4:
base += 0.2
base += fatigue_events_today * 0.15
if radio_response_delay_sec > 5:
base += 0.2
if radio_response_delay_sec > 10:
base += 0.3
return min(base, 3.0)
NO_GO_CONDITIONS = [
"AI-only authority to stop or restart equipment",
"Black-box score without evidence chain",
"Free-form voice conversation as primary UI",
"No fallback when communication is lost",
"Visualization-only design with no workflow integration",
"Replacing mandatory competent/certified person exams",
"Suppressing or delaying mandatory safety controls",
"Sending raw audio to cloud in low-bandwidth environment",
]
SITE_CONFIG = {
"mine_type": "surface",
"commodity": "limestone",
"jurisdiction": "MSHA MNM (30 CFR Part 56)",
"equipment": [
"haul_truck", "loader", "excavator",
"drill_rig", "crusher", "conveyor"
],
"primary_hazards": [
"powered_haulage",
"highwall_collapse",
"silica_dust",
"machinery",
"vehicle_pedestrian",
],
"communication": "surface_wifi_partial",
"shift_pattern": "12h_rotating",
"fatigue_program": "camera_based",
"exam_records": "paper_transitioning_digital",
"silica_compliance_date": "2026-04-08",
}
if __name__ == "__main__":
hf = compute_human_factor(
shift_type="night",
hours_into_shift=10,
consecutive_shifts=4,
last_break_hours_ago=5,
fatigue_events_today=1,
radio_response_delay_sec=7,
)
risk, needs_verify = compute_risk(
severity=4,
exposure=2.0,
human_factor=hf,
context=1.5,
confidence=0.8,
)
case = Case(
case_id="A17",
zone="Dump Point West",
equipment="Truck 12",
crew="Night Crew B",
risk_score=risk,
tier=classify_tier(risk, is_mandatory=False),
root_cause="Overspeed + fatigue flag + low visibility + near-miss history",
recommended_action="Verify operator alertness. Hold truck at staging area.",
evidence=[
"Speed: 38km/h in 25km/h zone",
"Fatigue camera: 2 microsleep events",
"Shift: night, hour 10, 4th consecutive",
"Zone: dump point near-miss 3 days ago",
"Maintenance: brake inspection overdue 2 days",
],
owner="Foreman Rodriguez",
deadline_minutes=2,
escalation_target="Superintendent Williams",
confidence=0.8,
needs_verification=needs_verify,
)
print(f"Case {case.case_id}: {case.zone}")
print(f"Human Factor: {hf:.2f}x")
print(f"Risk Score: {case.risk_score:.1f}")
print(f"Tier: {case.tier.name}")
print(f"Action: {case.recommended_action}")
print(f"Needs Verification: {case.needs_verification}")
print(f"Deadline: {case.deadline_minutes} min")
print(f"\nEvidence:")
for e in case.evidence:
print(f" - {e}")
print(f"\nNo-Go Conditions:")
for ng in NO_GO_CONDITIONS:
print(f" ✗ {ng}")