Skip to content

licensing.md

Latest commit

 

History

History
30 lines (22 loc) · 2.46 KB

licensing.md

File metadata and controls

30 lines (22 loc) · 2.46 KB
Raw

Licensing Architecture

Status: Docs-only synthesis Date: 2026-05-20

VisionFlow combines repositories with different licence obligations. This page is a map, not legal advice.

Repository Licence described in docs Practical boundary
VisionFlow AGPL 3.0 (MPL 2.0 relicense proposed); the code ecosystem it documents is AGPL-3.0-only across all four code repos Documentation and static website assets
VisionClaw AGPL 3.0 only (LICENSE + Cargo.toml); an MPL 2.0 relicense is proposed — LICENSE.MPL ships in-tree but is not operative Knowledge engineering substrate and GPU/XR application code
agentbox AGPL 3.0 Networked agent runtime and management API
solid-pod-rs AGPL 3.0 Solid/JSS foundation library and server
nostr-rust-forum AGPL 3.0 per ecosystem docs; workspace crates may carry crate-level terms Forum kit, Cloudflare Workers, relay/governance UI
dreamlab-ai-website Deployment repo; inherits obligations from consumed kit/components Branded site, operator config, deployment workflows
vowl-wasm MIT (clean-room reimplementation of the VOWL notation; carries the upstream WebVOWL MIT notice for attribution) Standalone library outside the AGPL boundary, like prose-sanitiser and diagram-ir; consumed as a crates.io / npm dependency, never linked into an AGPL substrate
knowledgeGraph ODbL-1.0 data, AGPL-3.0 pipeline Published corpus and build pipeline; explorer frontend consumes vowl-wasm as a dependency
visionGraph Authoring vault; publishing pipeline under the knowledgeGraph terms Deploys narrativegoldmine.com from the published vowl-wasm bundle

Boundary Rule

Treat protocol and server components derived from or linked against the JSS/Solid stack as AGPL-sensitive unless the owning repository states otherwise. VisionClaw is AGPL 3.0 only today, so no MPL/AGPL import boundary currently applies and the ecosystem's substrates are uniformly AGPL-sensitive; if the proposed MPL 2.0 relicense becomes operative, the import-boundary review returns.

Open Licensing Questions

  1. Which nostr-rust-forum crates are intended for independent publication, and under what crate-level licence?
  2. Does VisionClaw link to AGPL code at build time, call it over process/HTTP boundaries, or both?
  3. Are generated schemas, fixtures, and protocol docs intended to be reusable outside AGPL repos?
  4. What commercial licensing path applies when an enterprise deployment combines all five substrates?