Files
cubelinux/whitepaper/cubelinux-whitepapers.html
T
luulu cf865390d3 whitepaper: publish post 4 (The Memory Dial - local frontier inference)
- add whitepaper/cubelinux-local-frontier-inference.html: fourth blog post. Examines
  DwarfStar (DS4), which runs a 284B-parameter model on 128GB of consumer memory via
  selective quantization, calibration and SSD expert streaming. Maps what its
  reframing ("RAM stops being a wall and just becomes a dial") genuinely shares with
  the CZYX coordinate substrate - the one-seek record fetch, locality-preserving
  ordering, prefix-scan session replay, explicit edges between spaces - and states
  plainly where the resemblance fails: the compression is quantization, not
  addressing, and the hot path belongs to raw block reads rather than the durable
  store. Also covers the Jetson AGX Thor sm_110 vs supported sm_121 mismatch and
  proposes one bounded experiment (expert placement by co-activation) with a stated
  pass/fail.
- update whitepaper/cubelinux-whitepapers.html: listing now shows four drafts.
2026-09-12 20:37:00 -04:00

156 lines
12 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
<title>CUBELinux — Whitepapers</title>
<meta name="description" content="The CUBELinux whitepapers: a coordinate-addressed OS where the database lives in the kernel.">
<style>
:root{
--gold:#d8af68; --gold-hi:#fff9b1; --cyan:#39d7ff; --bg:#0c0f14;
--panel:#141a22; --panel2:#1b232e; --ink:#e8eaeb; --muted:#8a97a6;
--ok:#5ee0a0; --line:#26303c; --warn:#e8a040;
}
*{box-sizing:border-box}
html,body{margin:0;height:100%}
body{
background:radial-gradient(1200px 600px at 80% -10%, #15212e 0%, var(--bg) 55%);
color:var(--ink); font:15px/1.55 -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif;
-webkit-tap-highlight-color:transparent;
}
.wrap{max-width:780px;margin:0 auto;padding:18px 16px 40px}
header{margin-bottom:18px;border-bottom:1px solid var(--line);padding-bottom:14px}
.logo{width:36px;height:36px;border-radius:10px;background:linear-gradient(135deg,var(--gold),var(--cyan));box-shadow:0 0 20px rgba(57,215,255,.3);flex-shrink:0}
h1{font-size:21px;margin:8px 0 2px;font-weight:700;letter-spacing:.2px}
h1 span{color:var(--cyan)}
.meta{color:var(--muted);font-size:12px;margin-top:4px}
.meta b{color:var(--ink);font-weight:600}
h2{
font-size:14px;margin:22px 0 6px;padding-bottom:4px;border-bottom:1px solid var(--line);
color:var(--gold);letter-spacing:.4px;text-transform:uppercase;font-weight:700;
}
.note{background:var(--panel);border:1px solid var(--line);border-left:3px solid var(--warn);border-radius:8px;padding:8px 12px;margin:10px 0;color:var(--ink)}
.note b{color:var(--warn)}
article{
background:var(--panel);border:1px solid var(--line);border-radius:12px;
padding:14px 16px;margin:10px 0;display:block;
}
article h3{margin:0 0 6px;font-size:15px;color:var(--cyan);font-weight:600}
article .date{color:var(--muted);font-size:11px;letter-spacing:.04em;margin-bottom:6px}
article p{margin:4px 0 8px;color:var(--ink)}
article footer{margin-top:8px;border-top:1px solid var(--line);padding-top:8px;display:flex;justify-content:space-between;align-items:center;gap:12px;flex-wrap:wrap}
article .tags{display:flex;gap:4px;flex-wrap:wrap}
.pill{display:inline-block;background:var(--panel2);border:1px solid var(--line);border-radius:10px;padding:1px 7px;font-size:10.5px;color:var(--muted);letter-spacing:.04em}
.pill.primary{background:rgba(216,175,104,.12);border-color:var(--gold);color:var(--gold)}
.pill.optional{background:var(--panel2);border-color:var(--line);color:var(--muted)}
.pill.explored{background:rgba(57,215,255,.1);border-color:var(--cyan);color:var(--cyan)}
.pill.standard{background:var(--panel2);border-color:var(--line);color:var(--muted)}
.pill.booted{background:rgba(94,224,160,.12);border-color:var(--ok);color:var(--ok)}
a.read{
display:inline-flex;align-items:center;gap:5px;color:var(--gold-hi);text-decoration:none;
font-size:13px;font-weight:600;letter-spacing:.02em;padding:5px 10px;border:1px solid var(--gold);
border-radius:8px;background:rgba(216,175,104,.08);transition:background .15s,border-color .15s;
}
a.read:hover{background:rgba(216,175,104,.16);border-color:var(--gold-hi)}
a.read.optional{color:var(--cyan);border-color:var(--cyan);background:rgba(57,215,255,.08)}
a.read.optional:hover{background:rgba(57,215,255,.14)}
footer{margin-top:32px;padding-top:12px;border-top:1px solid var(--line);color:var(--muted);font-size:12px}
</style>
<!-- Open Graph / Twitter / canonical (site prep) -->
<meta property="og:type" content="website">
<meta property="og:title" content="CUBELinux — Whitepapers">
<meta property="og:description" content="The CUBELinux whitepapers: a coordinate-addressed OS where the database lives in the kernel.">
<meta property="og:url" content="https://cubelinux.com/cubelinux-whitepapers.html">
<meta property="og:image" content="https://cubelinux.com/images/logo-header@2x.png">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="CUBELinux — Whitepapers">
<meta name="twitter:description" content="The CUBELinux whitepapers: a coordinate-addressed OS where the database lives in the kernel.">
<meta name="twitter:image" content="https://cubelinux.com/images/logo-header@2x.png">
<link rel="canonical" href="https://cubelinux.com/cubelinux-whitepapers.html">
</head>
<body>
<div class="wrap">
<header>
<div class="logo"></div>
<h1>CUBELINUX <span>·</span> Whitepapers</h1>
<div class="meta"><b>Four drafts — two posted 2026-08-25, one 2026-09-09, one 2026-09-12.</b> Pick one to read in full — each is a standalone HTML page.</div>
</header>
<div class="note"><b>About these drafts.</b> The whitepaper documents the design, verified on-disk state, and completed kernel build of the CUBELinux coordinate-addressed OS. The addendum is a separate, clearly-labeled <em>preliminary exploration</em> of how state-spanning neural networks might one day layer on top of the CZYX filesystem — nothing in it is built or committed. The ESP32 integration proposal is likewise a <em>preliminary exploration</em> of carrying the coordinate substrate onto microcontrollers, and is likewise not built. The local-inference note is an <em>architectural observation</em> on an external project, DwarfStar, and where the coordinate model may or may not contribute to it.
<div class="note" style="border-left-color:var(--cyan)"><b>CUBELinux Newsletter.</b> Get update summaries as they happen — new builds, verified milestones, and project progress. <br><a class="read" style="display:inline-block;margin-top:8px;color:var(--cyan)" href="/spec.php">Sign up for the newsletter →</a></div>
<h2>The drafts</h2>
<article>
<h3>CUBELinux — A Coordinate-Addressed OS</h3>
<div class="date">Final draft · 2026-08-21 · updated 2026-09-06 with WordFlags + cubetrace + verification pass</div>
<p>The primary whitepaper. Documents the core claim (a position in space resolves to bytes), the coordinate primitive (256-bit space selector + Morton-ordered leaf behind a Curve trait), the storage layer (WAL + delta checkpoint, 250ms/200-op burst cap), the OS entity schema (MEM/SES/PRJ/EDG, with metatags as first-class citizens), the crate structure (7 built / 3 deferred / 1 dropped), and the custom kernel that has been built, installed, and booted. §7 closes with the FUSE proxy reaching M2(a): 2 tests added, 2 bugs fixed, `./check` green.<br/><br/><strong>Updated 2026-09-06</strong> — the tri-channel word&apos;s 12 &quot;wasted&quot; bits were realized as a <strong>16-bit per-word flag field</strong> (<code>cubecoords::WordFlags</code>, header tag 14) with <code>scan_by_word_flag</code>/<code>show-flags</code>; the <strong>cubetrace</strong> layer is now built (execution capture → replay → store as <code>Kind::Layer</code> records → golden-regression → lineage walk, with the Solitaire example); and the whitepaper&apos;s own benchmarks were <strong>re-tested in release</strong> — ~180 tests green, encode costs/box bake-off/session-replay/edge-walk reproduced within ~1&ndash;2%, with one revision: feature-ball recall does <em>not</em> favor Hilbert. See §8&ndash;9.</p>
<footer>
<div class="tags">
<span class="pill primary">primary deliverable</span>
<span class="pill primary">WordFlags 16-bit flag field</span>
<span class="pill primary">cubetrace capture + replay</span>
<span class="pill booted">kernel built + booted</span>
<span class="pill booted">~180 tests green</span>
<span class="pill standard">durable WAL store</span>
<span class="pill standard">FUSE proxy M2(a)</span>
</div>
<a class="read" href="cubelinux-final-whitepaper.html">Read the full whitepaper →</a>
</footer>
</article>
<article>
<h3>State-Spanning Neural Networks for the CZYX Coordinate Filesystem</h3>
<div class="date">Preliminary draft · 2026-08-23 · posted 2026-08-25</div>
<p>An exploratory addendum. Proposes five application domains for state-spanning neural networks (LSTM / SSM / GNN / transformer-with-memory / autoencoder) layered optionally on top of the CZYX filesystem: access-pattern prediction with prefetching, coordinate-conditioned compression, anomaly detection in cube operations, learned indexing for range queries, and adaptive caching with neural policies. Each domain gets a model sketch, integration point, and challenge assessment. Central thesis: CZYX's Morton-encoded locality makes neural approaches viable as optional optimizations, not as replacements for the deterministic storage core.</p>
<footer>
<div class="tags">
<span class="pill optional">optional advisory layer</span>
<span class="pill explored">architectural exploration</span>
<span class="pill standard">not implemented</span>
<span class="pill original">original work</span>
</div>
<a class="read optional" href="cubelinux-neural-networks-addendum.html">Read the addendum →</a>
</footer>
</article>
<article>
<h3>CUBE Integration into ESP32 Modules</h3>
<div class="date">Preliminary draft · 2026-09-09</div>
<p>A proposal for carrying the coordinate substrate onto ESP32-class microcontrollers. Describes the device as a first-class coordinate space — its own 256-bit <code>SpaceId</code>, with configuration, telemetry, and health held at coordinates and its relationships held as first-class association edges. Presents two deployment tracks: the device as a CUBE <em>client</em> speaking a coordinate protocol to a host daemon over MQTT/TCP, and the device as a standalone CUBE <em>node</em> with a non-volatile store and its own listener. Draws the precise portability boundary — <code>cube-core</code> and <code>cube-store-raw</code> are <code>no_std</code> and cross to the device, while the durable store, daemon, and FUSE view do not — and closes on the graph-and-Portal model for a device fleet plus the agent monitoring layer, in which recall and topology are the same graph walk. Central thesis: CUBE does not merely store bytes on a device faster; it makes monitoring, memory, and control one traversable, capability-gated coordinate graph.</p>
<footer>
<div class="tags">
<span class="pill optional">architectural proposal</span>
<span class="pill explored">edge / embedded</span>
<span class="pill standard">not implemented</span>
<span class="pill original">original work</span>
</div>
<a class="read optional" href="cubelinux-esp32-integration.html">Read the proposal →</a>
</footer>
</article>
<article>
<h3>The Memory Dial: Local Frontier Inference and the Coordinate Substrate</h3>
<div class="date">Preliminary draft · 2026-09-12</div>
<p>An architectural observation on DwarfStar (DS4), which runs a 284-billion-parameter model on 128&nbsp;GB of consumer memory by quantizing only the routed experts, protecting the load-bearing weights, and streaming experts from SSD through a power-law cache. Examines what its reframing — <em>RAM stops being a wall and just becomes a dial</em> — genuinely shares with the CZYX coordinate substrate: the one-seek record fetch, the locality-preserving ordering, prefix-scan session replay, and explicit edges between spaces. States plainly where the resemblance fails (the compression is quantization, not addressing; the hot path belongs to raw block reads, not the durable store), examines why the Jetson AGX Thor is <code>sm_110</code> against the supported <code>sm_121</code>, and proposes one bounded experiment — placing experts by co-activation so the hot set becomes a contiguous span — with a stated pass/fail.</p>
<footer>
<div class="tags">
<span class="pill optional">architectural note</span>
<span class="pill explored">external project review</span>
<span class="pill standard">not implemented</span>
<span class="pill original">original work</span>
</div>
<a class="read optional" href="cubelinux-local-frontier-inference.html">Read the note →</a>
</footer>
</article>
<footer>
<p>CUBELinux — Whitepapers · Posted 2026-08-25 · updated 2026-09-12 · <a href="/" style="color:var(--cyan)">Back to CUBELinux.com</a></p>
</footer>
</div>
</body>
</html>