bitbornMAKE EVERY BIT COUNT

ARCHITECTURE / THE SOURCE BOUNDARY

The instruction
starts as bits.

Executable instructions are authored as literal binary digits. Ordinary host tools package those values, inspect them, and test them in the intended execution environment.

SOURCE → PACKAGING → EXECUTION

Follow what crosses
each boundary.

  1. 01 / SOURCELiteral .bits10111000 00101010 00000000

    Opcodes, operands, addresses and data are chosen directly. Mnemonics in comments explain the bytes.

  2. 02 / HOST TOOLByte packingB8 2A 00

    Python strips comments and whitespace, validates eight-bit tokens, then writes their values unchanged.

  3. 03 / ENVIRONMENTCPU executionBIOS real mode / Linux x86-64

    The environment determines how bytes are decoded and which firmware or syscall services are available.

INSTRUCTIONS AND CONTAINERS

What the host adds.

The canonical 512-byte image

boot/boot.bits contains the entire sector: instruction bytes, message data, explicit padding, and the 55 AA signature. Packing this source reproduces the image without adding bytes.

Read the canonical source →

Gallery packaging

Smaller payloads receive non-executable sector padding and signature data, or ELF headers for Linux. Multi-sector images combine a separately handwritten loader with separately handwritten second-stage instructions.

Host metadata is generated. Target instruction encodings are not generated by an assembler or compiler.

THREE DISTINCT KINDS OF EVIDENCE

A model is one view.

EnvironmentWhat happensWhat it establishes
Browser modelJavaScript represents a supported 16-bit instruction subset and selected BIOS/I/O behavior, with a bounded run.Useful state and encoding feedback for modeled behavior. No native x86 or complete BIOS execution.
QEMU guestEmulated x86 hardware and BIOS execute the guest’s actual bytes. Tests can inspect serial, VGA, and keyboard behavior.Observed behavior in that configured emulator. Hardware and UEFI compatibility need their own evidence.
Linux x86-64A native Linux kernel loads the ELF container and executes the unchanged x86-64 syscall payload.Observed behavior in the supported native environment. These files do not run directly on macOS or ARM Linux.