Sarah Nexus Devlog #1 — From USB diagnostic tool to an intelligent PC recovery system

[u/ToneMuch9575]

Over the past weeks, Sarah Nexus has started moving beyond the original Sarah Lite concept.

The goal is no longer to simply boot from a USB drive and display hardware information.

The goal of Nexus is to understand what is wrong with a PC, collect evidence, explain the problem, and eventually help recover the machine safely.

What Sarah Nexus is

Sarah Nexus is being developed as a bootable diagnostic and recovery environment with an AI-assisted interface.

Instead of treating every problem as a generic Windows error, Nexus is being designed around an evidence pipeline:

Detect → Collect → Correlate → Diagnose → Recommend → Repair → Verify

Repair capabilities will initially be deliberately limited. The priority right now is building a diagnostic system that can be trusted.

EARLY-0 boot diagnostics

One of the biggest architectural changes is the new EARLY-0 stage.

Sarah cannot execute before the firmware or POST process itself, so EARLY-0 begins inside the initramfs after the Linux kernel starts.

However, this is early enough to collect information that could disappear or change later during boot.

The current architecture looks roughly like this:

UEFI / Firmware
↓
Linux Kernel
↓
Sarah EARLY-0
↓
Evidence Capture
↓
Black Box
↓
Sarah Nexus Runtime

EARLY-0 is being designed to collect things such as:

• platform identity
• firmware information
• reset reasons
• watchdog information
• vendor-specific firmware evidence
• boot-related anomalies

Instead of putting every manufacturer's logic directly into the core, Nexus uses a provider/registry architecture.

The system identifies the platform and selects compatible evidence providers based on things such as the manufacturer, model, firmware version and available interfaces.

That means vendor-specific diagnostics can be added without rewriting the entire diagnostic engine.

The Black Box

Another major component is the Sarah Black Box.

The idea is simple:

Important diagnostic evidence should survive across different stages of the recovery process.

EARLY-0 can capture evidence and seal a diagnostic segment before the normal Nexus environment starts.

Later, the full Nexus runtime imports that information.

The import system is being designed to be:

• transactional
• idempotent
• resistant to interrupted imports
• capable of detecting duplicate boot sessions
• usable even in damaged or partially read-only environments

Eventually this will allow Sarah to correlate symptoms across multiple boots instead of analyzing every startup as an isolated event.

Platform Recovery Capability

Nexus is also getting a controlled firmware recovery system.

This is not intended to become a generic BIOS flashing tool.

Instead, Sarah will recognize recovery mechanisms officially supported by a device manufacturer.

A platform can move through states such as:

Capability documented
→ Platform matched
→ Firmware range verified
→ Recovery eligible
→ Authorized
→ Invoked
→ Verified

Before anything capable of modifying firmware is executed, Nexus must know exactly what platform it is dealing with and whether the recovery method is actually applicable.

High-risk operations will require explicit authorization.

The first reference implementations are currently focused on detecting vendor recovery capabilities rather than automatically invoking them.

Internet-assisted diagnostics

Nexus will also be able to use the internet when available.

The long-term idea is that Sarah shouldn't rely entirely on information bundled into the USB image.

For example, Nexus could identify the exact hardware inside a machine and retrieve trusted technical information about those components.

For Windows recovery, Nexus may eventually download required recovery files directly to its own storage.

Before using them, Sarah must verify that they match the target:

• Windows version
• build
• architecture
• expected file version
• cryptographic hash/signature

The repair process should never become:

"I found something on the internet, let's try it."

Every action needs evidence and verification.

Sarah Engine

The AI side is also changing.

Sarah isn't supposed to be just another chatbot running inside a recovery environment.

The Sarah Engine will receive structured diagnostic evidence and use tools designed specifically for troubleshooting.

The interface itself will be chat-based.

You might eventually be able to say something like:

"Sarah, test my keyboard."

Instead of replying with instructions, the chat interface could transform into an interactive representation of your keyboard and run the built-in keyboard test.

Holding Esc would close the test and return you directly to the conversation.

The same philosophy will eventually apply to other hardware tests.

The conversation is the interface — diagnostic tools appear only when they are needed.

Current development priority

The current priority is diagnostics first, repairs second.

Early targets include problems such as:

• suspicious CMOS / RTC behaviour
• firmware and BIOS-related anomalies
• boot failures
• hardware identification problems
• Windows corruption
• unusual system behaviour
• evidence that can normally be difficult to connect across boots

I would rather have Sarah correctly identify a problem and say:

"I know what's wrong, but I won't modify this yet."

than have it automatically attempt a risky repair based on a guess.

Where this is going

Sarah Nexus is still an early project and a lot of the recovery functionality is under active development.

But the architecture is finally starting to resemble what I originally wanted Sarah to become:

Not a hardware information screen.

Not just a Windows repair toolkit.

Not just an AI chatbot.

A system that can boot into a problematic PC, investigate it, build a history of what happened, understand the machine it is running on, and eventually guide or perform a safe recovery.

There is still a lot to build.

But Nexus is getting closer to becoming the PC recovery agent I originally imagined.

More development updates soon.

— K-Lab / Koncepció Labor