OSS Policy (zero open-source applications) · oss-policy

Owner directive (2026-07-10), canonical. "Do not use open source software, basically create like them, but stick to optimal development." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:638] — read together with the same prompt's explicitly named stack: "For now, generate with the Holonprint Loop with gaussian splatting, lenis, tailwind, react, next…" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:498]

Content

Ruling (specific-beats-general). The owner issued both a general prohibition and, in the same prompt, a specific named stack. The specific grant governs the general ban:

1. Zero third-party OSS APPLICATIONS / SERVICES. No n8n, no Gitea UI, no ComfyUI, no Jupyter, no Matrix, no hosted OSS panels. Every surface named after such tools ("the Runs with n8n like", "almost like. notebook jupyter", "style of google colab", "like the obsidian knowledge base of antropic … but following the whole HOS model" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:534, :536, :571, :542]) is a custom-built HOS surface in the style of the referenced tool — "basically create like them". Named OSS tools appear in canon only as neuralware capability references the datan may bring from the Academy ("it should go to the academy and bring a new neuralware (N8N, ComfyUI,VisualStudio,Gitea,Servers,APIS,TOOLS, WHATEVER)" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:612]), never as deployed third-party applications.
2. Zero OSS UI kits / runtime helpers. No d3, no mermaid runtime, no syntax-highlighter runtime, no component kits. Diagrams, charts and highlighting are rendered by our own code (pad/pod discipline, petra glass rules).
3. Owner-NAMED libraries stay. The 2026-07-10 prompt names the runtime stack for the holonprint Loop verbatim: "gaussian splatting, lenis, tailwind, react, next, use webgl, JTREE, HTML5, scroll video control, 3D animated elements, physics model as gravity, wave, sparks of electricity, hitbox" [src: :498]. The permitted libraries are therefore: react (cb-react), next (cb-nextjs), tailwind (cb-tailwind), lenis (cb-lenis), gsap (cb-gsap; owner-directed scroll language of royal-orbit and encoded as the site device stack stack: 'gsap' [src: HOS-Webdoc/web/src/lib/cland/types.ts:64]), three (cb-threejs; "JTREE"/webgl), and @sparkjsdev/spark (cb-spark; the gaussian-splatting renderer, spark-renderer).

The policy binds every Run of the spatial-site district and all library-driven builds (pb-002-library-authoring, bp-001-spatial-site): if a capability is not on the named-library list, the squad builds it in-house.

Variants

Open question

Owner to confirm or tighten. Current resolution reads A as a carve-out inside B: zero OSS applications/services and zero OSS UI kits/runtime helpers, while the owner-named libraries (react, next, tailwind, lenis, gsap, @sparkjsdev/spark, three) remain permitted. If "Strictly zero OSS" is intended absolutely, the ruling tightens to a zero-library rewrite: replace the named libraries with in-house equivalents (own reactive renderer, own smooth-scroll, own utility CSS, own splat renderer) in a scheduled sequence of Runs. Please confirm: (a) keep the named-library carve-out, or (b) order the zero-library rewrite.

Composition

• uses: cb-react · cb-nextjs · cb-tailwind · cb-lenis · cb-gsap · cb-threejs · cb-spark (the whitelist), neuralware (OSS-as-reference pattern)
• used-by: spatial-site builds, pb-001-spatial-site-loop, pb-002-library-authoring, sop-003-run-dispatch (dispatch gate: refuse particles that add unlisted dependencies), bm-001-web-perf, bp-001-spatial-site

See also

• gaussian-splatting · spark-renderer · holonprint
• [Owner prompt, archived 2026-07-10](../../../wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md)