V.E.L.O.C.I.T.Y.-OS: The Synaptic Canvas GUI & V-NCE GPU (Part 10)

Description and use

Implemented a double‑buffered GUI stack with GPU acceleration for a bare‑metal OS, enabling real‑time visualization of system metrics and JIT execution blocks.

Problem

The bare‑metal kernel lacked a graphical interface, limiting usability and debugging.

Outcome

A fully functional, double‑buffered GUI stack was added to a bare‑metal OS, enabling real‑time visualization of system metrics and JIT execution blocks, with GPU acceleration for embedding calculations.

Workflow

• 1. Mapped UEFI GOP framebuffer and created a backbuffer in heap memory.
• 2. Implemented double‑buffering: draw to backbuffer then copy to screen in one operation.
• 3. Developed three GUIs in no_std Rust, each rendering without floating point libraries.
• 4. Added force‑directed layout for SynapticCanvasGui using cosine similarity of FAT32 file embeddings.
• 5. Implemented Bezier spline rendering for connections and glow effects.
• 6. Scanned PCI space for GPUs, mapped registers into UMA, and built a zero‑copy compute API.
• 7. Integrated GPU command lists (BindPipeline, SetPushConstants, DispatchCompute) with JIT compiler output.
• 8. Tested rendering performance and visual fidelity on bare metal.
• 9. Planned multi‑agent swarm runtime for future scalability.

Evidence

I implemented a double-buffering scheme: drawing elements to a heap-allocated backbuffer (Vec<u32>) and blasting it to screen memory in a single operation to prevent screen flicker.

Source

The compositor computes the pairwise cosine similarity between all files in the FAT32 directory.

Source

The driver scans the PCI space for standard graphics adapters and maps their registers in Unified Memory Architecture (UMA) space.

Source