Record IP framing of the three products: 3 patent applications + 3 marks (StarForth, StarshipOS/LithosAnanke, Compudynamics)

The three-product split is treated as three patent applications, each matched
to a trademark (decided 2026-08-29):

  - Patent 1 + mark StarForth                  -> hosted/interpreted runtime
  - Patent 2 + marks StarshipOS (canonical spelling; noted as "StarshopOS"
    in the decision words) + LithosAnanke       -> full standalone OS
  - Patent 3 + mark Compudynamics               -> Zynq steady-state machinery
    with sealed executions, HOL-proven, anchored by the physics-adaptive runtime

Flagged open for counsel (not assumed/filed): the repo already carries a
"Patent pending" USPTO provisional filed Dec 2025 for the Compudynamics
physics-adaptive runtime (docs/patent/). Whether patent 3 is a continuation/
refinement of that provisional, and whether the three product applications are
additive to or fold it in, must be reconciled. Records intent only; no legal
text drafted or filed. Authoritative form in ROADMAP.md; FABRIC-3.md tracks it.

FABRIC-3.md

@@ -3512,3 +3512,13 @@ product: hardware-enforced sealed executions and steady-state machinery machine-
 proof assistant (HOL); delivery is the bitstream + HOL proof artifacts. Product 3 is born on
 the FPGA and its existence is what cleanly separates 1 from 2 from 3. Full form in
 `ROADMAP.md` "Release Versioning Policy → The FPGA creates a three-product split".
+
+**IP framing, decided 2026-08-29.** The three products are treated as three patent
+applications with a matching mark each: Patent 1 + **StarForth** (hosted runtime); Patent 2 +
+**StarshipOS + LithosAnanke** (full standalone OS); Patent 3 + **Compudynamics** (Zynq
+steady-state/sealed-execution HOL-proven hardware, anchored by the physics-adaptive runtime).
+Open for reconciliation with counsel: the repo already has a **"Patent pending"** USPTO
+provisional (filed Dec 2025) for the Compudynamics physics-adaptive runtime (`docs/patent/`);
+patent 3 and the three product applications must be positioned relative to it (continuation?
+additive?) — recorded as intent here, nothing filed or drafted. Authoritative form in
+`ROADMAP.md` "IP framing of the three products".

docs/lithosananke/ROADMAP.md

@@ -83,6 +83,28 @@ through 3 as separate tracks, is defined at v2.5.0 close / during the coloring-i
 (This complements, and does not retract, the existing "hardware bare-metal release" policy
 above.)
 
+**IP framing of the three products — 3 patent applications + 3 marks, decided 2026-08-29.**
+The three products are treated as **three patent applications**, each matched to a trademark,
+with one caveat about the pre-existing provisional:
+
+- **Patent 1 + mark StarForth.** The hosted/interpreted StarForth runtime product.
+- **Patent 2 + marks StarshipOS + LithosAnanke.** The full standalone OS
+  (LithosAnanke → StarshipOS). (Noted as "StarshopOS" in the 2026-08-29 decision words;
+  canonical repo spelling and mark is **StarshipOS** — confirmed as the literal mark
+  to register.)
+- **Patent 3 + mark Compudynamics.** The Zynq hardware steady-state machinery with sealed
+  executions, HOL-proven — anchored by the physics-adaptive runtime.
+
+**Relationship to the existing provisional (must be reconciled, not assumed).** The repo
+already carries a **"Patent pending"** USPTO **provisional filed December 2025** for the
+physics-grounded self-adaptive runtime (the Compudynamics adaptive runtime), sourced in
+`docs/patent/` and referenced in `README.md`. Compudynamics is therefore already staked as
+the brand of that foundation. Open points to resolve with counsel before any filing, so
+nothing is invented or double-filed: is patent 3 the continuation/refinement of that
+provisional (its HOL hardware realization) or a fresh application? Are the three product
+applications additive to, or folding in, the Dec-2025 provisional? This record states intent;
+it does not file, claim, or draft legal text.
+
 **Before the FPGA — "coloring in", decided 2026-08-29.** The period between the all-three
 bare-metal cut (v2.5.0) and starting the Zynq is finishing/hardening work that thickens the
 shape of what already exists rather than adding new silicon. This is not idle time; it is