03 / BUILD / TARGETS
From a source contract
to a measured machine.
Each target earns its own evidence. A host test and a hardware boot are different milestones.
The target matrix
| TARGET | OBSERVED SCOPE | STATUS |
|---|---|---|
| Python Functional DNA 2.0.0 | Three-fixture / five-stage self-test and SEND BOOK | HOST EXECUTED |
| C++ recovery / FAT-MIPS | g++ C++17 host build; 8,192-byte recovery fixture | HOST EXECUTED |
| Temporal task machine | 15 of 15 synthetic scheduler checks | HOST EXECUTED |
| Julia reviewed revisions | Native Julia 1.13.2 regression and CLI self-tests | NATIVE HOST EXECUTED |
| PS2 homebrew | Source sketches and host-related recovery work | TARGET RUN NOT VERIFIED |
| FPGA glyph lookup | 256 x 32 = 8,192 bits of table capacity | RTL / SYNTHESIS / BOARD UNVERIFIED |
| Kernel / native boot | Width relations and bootstrap architecture | BOOT NOT VERIFIED |
The first FPGA component
256 entries x 32 bits
= 8,192 bits.
That is the capacity arithmetic for one chosen lookup layout. A real component still needs a scalar encoding, interface, reset contract, testbench, named FPGA part, clock constraint and post-route report.
The inverse decoder may have a different resource cost. Julia Char storage is not automatically a synthesizable Unicode-scalar memory layout. The whole program does not become a BRAM because it contains a lookup table.
Five separate meanings of start
- ProtoScroll bootstraps internal language rules.
- A capsule hydrates an application workspace.
- A host operating system starts a process.
- A kernel boots on a named machine.
- An FPGA loads a verified programmable-logic image.
Each deserves its own certificate: source, toolchain, target, input fixture and observed output.
Native protocols remain a research track
The recovered proposal includes ProtocolCore, PseudoBuf, PseudoHTTP, PseudoSMTP, PseudoIMAP, PseudoDNS, PseudoTLS and PseudoJIT. A shared architecture can guide implementation; each protocol still needs its own compatibility and security tests.
The public showcase uses the existing Netlify delivery stack while this work develops.
FOLLOW THE HARDWARE AND PROTOCOL PULSES →