DEV Community: Yuji Marutani

When AI Makes Decisions Feel Obvious

Yuji Marutani — Sat, 03 Jan 2026 09:26:11 +0000

Generative AI is often framed as a productivity tool.
It suggests code, summarizes documents, recommends next actions.
In most systems, it doesn’t decide — it assists.

And yet, many users report the same experience:

“I technically chose, but it didn’t feel like a decision.”

This article is about why that feeling matters — and what it means for how we design AI systems.

AI Rarely Decides for You — It Redesigns the Decision
Most AI systems today operate through recommendations:

ranked lists

suggested defaults

optimized outputs

“best” answers

None of these force action.
But they do something subtler: they shape what feels reasonable.

When a system presents an option as:

comprehensive

optimized

neutral

disagreeing with it starts to feel irrational, even irresponsible.
The user still chooses — but the space of judgment has already been compressed.

From External Rules to Internal Alignment
Traditional hierarchy worked through explicit authority:

rules

approvals

commands

These were visible, and therefore contestable.

Modern systems increasingly work through standards instead:

efficiency

best practice

optimization

benchmarks

Generative AI accelerates this shift.
Instead of telling users what to do, it shows them what “makes sense.”
Over time, those standards are internalized.
Compliance feels like good judgment.

This is what I call internalized hierarchy:
power embedded not in commands, but in the reasoning process itself.

Why “Human-in-the-loop” Often Fails
Many AI systems address responsibility by keeping a human “in the loop.”
A human approves the output. A checkbox is checked.

But approval is not judgment.

If the system:

resolves uncertainty in advance

hides trade-offs

presents one option as clearly superior

then the human role becomes ceremonial.

Judgment requires:

incomplete information

visible trade-offs

the possibility of being wrong

When those conditions are optimized away, judgment disappears — even if a human is still present.

Designing Systems That Still Require Judgment
If we want AI systems that preserve human agency, this cannot be solved with ethics statements alone.
It is a design problem.

Here are three practical design principles:

Preserve Friction

Not every decision should feel smooth.
Moments of hesitation are not bugs — they are signals that judgment is happening.

Expose Trade-offs

Avoid single “best” outputs when real alternatives exist.
Show why one option excels and where it fails.

Keep Decisions Incomplete

Systems should support interpretation, not closure.
A decision that feels finished before a human engages with it is already delegated.

The Question That Matters
The real question is not:
“Should we use AI?”

But:
Does this system invite human judgment — or quietly render it redundant by design?

Generative AI will continue to improve.
The risk is not that it becomes too powerful,
but that it becomes so reasonable we stop noticing when judgment is no longer required.

Further Reading
This post is based on my recent paper:
Reclaiming Judgment in the Age of Generative AI: Design, Internalized Hierarchy, and Individual Agency

DOI: 10.5281/zenodo.18136101

I welcome feedback, critique, and collaboration — especially from those designing systems where human judgment still needs to remain meaningful.

Human-Side Hallucination Bias: Why Developers Mislabel AI Deviations (and How It Hurts Our Systems)

Yuji Marutani — Mon, 29 Dec 2025 09:43:33 +0000

Hallucination has become one of the most overused words in AI development.
But here’s the uncomfortable truth:

Developers hallucinate too — not in outputs, but in judgment.

We often label an AI response as a hallucination not because the model is wrong, but because our own cognitive frame is too narrow to interpret what it’s doing.

This article introduces a concept I call human-side hallucination bias — a multilayered pattern that affects how developers evaluate AI behavior.
Understanding this bias is essential if we want to build better models, better evaluation pipelines, and better products.

The Real Problem: We Treat “Expected Output” as “Correct Output”

Most hallucination reports I see in dev teams fall into one of these categories:

• “It said something I didn’t know.”
• “It gave an answer outside the mainstream.”
• “It challenged the expert’s view.”
• “It reframed the problem in a way I didn’t expect.”

None of these are hallucinations.
They’re deviations from human expectation, not deviations from truth.

And when we conflate the two, we end up building brittle systems.

The Five Layers of Human-Side Hallucination Bias

Layer 1 — Personal Knowledge Fragility

When the model outputs something unfamiliar, the instinctive reaction is:

“That can’t be right.”

But often the model is surfacing:

• edge cases
• alternative interpretations
• lesser-known facts

This layer affects debugging and prompt evaluation more than we admit.

Layer 2 — Consensus Overfitting

Teams often treat consensus as ground truth.
But consensus is:

• culturally dependent
• historically contingent
• sometimes just outdated

AI trained on diverse corpora may surface valid but non-consensus perspectives.
Calling these hallucinations suppresses innovation.

Layer 3 — Authority Preservation

Experts react strongly when AI challenges established knowledge hierarchies.

This leads to:

• overcorrection
• unnecessary guardrails
• “safe but dumb” alignment

In enterprise settings、this layer shapes risk policies more than technical reality.

Layer 4 — Centralized Epistemic Governance

Modern institutions rely on centralized control of “truth.”
Generative AI introduces distributed knowledge production.

For developers, this shows up as:

• discomfort with unpredictable outputs
• pressure to enforce deterministic behavior
• fear of losing control over epistemic boundaries

This layer influences alignment strategies and product decisions.

Layer 5 — Anthropocentric Anxiety

At the deepest level, AI deviations challenge the assumption that:

• humans are the primary interpreters
• human reasoning is the reference frame

This creates subtle resistance to AI-generated novelty.

In product teams、this becomes:

• “Make it more human-like.”
• “Avoid outputs users can’t immediately understand.”

Even when those constraints reduce capability.

Why This Matters for Developers

Mislabeling deviations → bad engineering

If every unexpected output is labeled a hallucination, teams will:

• overfit alignment
• suppress creative reasoning
• mis-tune reward models
• reduce model diversity
• kill emergent capabilities

This leads to safer but weaker systems.

Human bias becomes training data

When developers annotate outputs, their biases become:

• reward gradients
• evaluation benchmarks
• safety constraints

Human-side hallucination bias literally becomes part of the model.

Innovation dies when deviation is punished

Some of the most valuable AI behaviors come from:

• reframing problems
• generating alternative structures
• proposing unconventional hypotheses

These are the same behaviors humans often misclassify as hallucinations.

How to Build Better Evaluation Pipelines

Here are practical steps teams can take:

• Separate factual errors from conceptual deviations
• Use multi-perspective evaluation (not single-expert judgment)
• Allow “creative deviation zones” in prompts
• Avoid over-aligning to narrow human expectations
• Treat consensus as a reference, not a truth oracle
• Encourage structured reasoning instead of conformity

The goal is not to eliminate deviation —
but to distinguish harmful error from productive novelty.

Final Thoughts

AI hallucination is not just a model problem.
It’s a human cognition problem.

Developers, reviewers, and institutions bring their own hallucinations —
their assumptions, biases, and epistemic constraints —
into the evaluation process.

If we want better AI, we need to debug ourselves too.

“Harvest Now, Decrypt Later” Is Already in Production

Yuji Marutani — Mon, 29 Dec 2025 07:07:11 +0000

This is not a futurist piece.

This is about why quantum risk has already become an operational, legal, and governance problem for developers, security teams, and engineering leadership—and why waiting for “real quantum computers” is already a failure mode.

The shift we are living through is subtle but decisive:

from future speculation to active liability.

By late 2025 / early 2026, that shift is no longer theoretical.

1. The HNDL Reality Check: Why Time Is Already Against You

The “Harvest Now, Decrypt Later” (HNDL) strategy has moved from theory to documented intelligence practice.

If the shelf-life of your data (X), plus your migration time (Y), exceeds the time until a Cryptographically Relevant Quantum Computer exists (Z), your data is already compromised—just not yet decrypted.

X (Data shelf-life): 10–30 years (PII, genomic data, trade secrets)
Y (Migration time): 5–10 years for large organizations
Z (Threat horizon): Estimated 2030–2035

For many organizations today, X + Y > Z.

That means the breach already happened.

The only thing missing is compute.

2. Standards Removed the Last Excuse

In August 2024, NIST finalized FIPS 203, 204, and 205.

In March 2025, HQC (Hamming Quasi-Cyclic) was selected as a backup algorithm to ensure cryptographic diversity.

From that point forward, “there are no standards yet” stopped being a defensible position.

By 2026, insurers, regulators, and courts increasingly treat the absence of a PQC migration plan the same way they treat unpatched known vulnerabilities:

a failure to meet the standard of care.

3. Hardware Reality: The Shift to Logical Qubits

The conversation has moved beyond raw qubit counts.

The real metric now is logical qubits—error-corrected, stable computation.

Platform	Status (2026)	Key Breakthrough
IBM	120+ qubits, 300mm fab scaling	10× faster qLDPC decoding
Google	105-qubit chip	Exponential error suppression
Microsoft	28 logical qubits	Topological hardware protection
QuEra	Targeting 100 logical qubits	Reconfigurable neutral atoms

This is no longer science fiction.

It is roadmap execution.

4. What This Means for Engineering Teams (Not Just Boards)

This is not a “wait-and-see” problem.

It is an operations and governance problem.

Three actions matter now:

Inventory your crypto like you inventory dependencies

Establish a Cryptographic Bill of Materials (CBOM).

You cannot migrate—or defend—what you cannot see.

Wrap before you replace

Pilot hybrid key exchange (e.g., ML-KEM alongside classical TLS).

This immediately mitigates HNDL risk without ripping out proven systems.

Quantum risk is a supply-chain problem

Audit third-party dependencies and vendors.

If your vendors cannot articulate a PQC roadmap, they are already a liability.

5. This Is Not a Migration Project

Quantum security is not a one-time upgrade.

It is an operational discipline.

The real failure mode will not be “broken crypto.”

It will be the inability to prove—technically and legally—that you acted responsibly after the risk was already known.

That is the line history keeps drawing.

And by 2026, that line is no longer theoretical.

DevRealityOps Manifesto

Yuji Marutani — Sun, 28 Dec 2025 22:08:48 +0000

Reality Is Already in Production

We are no longer debating hypothetical risks.

Deepfakes, voice cloning, and large-scale misuse of AI systems are not future threats.
They are already live in production.

This manifesto is not a moral argument.
It is not a policy proposal.
It is a position statement for those who choose to operate inside reality rather than deny it.

1. Reality doesn’t wait for permission

Reality does not pause for ethics committees, legislation, or design reviews.
History shows the same pattern repeatedly:
things break first, explanations come later.

If your system requires “time to prepare,” it is already failing.

2. If it can be abused, it will be

Every capability that can be exploited eventually will be.
This is not pessimism — it is operational experience.

“Unforeseen misuse” is not an excuse.
It is a failure to acknowledge reality.

3. Prohibition scales poorly. Operations scale

Bans, prohibitions, and blanket restrictions do not scale.
Detection, response, and continuous operation do.

What scales is not control —

what scales is adaptation.

4. Perfect safety is a fantasy. Resilience is not

There is no such thing as a perfectly safe system.
There are only systems that fail silently and systems that recover loudly.

Resilience is achievable.
Denial is not a strategy.

5. Detection is not optional — it is infrastructure

Detection is not a “nice to have.”
It is not a premium feature.

It is infrastructure —

as fundamental as networking, logging, or observability.

If you cannot detect abuse, you are not running a system.
You are running a liability.

6. Victims who refuse to adapt will be victims again

Being exploited is not a moral failure.
Refusing to change after exploitation is an operational one.

Reality does not reward innocence.
It rewards adaptation.

7. Arms races are inevitable. Fragility is a choice

Technological arms races do not end.
They are a permanent condition.

You cannot opt out of the race —

but you can opt out of fragility.

8. Reality broke the system. Fix it while running

The system is already broken.
Stopping everything to redesign it is not an option.

Fix it while it is running — or be replaced by something that does.

What DevRealityOps Rejects

The belief that prohibition alone prevents misuse
The assumption that ethics can outpace reality
The myth that abuse is an edge case

What DevRealityOps Demands

Facing reality as it is, not as we wish it were
Shipping imperfect defenses into production
Turning victims into operators

Closing Statement

DevRealityOps is not optimism.
It is not cynicism.

It is the discipline of surviving reality without denial.

Reality is already in production.

DevRealityOps is how we stay alive inside it.

When Illegality Accelerates Democratization

Yuji Marutani — Sun, 28 Dec 2025 20:18:33 +0000

Deepfakes, Voice Cloning, and the Rise of DevRealityOps

As of late 2025, deepfake and voice-cloning technologies have crossed a decisive threshold.
High-quality synthetic audio and video are no longer confined to experts or well-funded organizations. With only a few seconds of audio, anyone can now generate convincing voice replicas using freely available, open-source tools.

This rapid democratization is not an anomaly.
It follows a recurring historical pattern:

Illicit or gray-zone misuse often acts as the ignition point for large-scale technological adoption.

This is not an endorsement of illegal behavior.
It is a description of a repeatedly observed mechanism by which technology collides with reality.

Today, deepfakes represent a textbook case of what can be described as a DevRealityOps moment.

⸻

What Is DevRealityOps?

DevRealityOps is a pragmatic operating philosophy:

Start from what is actually happening in reality—not from idealized designs, ethics frameworks, or regulatory assumptions—and continuously adapt development, deployment, and governance around it.

In practice:
• Reality moves first
• Damage, misuse, and distortions surface
• Systems are then redesigned to survive real conditions

This mirrors the original DevOps insight:

“Don’t wait for perfect architecture. Improve the system that is already running.”

Deepfakes represent a case where Reality has already reached production, whether we approve or not.

⸻

History Repeats: Reality Always Breaks the First Design

We have seen this pattern before.
• Napster (1999–2001)
Illegal file sharing exposed a reality: digital music was infinitely copyable.
The result was not the end of music, but iTunes, Spotify, and an entirely new industry structure.
• Silk Road (2011–2013)
Dark-web marketplaces demonstrated that value transfer without state intermediaries was technically viable.
Bitcoin moved from theory to practice almost overnight.
• Sci-Hub
Copyright infringement forced a global reckoning with access to knowledge, accelerating the Open Access movement.

In each case:
1. Institutions attempted control
2. Reality bypassed them
3. Society was forced to redesign the system

Deepfakes and voice cloning are following the same trajectory.

⸻

The 2025 Reality: Voices Are No Longer Trust Anchors

The current reality is unambiguous:
• Human voices can be replicated from seconds of audio
• Real-time calls can be convincingly forged
• Human auditory intuition has been technically defeated

This is not primarily an ethical failure.
It is a systems failure.

From a DevRealityOps perspective:

Any system that still treats “voice = identity” is already broken in production.

⸻

Regulation Is a Design Review — Not an Incident Response

Regulation matters.
But in DevRealityOps terms, regulation is closer to design review than to runtime defense.

Real attacks are:
• Cross-border
• Real-time
• Adaptively malicious

The history of cryptocurrency shows this clearly:
• Excessive restriction pushes activity underground
• Thoughtful institutionalization increases visibility and safety

Deepfakes will follow the same logic.

Regulation alone cannot stop reality once it is live.

⸻

The DevRealityOps Answer: Deploy Counter-Technology

The real inflection point is not stricter prohibition, but the democratization of counter-technology.

Detection, authentication, and verification tools are not ideal solutions:
• They are imperfect
• They will be bypassed
• They generate false positives

But DevRealityOps is not about perfection.

An imperfect defense in production is always superior to a perfect defense that doesn’t exist.

In this sense:
• Deepfake detectors are the WAFs and EDRs of the synthetic media era
• Tools like Reality Defender, Pindrop, and open scanners represent operational responses, not moral statements

They acknowledge reality and adapt to it.

⸻

When Victims Become Operators

A key DevRealityOps shift is moving affected parties from passive victims to active operators.

Plausible near-term scenarios include:
• Voice actors distributing detection models for their own voices
• Enterprises maintaining executive voice authentication profiles
• Families using multi-channel verification instead of voice trust

This is decentralized, operational defense — not centralized prohibition.

It scales because it accepts reality.

⸻

Objection: “Isn’t This Just an Endless Arms Race?”

Yes.
And DevRealityOps does not deny that.

DevRealityOps assumes:

Arms races cannot be stopped — only managed.

The goal is not to “win” permanently, but to:
• Reduce blast radius
• Increase detection cost
• Continuously adapt

This is how cybersecurity already works.
Synthetic media is simply joining that domain.

⸻

Conclusion: Deepfakes Are a Live Fire Test for DevRealityOps

Deepfakes and voice cloning entered society in the worst possible way:
through fraud, deception, and abuse.

But they also shattered comforting illusions:
• Voices are not proof
• Regulation lags reality
• Technology must be met with technology

DevRealityOps is the mindset that accepts this without panic or denial.

Reality broke the system.
Now the system must be rebuilt while running.

2026 will not be the year deepfakes disappear.
It will be the year DevRealityOps stops being a theory —
and becomes operational infrastructure.

mRNA and saRNA Vaccine Persistence: A Hidden Dialogue with Estrogen Signaling?

Yuji Marutani — Sun, 20 Apr 2025 22:41:20 +0000

Introduction

Synthetic RNA technologies, such as mRNA and self-amplifying RNA (saRNA), have rapidly gained attention as key platforms for vaccine development. While these technologies have proven effective in infectious disease control, questions are emerging about the long-term biological presence of these RNAs and their potential interactions with host cellular pathways. This post explores the possibility of crosstalk between RNA vaccine persistence and estrogen signaling—an area still
underexplored but potentially significant for sex-specific responses and endocrine-sensitive populations.

Background: What Do We Know About RNA Vaccine Persistence?

Initial clinical assumptions surrounding mRNA and saRNA vaccines emphasized their transient nature—designed to degrade rapidly after eliciting an immune response. However, recent studies have challenged this view. Evidence from biodistribution studies shows that synthetic RNAs, encapsulated in lipid nanoparticles, can persist in lymph nodes, liver, and muscle tissues for weeks, and in some cases, months.

Additionally, research such as the 2022 Aldén et al. study has raised the possibility of reverse transcription of vaccine mRNA into host DNA, at least in hepatic cell lines. While the clinical significance remains debated, these findings suggest that synthetic RNA may have more complex biological interactions than originally anticipated.

This persistence and potential integration raise new questions, particularly when considering RNA stability in hormonally active tissues.

Estrogen Signaling and the Unexpected Crosstalk

Emerging studies suggest that estrogen receptors—particularly ERα—may play a role in modulating immune responses to synthetic RNA. These receptors are expressed in various cell types, including immune cells and hepatocytes, which are also implicated in RNA vaccine biodistribution and reverse transcription events.

Notably, estrogen is known to influence the expression of endogenous retroelements and the regulation of APOBEC enzymes, both of which intersect with RNA editing and potential integration pathways. This opens the door to hypotheses where estrogen signaling could amplify or mitigate the biological activity of synthetic RNA within specific tissue environments.

This crosstalk is particularly relevant in populations with fluctuating hormone levels, such as women of reproductive age, postmenopausal individuals, and those undergoing hormone therapy. Sex-specific responses to RNA-based therapeutics may not be solely immunological but also endocrinological in nature.

Implications for Endocrine Function and Personalized Medicine

The potential interaction between mRNA and saRNA vaccines and estrogen signaling has far-reaching implications for endocrine function. If these vaccines indeed persist in hormonally active tissues and interact with estrogen receptors, this could influence a wide array of physiological processes, including metabolic regulation, immune responses, and tissue repair.

For personalized medicine, this discovery opens the door to more tailored vaccination strategies. By considering an individual's hormonal profile—whether related to sex, age, or hormone therapies—clinicians might be able to better predict responses to RNA-based vaccines. This is particularly important in populations such as postmenopausal women, those undergoing hormone replacement therapy (HRT), or individuals with hormone-sensitive conditions.

Understanding how estrogen and RNA vaccines interact could also help in designing vaccines that are more effective for certain subgroups or even in adjusting vaccine formulations to reduce adverse effects in hormonally sensitive populations. Ultimately, this approach could lead to more precise and individualized vaccine protocols, improving both the safety and efficacy of these therapies.

Conclusion: What Questions Should We Be Asking?

As we explore the intersection of synthetic RNA vaccines and estrogen signaling, several important questions remain unanswered. First and foremost, how significant is the persistence of RNA in hormonally active tissues over the long term, and what are the physiological implications of this persistence? While we have seen evidence suggesting RNA’s ability to linger in the body, especially in tissues like the liver and lymph nodes, we still lack comprehensive studies on its long-term effects on hormone-sensitive tissues.

Another critical question is whether estrogen’s modulation of RNA vaccine responses could be leveraged to improve vaccine efficacy or safety in different populations. Given the known influence of estrogen on immune function, understanding its role could be key to optimizing vaccine strategies for both women and men, particularly those with hormone-related conditions.

Moreover, the potential for personalized RNA vaccine therapies based on hormonal profiles presents a new frontier in precision medicine. How can clinicians best integrate hormonal considerations into vaccine development, and what biomarkers would be most useful for predicting individual responses? These questions underscore the need for more research to fully understand the dynamic interactions between RNA vaccines and endocrine pathways.

Ultimately, the emerging science surrounding RNA vaccines and their hormonal interactions highlights the complexity of human biology and the importance of considering sex and hormonal factors in the development of future therapeutics.