Idea stage · not yet started
Universal firmware.
A hook at the very first instruction.
AdaBIOS is a universal, cross-hardware-vendor firmware project — forked from
real open firmware (coreboot and/or EDK2/TianoCore), not built from scratch — with an
agent hook placed as early as boot gets.
The lowest layer of a full-stack agent architecture that runs from firmware to the cloud. Named and scoped; no code yet.
power on
│
▼
┌─────────────────────────────┐
│ AdaBIOS agent hook │ ← earliest possible boot-time presence
│ (forked coreboot / EDK2) │
└─────────────────────────────┘
│
▼
kernel — AdaOS agent (syscall/init boundary)
│
▼
OS — Ada Doctor (health/diagnostic agent)
│
▼
cloud — Ada + AdaShield, one AdaDo login
Why fork, not build from scratch
coreboot already has broad real-hardware vendor support; EDK2/TianoCore is the open UEFI reference
implementation most modern boards already trust. Writing a BIOS from zero means re-solving decades
of hardware-initialization edge cases that these projects have already solved in the open. AdaBIOS's
actual job is the agent hook at the boot boundary — not reinventing firmware.
Two teams, every layer
Ada's team and AdaShield's security team each run the entire stack — firmware to cloud — side by side, not one replacing the other.
Ada's team
- BIOS AdaBIOS hook
- Kernel AdaOS agent
- OS Ada Doctor
- Cloud Ada
Security's team
- BIOS hook
- Kernel agent
- OS agent
- Cloud AdaShield
One AdaDo account logs in to the OS, the browser, the app, and every other AdaDo service — the same real identity both cloud teams (Ada and AdaShield) use to link into that OS session. Not a separate login per layer, per app, or per device.
What this is — and isn't, yet
Is:
- A named, scoped project with a real architecture (ADADO-1948)
- The firmware layer of the same stack AdaOS occupies at the kernel — sibling projects, same ambition
Isn't, yet:
- Any code at all
- A decision between coreboot and EDK2/TianoCore (or both, layered)
- A downloadable image, or a subdomain with anything more than this page