@hyperscale0/hsx 3.0.1 → 3.2.0

package/LICENSING.md

@@ -1,52 +0,0 @@
-# Licensing
-
-The code in this repository is Copyright 2026 Hyperscale LLC and is licensed
-under the GNU Affero General Public License version 3 only
-(`AGPL-3.0-only`). The full text is in [`LICENSE`](./LICENSE).
-
-## What the AGPL asks of you
-
-Two obligations matter in practice.
-
-**If you distribute a copy in object form**, modified or not, you make its
-Corresponding Source available under the same license.
-
-**If you run a modified copy as a network service**, section 13 applies: the
-users interacting with it over the network get an offer of the source of the
-version you are running. Compiling HSX with an unmodified copy behind your own
-service does not trigger this. Changing the lexer, the parser, the lowering, or
-the emitted IR and then serving that change does.
-
-Using `@hyperscale0/hsx` as a library inside your own program is a combined
-work under the AGPL. If that does not fit how you ship, take the commercial
-license instead.
-
-## Commercial license
-
-Hyperscale LLC sells a commercial license to organisations that cannot accept
-the AGPL, for the usual reasons: a proprietary product that links the compiler,
-a hosted service you will not open, a procurement policy that refuses copyleft.
-It grants the same code under ordinary commercial terms with no source
-obligation.
-
-Ask through <https://hyperscale0.ai>.
-
-## The license covers code, not marks
-
-"Hyperscale" and "HSX" are trademarks of Hyperscale LLC. A copyright license
-says nothing about trademarks in either direction, so
-[`TRADEMARKS.md`](./TRADEMARKS.md) draws that boundary.
-
-## The language is not the compiler
-
-HSX the language and its output contract are separate from this compiler. The
-canonical UDL schema published by the UDL repository and the fixtures under
-[`examples/`](./examples) are data describing a language, and anyone may write their own compiler,
-formatter, or runtime against them, in any language, under any license, without
-touching this code.
-
-What you may then say about it is a trademark question, not a copyright one.
-[`TRADEMARKS.md`](./TRADEMARKS.md) has the rule: claim compatibility with an
-HSX IR version only when your implementation emits IR that validates against
-that version's published schema, from the published example programs,
-unmodified.

package/TRADEMARKS.md

@@ -1,35 +0,0 @@
-# Trademarks
-
-"Hyperscale" and "HSX" are trademarks of Hyperscale LLC.
-
-The AGPL covers the code in this repository and nothing else. It grants no
-rights to the marks, and it never mentions them: a copyright license says
-nothing about trademarks either way. This file draws that boundary so nobody
-has to guess where it sits.
-
-What that means in practice:
-
-- **Yes.** Say your project uses HSX, compiles HSX, or reads its internal lowering record.
-  Say it in your README, your docs, your talk, and your package description.
-  Fork this repository and keep the notices intact.
-- **Yes.** Publish an HSX implementation or tool in another language, and name
-  it in a way that describes what it does: `hsx-rs`, `hsx-lsp`, `tree-sitter-hsx`.
-- **No.** Name your project, company, or product in a way that suggests
-  Hyperscale LLC published it or endorses it. `@hyperscale0/*` on npm and the
-  `hyperscale0` GitHub organisation are ours.
-- **No.** Use the marks or our logo in a way that implies affiliation,
-  sponsorship, or certification we have not given.
-
-## Claiming compatibility
-
-An independent implementation may say it "implements HSX IR version X" only
-while it emits canonical UDL that validates against the UDL schema published
-for that version, from the published example programs, unmodified. The UDL
-schema and the programs in [`examples/`](./examples) are the whole
-test: no edited fixture, no local relaxation of the schema.
-
-That claim is a statement about your implementation, so keep the marks out of
-its name and off its logo, and do not present it as endorsement or
-certification by Hyperscale LLC. We certify nothing; the schema does.
-
-If you are unsure, open an issue and ask. Nobody has ever regretted asking.