FROZEN V11 ARCHIVE — historical DByteOS/native documentation. Read current v12.2.1 release notes.
RELEASE LINE13.2 STABLE13.1 PREDECESSOR13.0 PREVIOUS12.4 NATIVE MIRARCHIVE

HISTORICAL · FROZEN EVIDENCE

Native boundaries and nonclaims

A HARD BOUNDARY IS PART OF THE DESIGN. DO NOT DELETE IT FROM THE MANUAL TO MAKE THE PROJECT LOOK LARGER.

Surface separation§

HOSTED DBYTE
  tree interpreter
  bytecode VM
  CLI / REPL / test / shell
  host runtime available

NATIVE DBYTE
  i686-dbyte-none
  systems checker
  typed native IR
  DByte x86 encoder
  ELF32 objects + DByte linker
  freestanding runtime milestones

DBYTEOS USERLAND
  host-runnable .dby personal environment
  NOT proof of a standalone OS kernel

RUST KERNEL LAB
  separate freestanding research oracle
  NOT linked into the native DByte image
  NOT a hidden runtime service

v11.0 foundation exclusions§

NO hosted top-level execution
NO hosted globals
NO float / bytes / buffer / list / formatted-string native surface
NO modules/imports in v11.0
NO for / division / nested functions
NO filesystem/process/Windows/VM/host callbacks
NO unresolved native calls
NO external assembler/linker/compiler/runtime
NO heap
NO dynamic array
NO 64-bit arithmetic
NO dynamic linking
NO weak symbol
NO runtime module loading
NO scheduler
NO filesystem
NO driver framework
NO self-hosted compiler

v11.2 kernel-core boundary§

CPL0 -> CPL0 ONLY
32-BIT PROTECTED MODE
NO userspace transitions
NO task gates
NO VM86
NO paging recovery
NO scheduler / threads
NO heap / filesystem
NO drivers beyond serial / PIC / PIT
NO ACPI / SMP / networking / audio / GUI
NO textual assembly / NASM / C / Rust runtime shim

v11.3 memory-core boundary§

32-BIT NON-PAE
4 KiB PAGES
IDENTITY MAP FIRST 4 MiB
MONOTONIC FRAME ALLOCATION AT THIS MILESTONE
NO heap / freeing
NO scheduler / threads / filesystem / userspace
NO PAE / 64-bit physical arithmetic
NO Multiboot modules / ACPI / SMP / USB / network / audio / GUI

v11.4 runtime boundary§

ONE BOUNDED KERNEL ALLOCATOR
NO libc
NO compiler allocator
NO scheduler / threads / processes / userspace
NO filesystem / disk / USB / networking / audio / GUI / SMP
NO sparse interior decommit
NO physical memory above existing non-PAE 32-bit contract

v11.5 scheduler boundary§

SINGLE CORE
CPL0 TASKS
ROUND ROBIN
8 DETERMINISTIC SLOTS
NO second register-context ABI
IRQ0 MUTATION IS BOUNDED
IRQ0 ALLOCATES NOTHING
RECLAIM BY IDLE TASK

v11.6 blocking boundary§

task_sleep_ticks interval < half u32 tick space
8 fixed FIFO Event waiter slots
signals are non-sticky
event_signal does not schedule
event_signal does not acknowledge hardware
wait/sleep are task-context operations

v11.7 IRQ I/O boundary§

64-BYTE STATIC KEYBOARD FIFO
8-TASK SEMAPHORE WAITER QUEUE
IRQ1:
  one raw port-60 byte
  no overwrite
  one semaphore post
  one master PIC EOI
  no allocation
  no mapping
  no logging
  no blocking
  no scheduling

v11.8 ATA boundary§

PRIMARY ATA PROOF
LBA28
16-BIT PIO
ONE OUTSTANDING SECTOR REQUEST
512-BYTE ALIGNED BUFFER CONTRACT

NO AHCI
NO DMA
NO LBA48
NO ATAPI
NO request queues
NO partitions
NO caches
NO filesystem

v11.9 DBFS1 boundary§

512-BYTE SECTORS
ROOT-ONLY DIRECTORY MODEL IN FORMAT V1
64 FIXED INODES
64 FIXED ROOT DIRECTORY ENTRIES
8 DIRECT BLOCKS PER FILE
MAX FILE SIZE 4096
ASCII NAMES 1..31 BYTES

NO nested paths IN 11.9 FORMAT API
NO links / permissions / timestamps / sparse files
NO block cache
NO journal
NO crash-recovery claim
NO filesystem work in IRQ context

v11.10 · 11.10.1 boundary§

11.10 extends the filesystem runtime above the DBFS1 disk contract. 11.10.1 expands the native intrinsic/encoder boundary. Neither release, by itself, turns the project into a finished general-purpose operating system.

Documentation law§

DO NOT:
  infer a feature because x86 can do it
  infer a stable ABI from an intrinsic name
  infer a PASS from a release note
  merge DByteOS userland with native kernel state
  merge Rust Kernel Lab evidence into DByte native runtime evidence
  rewrite historical version labels to current release number

DO:
  name the source of each claim
  keep the verifier entrypoint
  keep failure conditions
  keep artifact hashes
  keep nonclaims visible