@jigging/jig 0.1.0-alpha.2 → 0.1.0-alpha.20

package/LICENSE.md

@@ -0,0 +1,253 @@
+# Jig licensing
+
+## Jig adoption notice
+
+**Bread License 1.0 adopted on 2026-09-21.** Victor Duarte, professionally known
+as zvictor, licenses the Jig material identified below under the retained text.
+This adoption applies from the source commit first carrying this completed
+notice and to subsequent covered Jig source distributed with it. The first
+planned npm release is `@jigging/jig@0.1.0-alpha.17`. Earlier distributions
+retain their existing licenses; this notice does not revoke those grants.
+
+| Field | Jig adoption |
+| --- | --- |
+| Software | Jig: original material in `packages/jig/**` and `docs/jig/spec/**`, excluding separately identified third-party material; the corresponding installed `@jigging/jig` distribution |
+| Licensor | Victor Duarte, professionally known as zvictor, personally; correspondence: c/o Pereirinhos s.r.o., Mateja Bela 8769/30, 010 15 Žilina, Slovakia |
+| Seller | Pereirinhos s.r.o., IČO 53427599, DIČ 2121379700, VAT ID SK2121379700; registered seat: Mateja Bela 8769/30, 010 15 Žilina, Slovakia. The company is authorized to sell and administer Jig company licenses on the Licensor's behalf; ownership remains with the Licensor. |
+| Licensing and notices | `licensing@jig.md`; postal notices use the Licensor correspondence address above |
+| Exact instrument | [Bread License 1.0, finalized text](https://github.com/jiggy/bread/blob/2160335c58eb6b6ea164e29d58fa8160f9a2e0df/LICENSE.md), retained in full below; the unchanged standard bargain |
+| Official release records | [Jig GitHub releases](https://github.com/jiggy/jig/releases) and [npm versions and publication times](https://registry.npmjs.org/@jigging%2fjig), including prereleases; a source commit is licensed source, not by itself a newly published official release for update coverage |
+| Direct prices | Jig schedule P-1.0 in [PRICING.md](PRICING.md), effective 2026-09-21: USD; twelve-month Update Terms |
+| Purchases | Email `licensing@jig.md` for an ordinary order, directly or through a supplier naming the actual customer Group. The authorized seller accepts payment or express credit and sends the customer its coverage record. Email also handles cancellation; no registration platform is required. |
+| Additional grants | None |
+
+The repository is a collection of separately licensed works. [LICENSES.md](LICENSES.md)
+identifies FLOW, documentation, tooling, and third-party exceptions. Bread does
+not relicense those works, independent Flows, or application source. Installed
+packages retain their component notices. The matching GitHub release supplies
+Jig's corresponding source download and build instructions. Jig's build uses
+the license retained in this repository; no checkout of Bread is required.
+
+The following reusable text is retained verbatim. Completing the identifying
+facts above does not amend its standard permissions. Commercial records must
+retain the completed notice, this exact text, and the accepted price schedule.
+
+---
+
+# Bread License 1.0
+
+This license applies only when a rights holder expressly adopts it for identified material. Publishing this reusable text or an example does not, by itself, license any software.
+
+The **Adoption Notice** identifies the **Software** and the **Licensor**, the rights holder giving the permissions in this license. It also identifies the authorized sellers and what they may do, contacts for licensing and notices, official release records, and a dated price schedule. These details cannot narrow this license. Using the Bread name does not combine separate software families, licensors, or payment obligations.
+
+## 1. Permissions and scope
+
+**Software** means the material identified in the Adoption Notice and expressly supplied under this license, including changes to that material. Separately licensed dependencies, protocols, independent applications, and extensions keep their own terms. An Adoption Notice cannot give rights the Licensor does not have.
+
+The Licensor gives you worldwide, nonexclusive permission to inspect, copy, modify, build, run, and distribute the Software for the uses allowed below, provided you follow this license. Official material covered by a purchase under section 4 stays covered by that purchase even if it is later released under different terms. Independent works and separately licensed dependencies remain outside that purchase.
+
+You owe no Software fee merely because the Software helped create a report, generated artifact, or other independent output. Software code included in an output keeps its applicable license.
+
+There is one complete product. You do not need runtime activation, license telemetry, execution metering, or network license checks to exercise these permissions. This is a source-available license, not an OSI-approved open-source license. It does not take away earlier valid permissions. Nothing in this license limits rights you have under fair use, fair dealing, or equivalent copyright exceptions.
+
+## 2. Free use and individual protection
+
+Without paying or registering, you may:
+
+- use the Software for your own personal, non-business activities;
+- use the Software in the operations of a Group with Annual Revenue below US$1 million, as defined in section 3;
+- evaluate the Software at any organization; and
+- inspect, modify, build, test, assess the security of, and prepare contributions to the Software itself.
+
+**Evaluation** means work to decide whether, where, or how to adopt the Software. It includes prototypes, demonstrations, and checks of compatibility, integration, security, and performance. There is no fixed deadline, and you may keep the evaluation's outputs.
+
+Routine work that relies on the Software as an adopted tool is operational use. This includes ordinary product development and internal development infrastructure. Calling that work evaluation does not make it evaluation.
+
+You may run the Software as needed to work on the Software itself under the free permission above. If you also use it operationally, that use still needs its own permission, even if it helps test or improve the Software.
+
+To evaluate, you do not need to declare revenue, have authority to buy for your employer, promise a purchase, or take responsibility for another team's use. You may obtain an optional confirmation, but the permission exists without it. Employer policies and authority to use systems, data, and external services still apply.
+
+Independent business activity, including a sole trader's paid work, follows the business rules regardless of its legal form. A freelancer using their own tools to supply independent outputs uses their own Group's permission. Someone operating a client's deployment uses the client's permission under section 6.
+
+If you work in good faith on an organization's behalf as an employee or individual contractor, the Licensor will not seek organizational license fees or damages from you personally solely because the organization failed to obtain permission. This protection does not excuse your own business obligations, fraud, or separate misconduct. It does not give the organization permission it is missing.
+
+Your personal-use rights in Software you receive last for the duration of copyright, provided you meet their conditions. Free business use lasts only while you qualify. Starting while small does not give your business permanent paid-up rights.
+
+## 3. Business eligibility
+
+### Group and revenue
+
+A **Group** includes the ultimate controlling parent and every entity it controls, directly or indirectly. Control means more than half the voting rights or equivalent enforceable management control. An independent business, including a sole trader, is its own Group. Passive minority investment does not combine Groups. Independently managed public bodies do not become one Group merely because they have the same government owner.
+
+**Annual Revenue** means the Group's consolidated revenue for its last completed financial year, using its consistently applied accounting framework. Exclude revenue from transactions within the Group. Do not add financing, investment proceeds, valuation, or headcount. If the Group has not completed a financial year, use revenue recognized since it was formed; do not scale that amount up to a full year. The same test applies to nonprofits and public bodies.
+
+Convert revenue to US dollars using the European Central Bank reference rates for the last available business day on or before the reporting period's end. Convert through euros if needed. If those rates are unavailable, use a consistent independent published reference.
+
+For an ordinary purchase, a truthful declaration of your revenue band is enough. You do not routinely need to supply accounts, customer lists, or deployment inventories.
+
+### Assessment and growth
+
+Check whether your Group qualifies for free use when it first uses the Software operationally, and once a year after that. Check its purchase band when buying an Update Term. Check free eligibility sooner if you learn of an acquisition or change of control that changes the relevant Group. You do not need to report revenue continuously.
+
+If your Group loses free eligibility in good faith, it has 90 days to obtain permission or stop operational use that lacks permission. Count from the required assessment or from learning of the change of control. You owe no fee for earlier legitimate free use. Revenue of exactly US$1 million does not qualify for ordinary free business use.
+
+Growth and later price changes do not increase the price of rights you have already purchased. A Group using only releases covered by its purchase does not need to buy again merely because it grows.
+
+## 4. Company purchases
+
+### Published purchasing and records
+
+While offering new purchases, the Licensor must publish prices and provide a working way to buy. An ordinary purchase must not require individual negotiation. The authorized seller must have authority to provide the standard coverage and future-release commitments for the identified Software family.
+
+The accepted order must identify:
+
+- the Licensor, seller, and Software family;
+- the customer Group, its ultimate controlling parent, and its revenue band;
+- the exact license and price terms, total price, and taxes; and
+- the start and end of the Update Term.
+
+The customer or someone authorized to buy for it accepts those terms. Permission begins when the authorized seller receives the agreed payment for that order, or expressly accepts an invoice order with a stated payment due date. A quotation or an invoice the seller has not accepted gives no permission.
+
+An order allowing later payment must say who owes the debt. If only the supplier owes it, that debt does not affect the customer's acquired permission. The customer's own payment obligations remain subject to section 8.
+
+The seller must send the customer an order and coverage confirmation it can keep, including the accepted terms and identified official release records. Email or downloadable documents are enough. If permission has been acquired under this section, the seller's failure to send a record does not take it away. Records prove permission; they do not activate the Software. Permission does not depend on keeping access to an account or website.
+
+### Twelve-month minimum and covered releases
+
+An **Update Term** is a purchased period of at least twelve calendar months. This standard does not offer shorter standalone purchases. Sellers may offer longer periods with their prices stated in advance. The whole agreed price is due upfront unless the authorized seller expressly accepts later payment. Paying an installment does not, by itself, buy a shorter Update Term.
+
+**Covered Releases** are all official Software releases first published before or during the Update Term. Any existing material the Licensor lacks authority to license must be specifically identified and excluded before purchase. A later license change, ordinary rename, or new major version does not remove releases that would otherwise be covered by an accepted term. No release or maintenance schedule is promised.
+
+The Update Term includes its start time and excludes its end time, using UTC. It ends on the agreed calendar anniversary; if that day does not exist, use the month's last day. Coverage depends on the official release identifier and first-publication time, not when you download or install it. Official release records must preserve those facts. Replacing a release's contents under the same identifier does not give new material an earlier publication date.
+
+### Company-wide, permanent release rights
+
+For Covered Releases, the Licensor gives the named Group permission to run, copy, back up, modify, integrate, distribute, and operate the Software in its business for the duration of copyright, provided it follows this license. There are no seat, machine, application, workflow, customer, or execution counts. The same permission covers these releases across the Group's products and installations, however it obtains them. It does not cover separately licensed software just because that software also uses Bread.
+
+Coverage includes employees, contractors acting for the Group, and subsidiaries its named parent later creates or acquires. Acquiring an entity that has a license does not extend that license to the new parent's other operations.
+
+An entity leaving the Group keeps its already-purchased Update Term and lasting release rights for its own operations. Those rights do not extend to its new parent's other operations. The retained coverage does not extend to entities the departing entity later creates or acquires. Any transfer or succession rights required by law still apply.
+
+If you do not renew, you can keep using your Covered Releases and their permitted modifications. Your purchase will not cover official releases published after its Update Term ends. A second application using a Covered Release requires no second purchase. An official release not already covered needs applicable permission, even if it is a security update. Section 7 governs later independent modifications.
+
+### Future purchases
+
+Published price changes require 90 days' advance notice to affected existing customers. Those changes apply only to future purchases. Accepted terms and rights already paid for remain unchanged.
+
+Renewals require the customer's agreement. Automatic renewal is optional, and customers must be able to cancel through the purchasing channel or by email. Applicable law and accepted purchase terms govern billing adjustments.
+
+## 5. Distribution and purchases through suppliers
+
+### Sharing software
+
+You may distribute the Software, with or without changes, for free or for a price. Include this license and the source and notices required by section 7. Giving someone a copy does not give them the distributor's company-wide permission. Each recipient receives the applicable free permissions directly and must obtain any additional business permission it needs.
+
+Identify the Software you include, its Licensor, its official release identifiers, any modifications, and the official purchasing channel. Tell recipients that independently operated business installations may need their responsible Group's company license, that an existing purchase may cover these releases, and that section 6 covers access to provider-controlled services. Supplying the Software separately, or asking customers to install it themselves, does not change their permission requirements.
+
+Distributors do not need to investigate recipients' finances, collect their fees, report sales, or obtain product approval. There is no distribution royalty, publisher coverage tier, or restriction on competition. Your own operational use as a distributor needs applicable permission. Merely sharing or mirroring copies does not require a paid company license.
+
+### Arranging a customer's purchase
+
+With a customer's authorization, a supplier may arrange an ordinary section 4 purchase for that customer's named Group. The customer declares its band; the supplier need not audit it. The Software's authorized seller receives payment, accepts the order, and sends confirmation directly to the customer, copying the supplier arranging the purchase.
+
+Arranging a purchase does not authorize the supplier to issue Software permissions or collect payment as the Licensor's agent. Paying the supplier alone does not buy the Software license. Before collecting money described as a Software license charge, the supplier must explain that distinction and identify the actual seller and intended customer coverage. The supplier may pay the seller in advance and recover that amount in its own sale, or direct the customer to pay through the official channel.
+
+Only payment received by the authorized seller, or that seller's express acceptance of an order allowing later payment, creates the section 4 permission. Once acquired, that permission does not depend on the supplier staying in business or forwarding payment later. It also does not depend on continuation of the application subscription. The supplier's own receipt or company license cannot replace the customer's permission from the Licensor.
+
+## 6. Hosted services and managed deployments
+
+The Group responsible for a deployment needs the applicable permission. An independent provider running its own service uses its own Group's permission. Its customers need no separate permission merely to access the service. This includes free plans, dedicated tenants, and services running workflows or programs written by customers. Execution supplied as part of that provider-controlled service is included even when the application computes locally in a browser. A copy deployed and controlled by the customer for independent operation requires its own applicable permission.
+
+If a supplier operates a customer's deployment on the customer's behalf, the customer's permission covers that operation and its authorized contractors. The supplier needs no second license solely for that work.
+
+Determine responsibility by who controls and commissions the deployment and is responsible for running it. The answer does not depend on who performs upgrades or calls the service SaaS. A customer-controlled installation in the customer's cloud account remains the customer's deployment when a supplier administers it. A dedicated tenant of a provider-controlled service remains the provider's deployment.
+
+Renting generic infrastructure does not, by itself, supply Software permission. A customer exporting the Software to operate independently needs its own applicable permission. Merely receiving independent outputs creates no Software fee. Section 7 does not require publication of private hosted modifications.
+
+## 7. Source and patent permissions
+
+### Source for distributed software
+
+When you distribute the Software, include its notices, identify material changes, and give recipients its corresponding source in the preferred form for making changes, along with the instructions needed to build that Software component.
+
+Software-covered files include modified Software source files and new source files containing Software code or adaptations of it. Renaming or splitting them does not remove that coverage.
+
+You do not need to disclose separate files containing only independent extensions, UI, or business logic. Keep private application logic in separate files. Putting it in a Software-covered source file makes that file subject to the source requirement. Building separate source files into one executable bundle does not, by itself, make the independent source files Software-covered. Credentials and application data are excluded.
+
+A free download supplied with the distribution is enough. Include or provide a source copy recipients can keep, rather than relying on a temporary link to the original project's source.
+
+You do not have to publish private modifications merely because they run internally or as a hosted service. You must not prohibit recipients from exercising the Software rights this license gives them.
+
+### Forks and contributions
+
+If you distribute modifications, you give recipients permission under this license to use all your additions and changes within Software-covered source files. This includes your necessarily infringed patent claims. You cannot require a separate permission fee or royalty for those additions and changes.
+
+The recipient's applicable permission from the upstream Licensor covers those modifications, including later modifications and successive forks, within its existing scope and duration. It does not cover upstream releases that were otherwise outside that permission. A fork does not replace the upstream Licensor or redirect its fees. You may charge for supplying copies or optional services. Independent material keeps its own terms.
+
+This grant does not require you to deliver future work or submit your changes upstream. It does not authorize the Licensor to relicense your modifications. Contributions submitted to the upstream project follow its separately disclosed contribution terms. Bread requires no particular contributor agreement, compensation arrangement, or governance model.
+
+### Patent permissions
+
+The Licensor gives a royalty-free license for patent claims it controls that would necessarily be infringed by exercising the permissions given here. This does not guarantee freedom from third-party patents.
+
+If a recipient starts a patent claim alleging that authorized Software use infringes its patent, that recipient's patent permission ends. Defensive counterclaims are excluded. This does not automatically cancel copyright permission or permissions held by unrelated recipients.
+
+## 8. Continuity, remedies, and other terms
+
+### Lasting permissions
+
+The Licensor cannot take away an acquired permission at will or narrow it by editing a website. Permission does not end merely because an update or supplier relationship ends. Properly issued rights come directly from the Licensor and survive an authorized seller's departure. Accepted commitments to cover future releases continue when the operator changes.
+
+### Unavailable licensing
+
+The Licensor may stop new sales by giving notice through its published licensing channel. Existing permissions and accepted Update Terms continue. The Licensor may appoint an authorized successor, but cannot reduce those rights by doing so.
+
+**Permanent permission when purchasing stays unavailable.** A Group automatically receives paid-up permission from the Licensor when both conditions are met:
+
+- It has been unable to make an ordinary company purchase through any designated channel for at least 180 consecutive days after making a qualifying request.
+- At least 30 days have passed since its further notice described below.
+
+This permission covers Software releases already published under this license when the request was sent. It allows the Group to use, modify, and distribute those releases for the duration of copyright, including after sales resume. Newcomers and existing customers can both qualify. All other conditions still apply, including source, notices, and downstream company requirements. It covers no future releases and does not excuse earlier payment obligations.
+
+**Making the request.** Identify your Group, its revenue band, the ordinary coverage requested, and your willingness and ability to pay the applicable published price and accept the terms. Send this to the published licensing contacts. Send a further notice stating that you intend to rely on this clause. A late further notice delays permission until both waiting periods are met; it does not restart the original request or change which releases qualify.
+
+If current contacts or prices disappear, use the last published ones. If no published contact is available, keep the qualifying request and dated evidence that no contact is available. That date counts as the date you sent the request. Do the same if you cannot send the further notice. If published prices cannot reasonably be recovered, keep dated evidence of that fact instead of accepting a price.
+
+Keep evidence of the request, further notice, and unsuccessful purchase attempt when claiming this permission. You do not need public registration or a new signature from the seller.
+
+**When purchasing becomes available again.** The waiting period is interrupted only when your Group is told, or otherwise knows, that a purchasing route has been restored and has a reasonable opportunity to complete the ordinary purchase. An acknowledgment, a momentary reopening without that opportunity, or sales to other buyers alone do not interrupt it. After an interruption, a new qualifying request starts a new waiting period.
+
+Refusing to pay, demanding different terms, legal restrictions specific to the applicant, and failing to use an available designated channel do not qualify as purchasing unavailability. Intentionally closing sales does count. A lack of development activity alone does not.
+
+**Continuing existing use after losing free eligibility.** If your Group makes a qualifying request within its section 3 transition period, it may continue the previously lawful operational uses and releases it was using before losing free business eligibility. This temporary permission ends:
+
+- 30 days after a restored purchasing route interrupts the waiting period; or
+- immediately if the request stops qualifying.
+
+Neither restoration itself nor an incomplete purchase during those 30 days makes the request stop qualifying. This temporary permission does not shorten the section 3 transition or any independently acquired permission. It covers no additional releases or new operational uses, and you owe no payment for this temporary use. Other Groups receive no interim operational permission under this clause.
+
+### Remedies and payments
+
+Before ending an affected permission for a material breach that can be corrected, give written details and at least 30 days to correct it. No unrelated permission or compliant customer's independently acquired permission ends automatically. Fraud, urgent relief, and mandatory law remain applicable.
+
+A payment dispute still in progress is not a final cancellation. A refund or payment reversal affects acquired coverage only to the extent it cancels the purchase that provided it, under applicable law and terms disclosed before purchase. Independent overlapping permissions remain intact. Refunding a separately purchased service does not cancel Software rights.
+
+If there is a concrete discrepancy, the seller may ask for proportionate clarification of the customer's revenue band under confidentiality. This gives no general right to inspect repositories, user data, or production systems.
+
+### Disclosures and liability
+
+Orders must state the total price, taxes, due dates, and renewal and cancellation terms. A standard fee does not promise support, indemnity, a service level, a particular update, or an execution result. Mandatory consumer, software, security, privacy, transfer, and other rights still apply. Downloading or evaluating the Software does not waive them.
+
+Except for express commitments and duties that cannot legally be excluded, the Software is supplied as is, without warranties or conditions of any kind. To the extent the law allows, the Licensor, authorized sellers, and contributors are not liable for damages from using the Software, being unable to use it, or defects in it. This includes direct, indirect, and consequential loss, regardless of the type of legal claim. This exclusion does not apply to breaches of express commitments in this license or separately accepted agreements.
+
+Under this license, indirect and consequential loss remain excluded to the extent the law allows, including for breaches of express commitments, unless greater liability was expressly accepted.
+
+For breaches of express software-license commitments owed under accepted company purchases, total direct damages are capped at the sum of the agreed license prices of the purchases whose commitments were breached, counting each purchase once. This is one combined cap across all claimants and claims against the Licensor, authorized sellers, and contributors, unless greater liability was expressly accepted. It does not govern separately purchased services.
+
+These limits do not cancel permissions, excuse promised performance, limit refunds or repayment otherwise owed, or prevent seeking an order to enforce rights. They do not exclude or limit liability for fraud, intentional wrongdoing, or anything the law does not allow to be excluded or limited.
+
+### Names and authority
+
+This license gives no general trademark rights or right to claim endorsement. You may still use names for descriptive attribution. This license sets the permissions; the dated price schedule accepted for a purchase sets its amounts. Guides explain those terms and cannot change them.
+
+Notices, orders, and separate service agreements may add identified rights. They cannot narrow the standard bargain in this license or take away existing rights. A changed instrument must be identified as modified, rather than offered as this unchanged Bread License version.

package/LICENSES/Apache-2.0.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.