@hyperscale0/udl 1.0.0-rc.1 → 1.0.123

package/CHANGELOG.md

@@ -1,214 +1,8 @@
 # Changelog
 
-All notable changes to this package are documented here. The format follows
-[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this package
-follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+## 1.0.123
 
-Format version and package version are different numbers. Format 1 is unstable
-until the package reaches 1.0.0; any change to what format 1 accepts is listed
-here under the release that made it.
-
-## [Unreleased]
-
-## [1.0.0-rc.1] - 2026-09-02
-
-### Added
-
-- Stable `UDL####` diagnostics include a category, fix, message, and JSON path.
-- Evolution comparison returns coded issues instead of strings.
-- `canonicalDigest` returns a promise for SHA-256 over canonical UTF-8 bytes.
-- `udl canon` prints canonical bytes or their digest, and `udl explain` prints
-  the catalog entry for one code.
-- The conformance runner has evolution pairs and pins canonical digests, issue
-  codes, and paths.
-- Eight guides, generated clause, diagnostic, and command references,
-  `llms.txt`, `llms-full.txt`, and an agent skill now ship with the package.
-
-- `reconcile` declares one expectation about money an action cannot see yet:
-  the amount path, currency field, direction, the ref naming the provider-side
-  row, exactly one evidence source, a match law, and a window. The match law is
-  `exact`, `tolerance` bounded by a `reconcile_tolerance` dial, or `window`. An
-  expectation that never matches by the end of its window is carried by the
-  named exception child, capped by `maxOpen`. The child is declared and
-  validated at admission, not materialized: the transition refuses with
-  `state_conflict` naming it and the due sweep re-arms the expectation.
-  `UdlReconcile` exposes the clause type.
-- An action may declare a `quote` offer and exactly one other action may spend
-  it through `commit`. Both the base money field and the net destination are
-  mandatory members of `fixes`, and `fixes` and `updates` may not overlap.
-
-### Removed
-
-- `requiresSettlement` and `UdlRequiresSettlement` are gone. A payout-owning
-  instrument now declares exactly one action carrying `reconcile` against a
-  debit statement line, under any match law. There is no wrapper and no alias.
-
-### Changed
-
-- The npm package includes `docs/` and `skills/`.
-- Derived effect rows for `quote`, `commit`, and `reconcile` change the canonical
-  bytes of stored documents that carry `effects` for those clauses.
-- Format 1 now carries every instrument contract clause. Instrument metadata
-  includes archetype template, navigation, visibility, dials, caller-parked
-  states, and extensible subjects. Actions include check gates, remainder
-  arithmetic, field updates, principal policy, and sandbox failure points.
-- Remainder clauses declare their computed money refs, so computed money has
-  one authored source.
-- Evolution snapshots protect lifted clauses that affect composition,
-  admission, or execution. Navigation, examples, and parked-state reason text
-  remain editable presentation.
-
-## [1.0.0-beta.1] - 2026-08-29
-
-- This is the first beta and has no package behavior changes from
-  1.0.0-alpha.5.
-
-## [1.0.0-alpha.5] - 2026-08-29
-
-### Added
-
-- Actions may declare a camelCase `publicAction` as their author-approved public
-  name while the action key remains the lifecycle and execution identity. System
-  due actions must omit it. `udlPublicActionSchema` is exported for consumers
-  that admit the same name outside a complete document.
-- `captureInput` maps declared action input fields into durable receipt refs.
-  Declare only input properties from that action and allocate each captured key
-  in the instrument's shared ref namespace.
-- `signedSum` computes stored add and subtract subtotals over typed child money,
-  then captures one net amount for exactly one payout or instrument transfer. Authors
-  must declare the child reference, money field, currency, admitted statuses,
-  and explicit negative and zero policies.
-- `requiresExposure` gates a child amount against a stored cap, with an optional
-  anchor-specific cap, and `setsAt.marker` records occurrence timestamps that
-  cannot drive a due condition or deadline. Use these clauses for bounded
-  installment writes and per-anchor occurrence markers.
-- `distribute` allocates one parent money field or remainder-computed money ref
-  across typed children selected by status and stored weight. The validator
-  resolves the parent, weight, statuses, and pool before admitting the document.
-- Instruments may declare up to four `derivedAmounts`. Each rule computes a declared
-  money field as 1 through 9,999 basis points of another declared money field
-  with floor rounding. Callers supply neither the result nor a fixed or tiered
-  rule, and a rule may not derive a field from itself.
-- Actions may declare one `payout` intent that reads stored money, currency,
-  source-account, and beneficiary values and captures the payout reference.
-  This does not add an operation to the seven-instruction kernel.
-- A system-only `requiresSettlement` transition may read a captured payout
-  reference and capture the durable evidence record that matched it. The
-  validator rejects caller input, decision ports, public actions, due and
-  deadline triggers, kernel steps, and money moves on that transition.
-- `validateUdlJsonSchema` validates one schema against UDL's sealed JSON Schema
-  subset without applying it to a value. `UdlPayout` and
-  `UdlRequiresSettlement` expose the new clause types to TypeScript consumers.
-
-### Changed
-
-- Evolution snapshots freeze public actions, captured receipt input,
-  distribution rules, exposure gates, signed sums, computed money clauses, and
-  derived-amount arithmetic once a instrument has live instances. Older snapshots
-  remain readable when those keys are absent.
-- Evolution snapshots freeze both payout intents and settlement evidence gates.
-- Receipt refs written by the new clauses share the instrument ref namespace with
-  kernel captures, input captures, signed sums, subject refs, and unwind refs.
-
-## [1.0.0-alpha.4] - 2026-08-26
-
-### Removed
-
-- `diffUdlEvolution`. It validated both arguments and then handed off to
-  `diffValidatedUdlEvolution`, and nothing called it: `udl diff` and the
-  engine's composer both take the validated door. Two doors onto one comparison
-  meant every caller first had to work out which one it was standing in.
-  Validate with `validateUdl` or `assertValidUdl`, then call
-  `diffValidatedUdlEvolution`, whose `UdlDocument` parameters keep the compiler
-  on the right side of that rule.
-
-## [1.0.0-alpha.3] - 2026-08-25
-
-### Changed
-
-- `diffUdlEvolution` validates both arguments, so a document `validateUdl`
-  refuses now throws a `UdlError` carrying that document's issues where
-  alpha.2 returned evolution violations. Measured on
-  `conformance/valid/protection.udl` with the product renamed to
-  `protection_v2` and the live `claim` instrument dropped: alpha.2 returned three
-  violations, naming the rename, the removed live instrument, and the version that
-  did not move; this release throws `invalid_semantics` at
-  `$.instruments[0].aggregateInvariants[0].childInstrumentId`, because another instrument's
-  aggregate still references `claim`.
-
-  Read the throw as a refusal to judge, not as a verdict of no violations.
-  A `catch` that treats it as a schema problem and carries on has skipped the
-  append-only check entirely, and the candidate above is exactly the kind that
-  then sails through: dropping a live instrument is the headline violation the law
-  exists to catch. Fix the document, or use `diffValidatedUdlEvolution`.
-
-  The parameters are `unknown` because the function now accepts input nobody
-  has parsed. A caller who wants the compiler checking the call should hold
-  two validated documents and use `diffValidatedUdlEvolution`, which keeps the
-  `UdlDocument` parameter types.
-
-### Fixed
-
-- The evolution exports no longer route around the validator. `diffUdlEvolution`
-  took typed `UdlDocument` arguments and called neither `validateUdl` nor
-  `assertValidUdl` before reaching the diff's comparison key, so a caller
-  handing it an object it had never parsed got a `RangeError` off the call
-  stack where `validateUdl` returns a `resource_limit` issue for the same
-  object. It takes `unknown` now and validates both arguments.
-- The comparison key behind every diff carries the same depth budget the
-  validator applies to a document (`UDL_LIMITS.maxDepth`, 24 levels; the
-  deepest conformance document reaches 12). This is what protects
-  `diffInstrumentEvolution`, which takes snapshots no validator has seen, and it
-  closes the case where `snapshotUdlInstrument` returns a cyclic snapshot that only
-  detonates when something later stringifies it.
-
-### Added
-
-- `diffValidatedUdlEvolution`, the same comparison for a caller holding two
-  documents `validateUdl` has already admitted. It keeps the `UdlDocument`
-  parameter types, and it is the door for judging a candidate that is not yet
-  valid on its own. It also skips a validation the caller has already paid
-  for: on the commerce-escrow fixture `validateUdl` costs 0.57 ms against the
-  diff's 0.38 ms, so `udl diff`, which parses both files first, takes this
-  door rather than validating four documents to compare two.
-
-## [1.0.0-alpha.2] - 2026-08-23
-
-### Fixed
-
-- `bin` points at the built JavaScript; alpha.1's registry metadata pointed at
-  TypeScript source. npm builds the packument from package.json as it sits on
-  disk after `postpack`, so the pack-time rewrite never reached `bin`, and
-  every install linked `.bin/udl` to `src/cli.ts`, which Node refuses to
-  execute.
-
-### Changed
-
-- Licensed AGPL-3.0-only with a commercial license from Hyperscale LLC;
-  copyright holder Hyperscale LLC; repository renamed to
-  `hyperscale0/hyperscale-udl`.
-
-## [1.0.0-alpha.1] - 2026-08-22
-
-First public release. Format version 1.
-
-### Added
-
-- `spec/udl.schema.json`, JSON Schema 2020-12 generated from the grammar, plus
-  `spec/README.md` carrying the ten laws, the canonical form, and the issue
-  codes.
-- `conformance/`, the format's semantic spec as data: 7 valid documents with
-  their canonical bytes and 11 refused documents with the issue codes and JSON
-  paths they must report, runnable from any language.
-- The `udl` command: `udl validate`, `udl fmt [--write]`, and `udl diff`.
-- `bun run spec:check`, which fails when the committed schema drifts from the
-  grammar it was generated from.
-
-[Unreleased]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-rc.1...HEAD
-[1.0.0-rc.1]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-beta.1...v1.0.0-rc.1
-[1.0.0-beta.1]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-alpha.5...v1.0.0-beta.1
-[1.0.0-alpha.5]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-alpha.4...v1.0.0-alpha.5
-[1.0.0-alpha.4]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-alpha.3...v1.0.0-alpha.4
-[1.0.0-alpha.3]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-alpha.2...v1.0.0-alpha.3
-[1.0.0-alpha.2]: https://github.com/hyperscale0/hyperscale-udl/compare/v1.0.0-alpha.1...v1.0.0-alpha.2
-[1.0.0-alpha.1]: https://github.com/hyperscale0/hyperscale-udl/releases/tag/v1.0.0-alpha.1
+First unified release. Every public Hyperscale package now ships under one
+version that follows the platform release number, so release 123 is 1.0.123.
+The compiled contract format is UDL 1 and the HSX header-manifest edition is
+HSX 1.

package/LICENSE.md

@@ -0,0 +1,356 @@
+# Hyperscale Intellectual Property and Copyright License
+
+Version 1.0, effective 18 September 2026. This text is under review by
+Hyperscale LLC's counsel. Until a revised version replaces it, it states the
+terms on which Hyperscale makes the Software available.
+
+SPDX identifier: `LicenseRef-Hyperscale-IPCL-1.0`
+
+Copyright (c) 2026 Hyperscale LLC. All rights reserved.
+
+This is not an open source license. The Software is proprietary. Hyperscale
+publishes some of it so that you can read it, learn it, build on the Hyperscale
+platform with it, and verify what Hyperscale runs. Publishing is not a gift of
+rights. Every right not written in this License stays with Hyperscale.
+
+---
+
+## 1. Acceptance
+
+By accessing, viewing, downloading, cloning, installing, copying, compiling,
+running, or otherwise using any part of the Software, you accept this License.
+If you do not accept it, do none of those things. If you act for an
+organisation, you confirm you have authority to bind it, and "you" means that
+organisation and every person acting for it.
+
+## 2. Definitions
+
+"Hyperscale" means Hyperscale LLC, a limited liability company organised under
+the laws of the Kingdom of Saudi Arabia, and its successors and assigns.
+
+"Software" means every work Hyperscale distributes under this License, in any
+form: source code, compiled or bundled code, schemas, grammars, standard
+libraries, headers, example programs, fixtures, conformance cases, generated
+artifacts, documentation, designs, images, and data files, and every update,
+version, or part of any of them.
+
+"Specification" means the parts of the Software that Hyperscale designates as a
+Specification in the applicable Notice: a schema, grammar, wire format,
+manifest format, vocabulary, or interface description, together with its
+documentation and published example inputs and outputs.
+
+"Hyperscale Platform" means the products and services Hyperscale offers or
+operates, in any form and under any name, including Hyperscale Arc, Architect,
+Composer, the Hyperscale engine, portals, registries, hosted compilers, hosted
+MCP servers, generated SDKs, and every successor product.
+
+"Notice" means the file named `NOTICE` or `NOTICE.md`, or the license
+statement in a package manifest, that accompanies a copy of the Software and
+states which Tier under section 4 applies to it.
+
+"Tier" means one of the three permission levels in section 4.
+
+"Derivative Work" means any work that is based on, incorporates, translates,
+adapts, ports, reimplements, transforms, or is derived from the Software or any
+part of it, in any language or form, including a work produced by studying the
+Software and then writing new code that performs the same function.
+
+"Competing Product" means any product, service, library, platform, or tool,
+whether or not sold, that performs or is offered as performing substantially the
+same function as the Hyperscale Platform or any part of it, including: a
+language, compiler, or checker for financial programs; an engine, runtime, or
+ledger that executes financial product definitions; a framework for declaring,
+conforming, or operating bank or payment provider adapters; a service that
+generates APIs, SDKs, or agent tools from a financial product definition; or a
+hosted or embedded version of any of those. A product you build on the
+Hyperscale Platform for your own customers is not a Competing Product.
+
+"Hosted Use" means making the functionality of the Software available to any
+third party over a network, whether as a service, an API, an agent tool, an
+embedded feature, or otherwise.
+
+"Contribution" means any work of authorship you intentionally submit to
+Hyperscale for inclusion in the Software, by any means, unless you clearly mark
+it "not a contribution".
+
+"Marks" means the names, logos, and trade dress of Hyperscale and its products,
+including "Hyperscale", "Hyperscale Arc", "HSX", "UDL", "ADL", "Architect",
+"Composer", the `hyperscale0` GitHub organisation, the `@hyperscale0` npm
+scope, and every confusingly similar name or sign.
+
+"Confidential Material" means Software distributed under Tier 3, and any part
+of the Software that Hyperscale has not made publicly available.
+
+## 3. Ownership
+
+Hyperscale owns all right, title, and interest in the Software, the
+Specifications, the Marks, and every Derivative Work Hyperscale creates,
+including all copyright, patent, trade secret, design, database, and moral
+rights, worldwide. The Software is licensed, not sold. This License transfers
+no ownership of anything to you. Your possession of a copy, in any form, gives
+you no right in it beyond what this License states.
+
+The Specifications describe how the Hyperscale Platform works. The design
+choices they record, the vocabulary they fix, the structure of the financial
+programs, products, ledgers, and adapters they define, and the standard library
+of financial instruments Hyperscale publishes are Hyperscale's intellectual
+property. Publication does not place any of it in the public domain.
+
+## 4. Tiers of permission
+
+Every copy of the Software carries a Notice naming its Tier. If a copy carries
+no Notice, Tier 3 applies. A permission granted at a higher-numbered Tier is
+never implied at a lower-numbered one.
+
+### Tier 1: Open Specification
+
+For Software designated as a Specification, Hyperscale grants you a worldwide,
+non-exclusive, non-transferable, royalty-free, revocable license to:
+
+1. read, copy, and redistribute the Specification, unmodified and with all
+   notices intact;
+2. write programs, documents, and data that conform to the Specification, and
+   use them in any way, including commercially;
+3. write and distribute software that reads, writes, validates, or displays
+   data conforming to the Specification, solely for the purpose of using or
+   interoperating with the Hyperscale Platform or with products built on it;
+4. quote reasonable portions of the Specification in documentation, teaching,
+   and commentary, with attribution to Hyperscale.
+
+Tier 1 does not permit you to build a Competing Product, to publish a modified
+Specification under any name that includes or resembles a Mark, or to claim
+conformance or compatibility except as section 8 allows.
+
+### Tier 2: Source Available
+
+For Software designated as Source Available, Hyperscale grants you a worldwide,
+non-exclusive, non-transferable, non-sublicensable, royalty-free, revocable
+license to:
+
+1. view, download, and study the source;
+2. install, compile, and run the Software, unmodified or modified, on systems
+   you control, for the purpose of building, testing, operating, and
+   maintaining your own products on the Hyperscale Platform;
+3. modify the Software for that purpose and keep the modification for your own
+   internal use;
+4. submit modifications to Hyperscale as Contributions;
+5. redistribute unmodified copies of the Software, in the form Hyperscale
+   published them, with all notices and this License intact, for example by
+   mirroring a package or vendoring a dependency.
+
+Tier 2 does not permit Hosted Use, distribution of modified copies,
+distribution of compiled or bundled forms other than those Hyperscale
+published, or any use in or toward a Competing Product.
+
+### Tier 3: Confidential
+
+For Software designated as Confidential, or carrying no Notice, Hyperscale
+grants you only the license written in the agreement under which you received
+it. If there is no such agreement, you have no license, and you must not use,
+copy, disclose, or retain the Software. Confidential Material includes generated
+SDKs, downloadable product artifacts, private repositories, and anything you
+obtain through a portal, a registry, or a signed-in session. You may use
+Confidential Material only for your own organisation's Hyperscale integration,
+must not publish it to any public repository or package registry, must not
+disclose it beyond personnel and contractors who need it and are bound by
+confidentiality at least as protective as this License, and must destroy it on
+request or when your access ends.
+
+## 5. Restrictions
+
+Whatever the Tier, you must not, and must not help or allow anyone else to:
+
+1. build, contribute to, market, sell, or operate a Competing Product using
+   the Software, a Derivative Work, or knowledge gained from the Software;
+2. create a Derivative Work except as Tier 2 permits for internal use;
+3. reimplement, port, translate, or clone the Software or any part of it, in
+   any programming language, whether by copying or by studying it and
+   rewriting it;
+4. offer the Software or a Derivative Work for Hosted Use;
+5. sublicense, sell, rent, lease, lend, or assign the Software or any right in
+   it;
+6. remove, hide, or alter any copyright, trademark, license, or attribution
+   notice, or misstate the origin of the Software;
+7. reverse engineer, decompile, disassemble, or unminify any compiled, bundled,
+   or generated form of the Software, except where a law forbids this
+   restriction and only to the extent it does;
+8. circumvent, disable, or evade any license check, access control, rate limit,
+   key, or technical protection in the Software or the Hyperscale Platform;
+9. use the Software, the Specifications, or any output of the Hyperscale
+   Platform as training, fine-tuning, evaluation, or retrieval data for any
+   machine-learning model, or to generate a Competing Product with such a
+   model, without Hyperscale's prior written consent;
+10. use the Software to benchmark or compare the Hyperscale Platform in any
+    publication without Hyperscale's prior written consent;
+11. register, apply for, or claim any patent, trademark, design, or domain
+    name that covers or resembles the Software, the Specifications, or the
+    Marks;
+12. use the Software in violation of any law, sanction, or export control;
+13. use the Software for any purpose this License does not expressly permit.
+
+## 6. Contributions
+
+You are not required to contribute. If you do, then on submission you grant
+Hyperscale, and everyone who receives the Software from Hyperscale, a
+perpetual, worldwide, non-exclusive, irrevocable, royalty-free license to use,
+reproduce, modify, distribute, sublicense, and relicense your Contribution
+under any terms, including this License and any commercial license, and you
+grant Hyperscale a patent license of the same scope covering the claims your
+Contribution alone or in combination with the Software would infringe. You
+confirm you have the right to make these grants and that the Contribution is
+your own work or that you have permission to submit it. Hyperscale may require
+a signed contributor agreement before merging any Contribution and may decline
+any Contribution for any reason. Feedback, suggestions, and ideas you send
+about the Software are not confidential and Hyperscale may use them freely.
+
+## 7. Marks
+
+This License grants no right to any Mark. You may refer to the Software and to
+the Hyperscale Platform by name to describe truthfully that your product uses
+or integrates with them. You must not use any Mark as or in the name of your
+product, company, package, domain, or repository, in a logo, or in any way that
+suggests Hyperscale made, sponsors, certifies, or endorses your work.
+
+## 8. Conformance and compatibility claims
+
+You may state that your product "conforms to" or "is compatible with" a named
+Specification version only if, at the time of the claim, your product
+validates against the Specification exactly as Hyperscale published it, using
+Hyperscale's published example inputs unmodified, and you built the product
+under Tier 1 for the purpose of interoperating with the Hyperscale Platform.
+The claim is a statement about your product and never an endorsement by
+Hyperscale. Hyperscale may require you to withdraw a claim it considers false.
+No claim of conformance permits a Competing Product.
+
+## 9. Commercial license
+
+Hyperscale offers a commercial license to organisations whose use falls
+outside this License, including Hosted Use, distribution of modified copies,
+embedding in a proprietary product, or any use a procurement policy cannot
+accept under these terms. Ask through <https://hyperscale0.ai>. Nothing in this
+section grants any right until a commercial agreement is signed.
+
+## 10. Prior releases
+
+Any version of the Software that Hyperscale released under a different license
+remains available under that license for that version only. This License
+applies to every version that carries it and to every later version unless
+that version states otherwise. Nothing in this License narrows a right you
+already hold in a prior version under its own license.
+
+## 11. Term and termination
+
+This License takes effect when you accept it and lasts until terminated. It
+terminates automatically, with no notice, the moment you breach section 5 or
+section 7. For any other breach, it terminates thirty days after Hyperscale
+notifies you, unless you cure the breach within that period and it is the
+first notice you have received. Hyperscale may also terminate this License for
+convenience for any Tier 3 material, on notice. On termination you must stop
+all use, destroy every copy in your possession or control, including
+Derivative Works, and confirm destruction in writing if asked. Sections 3, 5,
+6, 7, 11, 12, 13, 14, 15, and 16 survive termination.
+
+## 12. Disclaimer of warranty
+
+The Software is provided "as is" and "as available". Hyperscale makes no
+warranty of any kind, express, implied, or statutory, including any warranty
+of merchantability, fitness for a particular purpose, title, non-infringement,
+accuracy, or that the Software will be error-free or uninterrupted. Hyperscale
+is not a bank, does not hold money, and gives no assurance that any financial
+program, product, or adapter written with the Software is lawful, licensed,
+or fit for any real-world financial use in any jurisdiction.
+
+## 13. Limitation of liability
+
+To the fullest extent the law allows, Hyperscale is not liable to you or any
+third party for any indirect, incidental, special, consequential, exemplary, or
+punitive damages, or for any loss of profit, revenue, data, goodwill, or
+business opportunity, arising from or related to the Software or this
+License, however caused and under any theory of liability, even if advised of
+the possibility. Hyperscale's total liability under this License is limited to
+one thousand Saudi riyals (SAR 1,000) or the amount you paid Hyperscale for the
+Software in the twelve months before the claim, whichever is greater.
+
+## 14. Indemnity
+
+You will defend, indemnify, and hold harmless Hyperscale, its owners,
+officers, employees, and agents from every claim, loss, damage, liability,
+cost, and expense, including reasonable legal fees, arising from your use of
+the Software, your Derivative Works, your products, or your breach of this
+License.
+
+## 15. Remedies and enforcement
+
+You acknowledge that the Software embodies valuable trade secrets and
+intellectual property of Hyperscale, that a breach of section 3, 4, 5, or 7
+would cause Hyperscale irreparable harm that money alone cannot repair, and
+that Hyperscale is entitled to injunctive and other equitable relief in any
+court of competent jurisdiction to stop or prevent a breach, without posting a
+bond and in addition to every other remedy. You will pay Hyperscale's
+reasonable legal fees and costs in any action in which Hyperscale enforces
+this License and prevails on any claim. Hyperscale may bring an action in the
+courts named in section 16 or in any jurisdiction where the Software is used,
+a Derivative Work is made, or a Competing Product is offered, and you consent
+to the jurisdiction of those courts.
+
+## 16. Governing law and venue
+
+This License is governed by the laws of the Kingdom of Saudi Arabia, including
+the Copyright Law issued by Royal Decree M/41 and its implementing
+regulations, without regard to conflict-of-law rules. The competent courts of
+Riyadh have exclusive jurisdiction over any dispute arising from this License,
+subject to Hyperscale's right under section 15 to enforce elsewhere. The
+Berne Convention and the TRIPS Agreement apply to the protection of the
+Software in every member state. Where a law of another jurisdiction gives you
+a right this License cannot exclude, that right is preserved to the minimum
+extent that law requires and no further.
+
+## 17. General
+
+1. This License is the entire agreement between you and Hyperscale about the
+   Software under its Tier, and replaces every earlier or contemporaneous
+   understanding, except a signed commercial agreement, which prevails where
+   the two conflict.
+2. If any provision is held unenforceable, it is limited to the minimum
+   extent necessary and the rest stays in force.
+3. Hyperscale's failure or delay in enforcing any provision is not a waiver.
+   A waiver is effective only in writing signed by Hyperscale.
+4. You may not assign or transfer this License or any right under it, by
+   operation of law or otherwise, and any attempt is void. Hyperscale may
+   assign it freely.
+5. Hyperscale may publish new versions of this License. Each version of the
+   Software carries the License version it was released under, and a new
+   License version applies only to Software that carries it.
+6. This License is written in English. Hyperscale may publish an Arabic
+   translation. Where a court requires an Arabic text, the certified Arabic
+   translation Hyperscale provides is the text of record; in every other case
+   the English text governs.
+7. Nothing in this License creates a partnership, joint venture, agency, or
+   employment relationship between you and Hyperscale.
+8. Notices to Hyperscale go to the address published at
+   <https://hyperscale0.ai/legal>.
+
+---
+
+## Applying this License
+
+A copy of the Software must carry this file as `LICENSE.md` and a `NOTICE.md`
+that states the Tier. The form is:
+
+```
+This work is licensed under the Hyperscale Intellectual Property and
+Copyright License, version 1.0 (LicenseRef-Hyperscale-IPCL-1.0).
+Copyright (c) 2026 Hyperscale LLC. All rights reserved.
+
+Tier: 2 (Source Available)
+Specifications under Tier 1 in this repository: spec/, docs/grammar.md
+
+Not open source. See LICENSE.md.
+```
+
+A package manifest states `"license": "SEE LICENSE IN LICENSE.md"`. A source
+file may carry the one-line header:
+
+```
+// Copyright (c) 2026 Hyperscale LLC. Licensed under LicenseRef-Hyperscale-IPCL-1.0. Not open source.
+```

package/NOTICE.md

@@ -0,0 +1,8 @@
+This work is licensed under the Hyperscale Intellectual Property and
+Copyright License, version 1.0 (`LicenseRef-Hyperscale-IPCL-1.0`).
+Copyright (c) 2026 Hyperscale LLC. All rights reserved.
+
+Tier: 2 (Source Available)
+Specifications under Tier 1 (Open Specification) in this repository: spec/, docs/
+
+Not open source. See [LICENSE.md](LICENSE.md).