npm - space-data-module-sdk - Versions diffs - 0.8.15 → 0.8.16 - Mend

space-data-module-sdk 0.8.15 → 0.8.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (116) hide show

package/docs/_shell/consumer-assets.html +5 -0
package/docs/browser-wasmedge-isomorphic.html +261 -0
package/docs/byo-wasm-quickstart.html +226 -0
package/docs/byo-wasm-quickstart.md +204 -0
package/docs/conformance.html +156 -0
package/docs/emception-shared-memory-verdict.md +209 -0
package/docs/events-abi.html +313 -0
package/docs/events-abi.md +530 -0
package/docs/families/analytics.html +178 -0
package/docs/families/analytics.md +104 -0
package/docs/families/attitude.html +157 -0
package/docs/families/attitude.md +36 -0
package/docs/families/behavior.html +157 -0
package/docs/families/behavior.md +36 -0
package/docs/families/breakup.html +157 -0
package/docs/families/breakup.md +36 -0
package/docs/families/conjunction.html +186 -0
package/docs/families/conjunction.md +121 -0
package/docs/families/data-source.html +318 -0
package/docs/families/effects.html +157 -0
package/docs/families/effects.md +36 -0
package/docs/families/environment.html +170 -0
package/docs/families/environment.md +73 -0
package/docs/families/estimation.html +190 -0
package/docs/families/estimation.md +128 -0
package/docs/families/gnc.html +157 -0
package/docs/families/gnc.md +36 -0
package/docs/families/maneuver.html +209 -0
package/docs/families/maneuver.md +206 -0
package/docs/families/obstruction.html +191 -0
package/docs/families/obstruction.md +96 -0
package/docs/families/propagator.html +333 -0
package/docs/families/propulsion.html +157 -0
package/docs/families/propulsion.md +36 -0
package/docs/families/reentry.html +157 -0
package/docs/families/reentry.md +36 -0
package/docs/families/rf.html +193 -0
package/docs/families/rf.md +136 -0
package/docs/families/scheduler.html +157 -0
package/docs/families/scheduler.md +36 -0
package/docs/families/sensor.html +157 -0
package/docs/families/sensor.md +36 -0
package/docs/families/signature.html +157 -0
package/docs/families/signature.md +36 -0
package/docs/flatsql-host-contract.html +176 -0
package/docs/flatsql-streaming-standard.html +375 -0
package/docs/gpu-module-abi.html +233 -0
package/docs/harness-family-matrix.md +135 -0
package/docs/index.html +216 -85
package/docs/isomorphic-pthreads.html +228 -0
package/docs/isomorphic-pthreads.md +84 -0
package/docs/isomorphic-sdn-runtime-plan.html +274 -0
package/docs/language-runtime-matrix.html +182 -0
package/docs/llms.txt +86 -0
package/docs/module-bundle-runtime-plan.html +146 -0
package/docs/module-publication-standard.html +503 -0
package/docs/node-red-default-node-parity.html +201 -0
package/docs/propagator-abi.md +45 -12
package/docs/protect-and-sign.html +181 -0
package/docs/protect-and-sign.md +120 -0
package/docs/protocol-installation.html +296 -0
package/docs/publication-submission.html +158 -0
package/docs/publication-submission.md +78 -0
package/docs/secrets-capability.html +206 -0
package/docs/styles.css +860 -167
package/docs/testing-harness.html +408 -0
package/docs/tri-runtime-parity-gate.html +182 -0
package/docs/tri-runtime-parity.html +203 -0
package/include/orbpro/orbpro_event_runner.h +951 -0
package/include/orbpro/orbpro_events_abi.h +565 -0
package/include/orbpro/orbpro_propagator_abi.h +17 -0
package/package.json +11 -4
package/schemas/orbpro/Events.fbs +501 -0
package/schemas/orbpro/Propagator.fbs +72 -9
package/schemas/orbpro/reference-frame-crosswalk.json +108 -0
package/schemas/orbpro/reference-frame.lock.json +98 -0
package/src/browser.js +13 -0
package/src/generated/orbpro/events-abi.js +206 -0
package/src/generated/orbpro/events-abi.ts +319 -0
package/src/generated/orbpro/propagator/reference-frame.js +17 -0
package/src/generated/orbpro/propagator/reference-frame.ts +91 -1
package/src/generated/orbpro/propagator-abi.js +17 -0
package/src/generated/orbpro/propagator-abi.ts +17 -0
package/src/generated/spacedatastandards/plg/CCT.d.ts +94 -0
package/src/generated/spacedatastandards/plg/CCT.d.ts.map +1 -0
package/src/generated/spacedatastandards/plg/CCT.js +208 -0
package/src/generated/spacedatastandards/plg/CCT.ts +281 -0
package/src/generated/spacedatastandards/plg/CCTCategory.d.ts +98 -0
package/src/generated/spacedatastandards/plg/CCTCategory.d.ts.map +1 -0
package/src/generated/spacedatastandards/plg/CCTCategory.js +177 -0
package/src/generated/spacedatastandards/plg/CCTCategory.ts +269 -0
package/src/generated/spacedatastandards/plg/CCTCategoryRollup.d.ts +54 -0
package/src/generated/spacedatastandards/plg/CCTCategoryRollup.d.ts.map +1 -0
package/src/generated/spacedatastandards/plg/CCTCategoryRollup.js +106 -0
package/src/generated/spacedatastandards/plg/CCTCategoryRollup.ts +144 -0
package/src/generated/spacedatastandards/plg/PLG.d.ts +46 -2
package/src/generated/spacedatastandards/plg/PLG.d.ts.map +1 -1
package/src/generated/spacedatastandards/plg/PLG.js +78 -5
package/src/generated/spacedatastandards/plg/PLG.ts +90 -5
package/src/generated/spacedatastandards/plg/capabilityClass.d.ts +181 -0
package/src/generated/spacedatastandards/plg/capabilityClass.d.ts.map +1 -0
package/src/generated/spacedatastandards/plg/capabilityClass.js +183 -0
package/src/generated/spacedatastandards/plg/capabilityClass.ts +208 -0
package/src/generated/spacedatastandards/plg/main.d.ts +4 -0
package/src/generated/spacedatastandards/plg/main.d.ts.map +1 -1
package/src/generated/spacedatastandards/plg/main.js +4 -0
package/src/generated/spacedatastandards/plg/main.ts +4 -0
package/src/generated/spacedatastandards/plg/pluginCategory.d.ts +40 -2
package/src/generated/spacedatastandards/plg/pluginCategory.d.ts.map +1 -1
package/src/generated/spacedatastandards/plg/pluginCategory.js +40 -2
package/src/generated/spacedatastandards/plg/pluginCategory.ts +40 -2
package/src/host/browserModuleHarness.js +8 -0
package/src/host/wasiThreadHost.js +189 -14
package/src/index.d.ts +18 -1
package/src/transport/index.js +16 -0
package/src/transport/records.js +1015 -3

package/docs/gpu-module-abi.html ADDED Viewed

@@ -0,0 +1,233 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <meta name="description" content="This document defines the SDK-level standard for modules that can use GPU" />
+    <title>GPU module ABI — Space Data Module SDK</title>
+    <link rel="stylesheet" href="./styles.css" />
+    <!-- SDN_CONSUMER_ASSETS_START -->
+<link rel="stylesheet" href="https://static.spacedatanetwork.org/assets/hd-wallet-ui/2.0.28/sdn-wallet-public-client.c3f68d1cfd88478f10d836a5e829d1dfc6a10157972cf0f7d4d319d0636f2cc4.css" integrity="sha384-fICuhN4I9xqOK1F5vGGzl26opuO+xQIvTZXMSV76lWTBiQ6AfzztMGLLDw8yRT8i" crossorigin="anonymous">
+<script defer src="https://static.spacedatanetwork.org/assets/hd-wallet-ui/2.0.28/sdn-wallet-public-client.f611e7e151a3b5c38384272f8894a4c6634f0a29bf925b0e02e0e27f8db0bfff.js" integrity="sha384-R+QqsKoWJIS7iWrtPmgJ49DVnb1hSGjZokupbLInJd1PLp8RwQhtF/hnaerc33ci" crossorigin="anonymous" data-sdn-wallet-public-client="v1"></script>
+<script defer src="https://static.spacedatanetwork.org/assets/sdn-stack-nav/1.0.0/sdn-stack-nav.52fde607eee38ffa116188201f50258ed50bd18c9f06c1af9678f763147a8fe5.js" integrity="sha384-dgeojhJ8vTszHXIbv7O7nZcEzqD10oUYYJjBmPrV7+kLQEUlXLQD4ek5Q7HOFiO5" crossorigin="anonymous" data-nav-style-url="https://static.spacedatanetwork.org/assets/sdn-stack-nav/1.0.0/sdn-stack-nav.36a36359ce18322185e9ff179f88175bab67d5ad84a14d9c08a54f2ff27267e7.css" data-nav-style-integrity="sha384-c4M8Fg+kYaeOYYtJVr7jJsde24IhSWkWaRyAOHEZU9jozhRck089aw+mnHwxymds" data-wallet-client-url="https://static.spacedatanetwork.org/assets/hd-wallet-ui/2.0.28/sdn-wallet-public-client.f611e7e151a3b5c38384272f8894a4c6634f0a29bf925b0e02e0e27f8db0bfff.js" data-wallet-client-integrity="sha384-R+QqsKoWJIS7iWrtPmgJ49DVnb1hSGjZokupbLInJd1PLp8RwQhtF/hnaerc33ci" data-wallet-style-url="https://static.spacedatanetwork.org/assets/hd-wallet-ui/2.0.28/sdn-wallet-public-client.c3f68d1cfd88478f10d836a5e829d1dfc6a10157972cf0f7d4d319d0636f2cc4.css" data-wallet-style-integrity="sha384-fICuhN4I9xqOK1F5vGGzl26opuO+xQIvTZXMSV76lWTBiQ6AfzztMGLLDw8yRT8i" data-wallet-client-id="sdn-module-sdk-pages-v1" data-wallet-callback-uri="https://digitalarsenal.github.io/space-data-module-sdk/wallet-callback.html" data-wallet-registry-sha256="e1ce6fe903c9700484a8a87d96581c8cad97063dabf63030b4518a31a3bdaa93"></script>
+<!-- SDN_CONSUMER_ASSETS_END -->
+  </head>
+  <body>
+    <a class="skip-link" href="#main">Skip to content</a>
+    <sdn-stack-nav active="module-sdk"></sdn-stack-nav>
+    <header class="site-header">
+      <a class="site-brand" href="./">Space Data Module SDK</a>
+      <nav class="header-links" aria-label="Site">
+        <a href="./byo-wasm-quickstart.html">Quickstart</a>
+        <a href="./conformance.html">Conformance</a>
+        <a href="https://github.com/DigitalArsenal/space-data-module-sdk">GitHub</a>
+        <a class="stack-button" href="#stack">Stack</a>
+      </nav>
+    </header>
+    <div class="shell">
+      <nav class="sidebar" id="sidebar" aria-label="Documentation">
+<h2>Start here</h2><ul>
+<li><a href="./index.html"><span>Harness family matrix</span></a></li>
+<li><a href="./byo-wasm-quickstart.html"><span>BYO-wasm quickstart</span></a></li>
+<li><a href="./conformance.html"><span>Conformance kit</span></a></li>
+<li><a href="./protect-and-sign.html"><span>Protect and sign</span></a></li>
+<li><a href="./publication-submission.html"><span>Publication and listing</span></a></li>
+</ul>
+<h2>Dynamics</h2><ul>
+<li><a href="./families/propagator.html"><span>Propagator</span><span class="tag tag-shipped">shipped</span></a></li>
+<li><a href="./families/maneuver.html"><span>Maneuver</span><span class="tag tag-experimental">experimental</span></a></li>
+<li><a href="./families/propulsion.html"><span>Propulsion</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/attitude.html"><span>Attitude</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/gnc.html"><span>GNC</span><span class="tag tag-planned">planned</span></a></li>
+</ul>
+<h2>Environment and interaction</h2><ul>
+<li><a href="./families/rf.html"><span>RF</span><span class="tag tag-designed">designed</span></a></li>
+<li><a href="./families/sensor.html"><span>Sensor</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/signature.html"><span>Signature</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/environment.html"><span>Environment</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/obstruction.html"><span>Obstruction</span><span class="tag tag-designed">designed</span></a></li>
+</ul>
+<h2>Event physics</h2><ul>
+<li><a href="./families/breakup.html"><span>Breakup</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/reentry.html"><span>Reentry</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/conjunction.html"><span>Conjunction</span><span class="tag tag-designed">designed</span></a></li>
+<li><a href="./families/effects.html"><span>Effects</span><span class="tag tag-planned">planned</span></a></li>
+</ul>
+<h2>Estimation, data and logic</h2><ul>
+<li><a href="./families/estimation.html"><span>Estimation</span><span class="tag tag-experimental">experimental</span></a></li>
+<li><a href="./families/data-source.html"><span>Data source</span><span class="tag tag-shipped">shipped</span></a></li>
+<li><a href="./families/analytics.html"><span>Analytics</span><span class="tag tag-experimental">experimental</span></a></li>
+<li><a href="./families/scheduler.html"><span>Scheduler</span><span class="tag tag-planned">planned</span></a></li>
+<li><a href="./families/behavior.html"><span>Behavior</span><span class="tag tag-planned">planned</span></a></li>
+</ul>
+<h2>Runtime contract</h2><ul>
+<li><a href="./events-abi.html"><span>Event locator ABI</span></a></li>
+<li><a href="./module-publication-standard.html"><span>Module publication standard</span></a></li>
+<li><a href="./browser-wasmedge-isomorphic.html"><span>Browser / WasmEdge isomorphism</span></a></li>
+<li><a href="./isomorphic-pthreads.html"><span>Isomorphic pthreads</span></a></li>
+<li><a href="./tri-runtime-parity.html"><span>Tri-runtime parity</span></a></li>
+<li><a href="./tri-runtime-parity-gate.html"><span>Tri-runtime parity gate</span></a></li>
+<li><a href="./testing-harness.html"><span>Testing harness</span></a></li>
+<li><a href="./language-runtime-matrix.html"><span>Language and runtime matrix</span></a></li>
+</ul>
+<h2>Host surfaces</h2><ul>
+<li><a href="./flatsql-host-contract.html"><span>FlatSQL host contract</span></a></li>
+<li><a href="./flatsql-streaming-standard.html"><span>FlatSQL streaming standard</span></a></li>
+<li><a href="./secrets-capability.html"><span>Credential lanes</span></a></li>
+<li><a href="./protocol-installation.html"><span>Protocol installation</span></a></li>
+<li><a href="./gpu-module-abi.html" aria-current="page"><span>GPU module ABI</span></a></li>
+<li><a href="./module-bundle-runtime-plan.html"><span>Module bundle runtime</span></a></li>
+<li><a href="./isomorphic-sdn-runtime-plan.html"><span>Isomorphic SDN runtime</span></a></li>
+<li><a href="./node-red-default-node-parity.html"><span>Node-RED node parity</span></a></li>
+</ul>
+      </nav>
+      <main class="doc" id="main">
+        <h1>GPU module ABI</h1>
+<p>This document defines the SDK-level standard for modules that can use GPU compute acceleration while remaining portable across browser and WasmEdge module runtimes.</p>
+<h2 id="scope"><a class="anchor" href="#scope" aria-hidden="true">#</a>Scope</h2>
+<p>The standard covers:</p>
+<ul>
+<li>the manifest capability used by module authors</li>
+<li>the host-owned async dispatch boundary used by browsers and native hosts</li>
+<li>the C/C++ layout header shared by module code, browser adapters, and native Dawn-backed hosts</li>
+<li>the artifact layout for portable CPU fallback plus optional GPU adapters</li>
+</ul>
+<p>It does not add a new SDS FlatBuffer schema or a new <code>space_data_module_host</code> sync import. GPU dispatch is asynchronous in browser WebGPU and must stay outside the current sync guest hostcall bridge.</p>
+<h2 id="capability"><a class="anchor" href="#capability" aria-hidden="true">#</a>Capability</h2>
+<p>GPU-capable modules declare the coarse capability id:</p>
+<div class="codeblock"><div class="codeblock-head">json</div><pre><code>{
+  &quot;capability&quot;: &quot;gpu_compute&quot;,
+  &quot;scope&quot;: &quot;webgpu.v1&quot;,
+  &quot;required&quot;: false,
+  &quot;description&quot;: &quot;Optional WebGPU/Dawn compute acceleration.&quot;
+}</code></pre></div>
+<p>Use <code>required: false</code> unless the module has no correct CPU path. A missing GPU adapter must degrade to the module's CPU implementation, not to an incomplete result.</p>
+<p>The <code>gpu_compute</code> id is part of the SDK recommended capability vocabulary. The typed PLG <code>HOST_CAPABILITIES</code> enum cannot carry a dedicated GPU enum value until the canonical standards schema adds one. Until that SDS change lands, module manifests should use the string/object capability form above and avoid claiming a typed PLG host capability enum for GPU.</p>
+<h2 id="artifact-layout"><a class="anchor" href="#artifact-layout" aria-hidden="true">#</a>Artifact Layout</h2>
+<p>The canonical portable artifact remains:</p>
+<div class="codeblock"><div class="codeblock-head">text</div><pre><code>dist/isomorphic/module.wasm</code></pre></div>
+<p>That artifact must be valid without GPU access. Optional GPU adapters belong outside the shared guest binary:</p>
+<div class="codeblock"><div class="codeblock-head">text</div><pre><code>dist/browser/module.js
+dist/browser/module.wasm
+dist/wasmedge/gpu-host.{so,dylib,dll}</code></pre></div>
+<p>The browser adapter owns the browser <code>GPUDevice</code>. The WasmEdge host extension owns the native Dawn instance/device. The guest module owns correctness, fallback, exact refinement, and final result validation.</p>
+<h2 id="abi-layers"><a class="anchor" href="#abi-layers" aria-hidden="true">#</a>ABI Layers</h2>
+<h3 id="1-data-layout-abi"><a class="anchor" href="#1-data-layout-abi" aria-hidden="true">#</a>1. Data Layout ABI</h3>
+<p>The reusable C/C++ header is:</p>
+<div class="codeblock"><div class="codeblock-head">text</div><pre><code>templates/gpu-module/include/space_data_gpu_abi.h</code></pre></div>
+<p>It defines:</p>
+<ul>
+<li><code>SDN_GPU_ABI_VERSION</code></li>
+<li>the <code>gpu_compute</code> capability id and <code>webgpu.v1</code> scope</li>
+<li>status codes</li>
+<li>backend and buffer role enums</li>
+<li>split <code>f64</code> helpers using high/low <code>f32</code></li>
+<li>packed dispatch/result descriptors</li>
+</ul>
+<p>All multi-byte fields are little-endian in serialized buffers. Structs in the header are fixed-width and intentionally avoid owning pointers. Pointers are runtime-local implementation details and must not appear in durable manifests, publication metadata, or cross-process descriptors.</p>
+<h3 id="2-host-dispatch-abi"><a class="anchor" href="#2-host-dispatch-abi" aria-hidden="true">#</a>2. Host Dispatch ABI</h3>
+<p>The canonical operation is:</p>
+<div class="codeblock"><div class="codeblock-head">text</div><pre><code>gpu_compute.dispatch.v1</code></pre></div>
+<p>The host adapter receives:</p>
+<ul>
+<li>an ABI version</li>
+<li>a stable kernel id</li>
+<li>storage/uniform buffer descriptors</li>
+<li>little-endian input bytes</li>
+<li>requested workgroup counts</li>
+<li>declared output buffer sizes</li>
+</ul>
+<p>The host adapter returns:</p>
+<ul>
+<li>a status code</li>
+<li>backend metadata (<code>browser-webgpu</code>, <code>dawn-native</code>, or <code>cpu-fallback</code>)</li>
+<li>output buffer bytes</li>
+<li>optional counters such as candidates emitted, overflow count, and elapsed device time</li>
+</ul>
+<p>Browser and native hosts may expose this through their existing async capability adapter registries. A shared browser/WasmEdge guest must not depend on raw asynchronous wasm imports for this operation.</p>
+<h3 id="3-module-level-api"><a class="anchor" href="#3-module-level-api" aria-hidden="true">#</a>3. Module-Level API</h3>
+<p>Module methods should keep the public invoke contract domain-specific. For example, a conjunction assessment module should expose conjunction assessment request/response ports, not generic WebGPU command buffers.</p>
+<p>The GPU dispatch boundary is an implementation detail between the host runtime and the module/adapter pair. Hosts may precompute a GPU broadphase and pass coarse hits into the guest, or they may let a browser-specific adapter call the guest's exact refinement entry points after dispatch.</p>
+<h2 id="browser-backend"><a class="anchor" href="#browser-backend" aria-hidden="true">#</a>Browser Backend</h2>
+<p>Browser adapters use WebGPU through browser APIs or Emscripten's WebGPU/Dawn surface. They must:</p>
+<ul>
+<li>request and cache the <code>GPUAdapter</code> and <code>GPUDevice</code></li>
+<li>validate device limits before accepting a dispatch</li>
+<li>compile WGSL from a module-owned or SDK-owned source string</li>
+<li>copy results back through mapped buffers or equivalent browser APIs</li>
+<li>return a CPU fallback status when WebGPU is unavailable</li>
+</ul>
+<p>Browser WebGPU setup and buffer mapping are asynchronous. Do not model them as sync <code>space_data_module_host</code> calls.</p>
+<h2 id="wasmedge-backend"><a class="anchor" href="#wasmedge-backend" aria-hidden="true">#</a>WasmEdge Backend</h2>
+<p>WasmEdge deployments that need GPU acceleration should use a native host extension linked against Dawn. The native host implements the same <code>gpu_compute.dispatch.v1</code> operation and uses the same C/C++ layout header.</p>
+<p>The shared module artifact should still be loadable without that extension. A pure <code>[&quot;wasmedge&quot;]</code> artifact may choose a higher-capability native host profile, but a <code>[&quot;browser&quot;, &quot;wasmedge&quot;]</code> artifact must retain the portable fallback contract documented in <code>docs/browser-wasmedge-isomorphic.md</code>.</p>
+<h2 id="numerical-rules"><a class="anchor" href="#numerical-rules" aria-hidden="true">#</a>Numerical Rules</h2>
+<p>GPU kernels that need double-like position precision should use split high/low <code>f32</code> values:</p>
+<div class="codeblock"><div class="codeblock-head">c</div><pre><code>SdnGpuSplitF64 x = sdn_gpu_split_f64(x_km);</code></pre></div>
+<p>For orbital screening, store position components in kilometers unless a module contract states otherwise. The high component is the nearest <code>f32</code>; the low component is the residual:</p>
+<div class="codeblock"><div class="codeblock-head">text</div><pre><code>hi = f32(value)
+lo = f32(value - f64(hi))</code></pre></div>
+<p>GPU broadphase kernels must be conservative. They may emit extra candidates, but they must not drop candidates that the CPU exact path would refine. Exact TCA, probability, and final acceptance logic remain in the CPU double-precision module path unless a module ships a separately validated exact GPU algorithm.</p>
+<h2 id="template"><a class="anchor" href="#template" aria-hidden="true">#</a>Template</h2>
+<p>Start new GPU-capable modules from:</p>
+<div class="codeblock"><div class="codeblock-head">text</div><pre><code>templates/gpu-module/</code></pre></div>
+<p>The template contains:</p>
+<ul>
+<li><code>include/space_data_gpu_abi.h</code>: reusable C/C++ ABI layout header</li>
+<li><code>manifest.json</code>: manifest fragment showing <code>gpu_compute</code></li>
+<li><code>README.md</code>: integration notes for browser WebGPU and WasmEdge/Dawn hosts</li>
+</ul>
+<p>Use the template as a layout and ABI starting point. Real module repos should still define domain-specific FlatBuffer request/response schemas and must keep their canonical compiled artifact at <code>dist/isomorphic/module.wasm</code>.</p>
+        <p class="doc-footer">
+          Source of truth for this page:
+          <code>docs/gpu-module-abi.md</code>. Regenerate with
+          <code>npm run build:docs</code>.
+        </p>
+      </main>
+<nav class="rail" aria-label="On this page"><h2>On this page</h2><ul><li><a class="depth-2" href="#scope">Scope</a></li>
+<li><a class="depth-2" href="#capability">Capability</a></li>
+<li><a class="depth-2" href="#artifact-layout">Artifact Layout</a></li>
+<li><a class="depth-2" href="#abi-layers">ABI Layers</a></li>
+<li><a class="depth-3" href="#1-data-layout-abi">1. Data Layout ABI</a></li>
+<li><a class="depth-3" href="#2-host-dispatch-abi">2. Host Dispatch ABI</a></li>
+<li><a class="depth-3" href="#3-module-level-api">3. Module-Level API</a></li>
+<li><a class="depth-2" href="#browser-backend">Browser Backend</a></li>
+<li><a class="depth-2" href="#wasmedge-backend">WasmEdge Backend</a></li>
+<li><a class="depth-2" href="#numerical-rules">Numerical Rules</a></li>
+<li><a class="depth-2" href="#template">Template</a></li></ul></nav>
+    </div>
+    <section id="stack" class="section" aria-labelledby="stack-title">
+      <div class="section-head">
+        <p class="eyebrow">SDN Stack</p>
+        <h2 id="stack-title">Connected sites</h2>
+      </div>
+      <div class="link-list">
+        <a href="https://spacedatastandards.org/">
+          <span>Standards</span>
+          <small>Canonical schemas, record contracts, and generated bindings.</small>
+        </a>
+        <a href="https://digitalarsenal.github.io/flatbuffers/">
+          <span>FlatBuffers</span>
+          <small>Binary encoding, schema tooling, and runtime documentation.</small>
+        </a>
+        <a href="https://digitalarsenal.github.io/flatsql/">
+          <span>FlatSQL</span>
+          <small>SQL-style queries over FlatBuffer-backed datasets and streams.</small>
+        </a>
+        <a href="https://spacedatanetwork.org/">
+          <span>SDN</span>
+          <small>Distributed publication, discovery, delivery, and marketplace infrastructure.</small>
+        </a>
+        <a href="https://digitalarsenal.github.io/space-data-module-sdk/" class="active">
+          <span>Module SDK</span>
+          <small>WASM module packaging, validation, and host compatibility tooling.</small>
+        </a>
+      </div>
+    </section>
+    <footer class="site-footer">
+      Space Data Module SDK — Apache-2.0. Every ABI page renders a Markdown
+      source in <code>docs/</code>; edit the Markdown, never the HTML.
+    </footer>
+  </body>
+</html>

package/docs/harness-family-matrix.md ADDED Viewed

@@ -0,0 +1,135 @@
+# Harness family matrix
+The Space Data Module SDK exposes one *harness family* per kind of scenario
+behavior. A harness family is a uniform WASM ABI: a named export set, a
+generated wire layout, declared units and frames, named error codes, and a
+conformance kit that proves an implementation satisfies it. A third party
+implements the exports, compiles to WebAssembly, and the module is loadable by
+any consumer of that family — with no modification to the consuming engine.
+A family port that cannot absorb a legitimate module without an engine edit is
+itself the defect.
+## The uniform spine
+Every family is specified and documented against the same spine, in the same
+order. The propagator family is the reference implementation of the spine; read
+[Propagator](families/propagator.html) first, whichever family you are building for.
+| Section | What it fixes |
+| --- | --- |
+| Doctrine | Why this family exists and what it is explicitly not |
+| Capability | What a module of this family is allowed to compute and to touch |
+| Import / export set | The exact symbols the guest must export and may import |
+| Wire layout | Byte-exact structs, generated from a single `.fbs` source |
+| Units and frames | The unit of every field and the reference frame of every vector |
+| Sentinels | The reserved values that mean "absent", "unknown", "refused" |
+| Identity | How an entity is addressed across calls |
+| Threading | The threading model and the shard-write discipline |
+| Error codes | The named negative codes; never a generic `-1` |
+| Lifetime | Init, reuse, and a real idempotent teardown |
+| Parity envelope | What must be byte-identical across browser, WasmEdge and Docker WasmEdge |
+| Consumer seam | How a consuming surface takes the module as a pluggable port |
+| Guest C++ example | A compilable starting point |
+## How a family is built
+1. A single `.fbs` schema is the source of the wire layout. Nothing is
+   hand-written twice.
+2. A generator emits the ABI header (and the JS/TS bindings) from that schema,
+   and a drift gate byte-diffs the generated output against what is committed.
+   A schema edit that is not regenerated fails the gate.
+3. Modules are compiled `wasm32-wasip1-threads`. This is isomorphic by
+   construction: the same artifact runs in the browser, under WasmEdge, and
+   under Docker WasmEdge.
+4. Data in and out of a module is Space Data Standards records, never a bespoke
+   JSON shape.
+5. A conformance kit and a reference module ship with the family. The kit
+   carries its own negative control, so a kit that cannot catch a planted defect
+   fails itself.
+6. The artifact is protected, signed, published and listed. See the integrator
+   path below.
+7. Exactly one generic consumer port exists per family.
+## Status vocabulary
+Status on this site is literal, and is taken from the ratified harness-family
+taxonomy of 2026-08-14. It is not aspirational.
+| Status | Meaning |
+| --- | --- |
+| Shipped | Ratified `.fbs` single source, generated header with a drift gate, conformance kit, reference module. Build against it. |
+| Experimental | Real code exists and the shape is taking form, but it is not frozen and known defects are open. Do not ship a commercial module against it. |
+| Designed | An ABI has been drafted against a real consumer. No generated header, no conformance kit, no reference module has landed. |
+| Planned | A ratified entry in the taxonomy whose individual shape has not been ratified. Nothing is implemented. |
+Only **propagator** and **data-source** are Shipped. **maneuver**,
+**estimation** and **analytics** are Experimental — analytics on the strength
+of ONE sub-harness, [event location](events-abi.html), whose `.fbs`, generated
+header, drift gate, shared runner and measured parity envelope have landed and
+whose conformance kit has not. Only **rf**, **obstruction** and **conjunction**
+are Designed. Every other family is Planned, and its status has not been
+ratified individually — a Planned page states scope and nothing more.
+A sub-harness is not a twentieth family. The nineteen-family taxonomy above is
+owner-ratified: a capability that fits inside a ratified family arrives as a
+sub-harness with its own contract document, and the family page states exactly
+which part of it is shaped.
+Where a family page says a thing does not exist, that is a checked statement
+about the tree today, not a placeholder.
+## Vehicle domains are not a harness family
+Space, air, ground and naval vehicles do not each get a harness. The vehicle
+domain is a declaration in the module manifest — state space, frames, and
+degrees of freedom — consumed by whichever family the module implements. A
+ground-vehicle propagator and a spacecraft propagator implement the same
+propagator export set and differ in the manifest.
+## Harness families are not the runtime `PluginFamily` enum
+Two vocabularies exist and they are not the same list.
+- The **harness-family taxonomy** on this site is the owner-ratified list of
+  ABI-bearing plugin kinds: propagator, maneuver, propulsion, attitude, gnc, rf,
+  sensor, signature, environment, obstruction, breakup, reentry, conjunction,
+  effects, estimation, data-source, analytics, scheduler, behavior.
+- The **`PluginFamily` enum** in `schemas/PluginManifest.fbs` is the SDK's
+  internal manifest classification (`SENSOR`, `PROPAGATOR`, `RENDERER`,
+  `ANALYSIS`, `DATA_SOURCE`, `COMMS`, `SHADER`, `SDF`, `INFRASTRUCTURE`, `FLOW`,
+  `BRIDGE`, `MANEUVER`, `ORBIT_DETERMINATION`, `FOUNDATION`, `PARSER`,
+  `VALIDATOR`, `EXPORTER`, `PUBLISHER`, `BASILISK`). It is what a manifest
+  declares today.
+They overlap but do not correspond one-to-one, and a family in the taxonomy may
+project onto a broader `PluginFamily` member until a dedicated one is minted.
+Do not file a mismatch between the two lists as a bug; the family pages state
+which enum member each family projects onto.
+## Internal plumbing is never a public contract
+Two boundaries are permanent rulings, not maturity gaps:
+- **JavaScript registries are internal engine plumbing.** They are how a
+  consuming engine dispatches to compiled modules. They are never offered as a
+  public extension point. Harness contracts are WASM ABIs only.
+- **Scalar kernel-op ABIs behind closed modules are internal.** In particular
+  the closed scalar `rf_*` kernel ABI is never the public RF contract. The
+  public RF surface is the `.fbs`-defined harness ABI plus the record types
+  a module consumes and emits.
+## The integrator path
+1. [BYO-wasm quickstart](byo-wasm-quickstart.html) — multi-translation-unit C++
+   against the pinned `wasm32-wasip1-threads` toolchain, to a loadable artifact.
+2. [Conformance kit](conformance.html) and the
+   [tri-runtime parity gate](tri-runtime-parity-gate.html) — prove the ABI, then
+   prove byte-identical behavior in every lane.
+3. [Protect and sign](protect-and-sign.html) — encrypt the payload where the
+   module is closed, attach the manifest, sign the artifact.
+4. [Publication and listing](publication-submission.html) — the publication
+   record layout, delivery, and the current state of self-serve listing.
+An LLM building a module against this SDK should start at
+[llms.txt](llms.txt).