invos 1.0.0 → 2.0.2

package/kit/.agents/skills/canvas-design/canvas-fonts/YoungSerif-OFL.txt

@@ -0,0 +1,93 @@
+Copyright 2023 The Young Serif Project Authors (https://github.com/noirblancrouge/YoungSerif)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+https://openfontlicense.org
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.

package/kit/.agents/skills/carrossel/SKILL.md

@@ -0,0 +1,272 @@
+---
+name: carrossel
+description: >
+  Cria carrosséis e posts visuais pra Instagram, TikTok, LinkedIn com a identidade visual da marca.
+  Gera HTML estilizado + renderiza em PNG 1080x1350 via Playwright, com legenda pronta no final.
+  Suporta carrossel texto puro, carrossel com foto IA (gerada via OpenAI) e post único.
+  Use quando o usuário pedir "carrossel", "post", "conteúdo pro instagram", "criar imagem",
+  "gerar foto", "post educativo", ou /carrossel.
+---
+
+# /carrossel — Carrossel e posts visuais
+
+Skill central de criação de conteúdo visual. Pega um tema → entrega HTMLs estilizados + PNGs prontos pra postar + legenda no padrão da marca.
+
+## Dependências
+
+- **Identidade visual:** `marca/design-guide.md` — LER ANTES de criar qualquer visual
+- **Contexto do negócio:** `_memoria/empresa.md`
+- **Tom de voz:** `_memoria/preferencias.md`
+- **Playwright:** pra renderizar HTML em PNG (`npx playwright screenshot` ou via `render.js`)
+- **OpenAI API (opcional):** pra gerar fotos realistas — só se o cliente tiver chave configurada
+- **Outputs vão em:** `marketing/conteudo/<tipo>-<tema>-<YYYY-MM-DD>/`
+
+---
+
+## Tipos de conteúdo
+
+Ao receber um pedido, identificar qual tipo se encaixa:
+
+### 1. CARROSSEL TEXTO PURO
+- **Quando usar:** posts educacionais, dicas, listas, explicações
+- **Formato:** 1080x1350 (4:5) — sempre
+- **Estilo:** tipografia clean, cores da marca alternadas, sem fotos
+
+### 2. CARROSSEL COM FOTO
+- **Quando usar:** apresentação visual, conteúdo aspiracional, capa com personagem
+- **Formato:** 1080x1350 (4:5)
+- **Estilo:** foto como capa com gradient overlay + slides internos no padrão alternado
+- **Foto:** pode ser IA (gerada por OpenAI) ou real (passada pelo usuário)
+
+### 3. POST ÚNICO
+- **Quando usar:** frase de impacto, dado/estatística, depoimento, bastidores
+- **Formato:** 1080x1350
+- **Estilo:** varia conforme o conteúdo (citação, número grande, foto com overlay)
+
+Se o tipo não estiver claro, perguntar:
+> "Que tipo de conteúdo? (1) carrossel texto, (2) carrossel com foto, (3) post único"
+
+---
+
+## Estilo visual base
+
+O INVOS tem um estilo próprio — editorial, calmo, premium. Sem clip-art, sem emoji decorativo, sem gradiente arco-íris, sem template genérico de IA. `marca/design-guide.md` sobrescreve esses padrões; quando o design-guide for vago ou estiver em branco, usar o que tá aqui (não parar pra pedir `/instalar` — o `/carrossel` funciona com defaults bons).
+
+### Tipografia padrão
+
+- **Fonte:** Inter (Google Fonts), pesos 400/500/600/700/800/900
+- **Título de capa:** 90-100px, weight 900, line-height 0.98, letter-spacing **-0.04em**
+- **H2 (slides internos):** 60-72px, weight 800, line-height 1.04, letter-spacing **-0.035em**
+- **Corpo:** 20-24px, weight 500, line-height 1.5
+- **Eyebrow/kicker:** 13-16px, weight 700-800, **UPPERCASE**, letter-spacing **0.22-0.32em**, cor de destaque
+- **Page counter (canto sup. dir.):** 14-16px, weight 500-600, letter-spacing 0.18em, cor muted
+- **Meta/handle (@):** 15-18px, weight 600
+
+Regra do tipo: títulos grandes com kerning **apertado** (-0.035em), eyebrows pequenos com kerning **aberto** (0.22em+). Esse contraste é o coração do estilo.
+
+### Cores padrão (quando design-guide for vago)
+
+Paleta sóbria: fundo dark + off-white + **UMA** cor de destaque. Nunca quatro cores brigando.
+
+- Fundo escuro: `#0E1116` ou `#1A1A1A`
+- Fundo claro alternativo: `#F5ECD7` (cream) ou `#FAFAF7`
+- Texto sobre escuro: `#FAFAF7`
+- Texto sobre claro: `#1A1A1A` (h2) e `#444` (corpo)
+- Destaque: cor da marca (uma só)
+
+### Elementos visuais recorrentes
+
+- **Régua fina** (3-4px de altura, 60-80px de largura, cor de destaque) entre kicker e h2 ou como divisor
+- **Logo top-left + page counter top-right** em todos os slides
+- **Border-top 1px** `rgba(255,255,255,0.12)` separando rodapé do conteúdo (em slides escuros)
+- **Stamps circulares** (200x200, border 3px translúcida, rotate -10deg) pra selos/datas/dados
+- **Tags/pills** uppercase, padding generoso, kerning 0.2em, pra rotular categoria do slide
+- Padding base: 70-100px nas laterais
+
+### Layouts nomeados
+
+Vocabulário de layout — cada slide tem um nome. Variar entre eles pra criar ritmo:
+
+- **CAPA** — eyebrow + título grande + subtítulo + @handle. Fundo: foto com gradient overlay (`rgba(12,10,9,0.55)` → `rgba(12,10,9,0.85)`) OU sólido (escuro/claro/destaque)
+- **SOLO** — split horizontal: foto à esquerda 50% + texto à direita 50% (kicker + h2 + régua + parágrafo)
+- **DUO** — texto em cima (kicker + h2 + régua + p) + 2 fotos lado a lado embaixo (ou 1 foto larga)
+- **NÚMERO** — numeral gigante (200-320px, weight 800, cor de destaque) como elemento gráfico + h2 + parágrafo de apoio
+- **CITAÇÃO** — aspas grandes em watermark + frase em h2 + atribuição
+- **CTA FINAL** — fundo na cor de destaque, logo centralizado, headline curta, botão/CTA, telefone/@handle
+
+**Ritmo de slide a slide:** alternar fundo escuro ↔ claro ↔ destaque. Nunca dois slides seguidos com o mesmo fundo.
+
+---
+
+## Padrão do carrossel
+
+**Arco (5 a 10 slides) — não pular etapas:**
+1. **CAPA (hook)** — para o scroll (ver checklist de copy abaixo)
+2. **Desenvolvimento** — 2–3 layouts entre `SOLO` / `DUO` / `NÚMERO` / `CITAÇÃO`; uma ideia por slide
+3. **Reflexão** — penúltimo slide de conteúdo: o que isso muda na prática do leitor (não mais um dado solto)
+4. **CTA FINAL** — ação específica ligada ao conteúdo (não “nos siga”)
+
+Antes de criar HTML: ler `marca/design-guide.md`. Se estiver em branco, usar o "Estilo visual base" acima como default.
+
+### Checklist de copy (antes do visual)
+
+Aplicar **sempre** no texto. Se falhar, reescrever — não “melhorar no design”.
+
+| Gate | Passa se… | Falha se… |
+|------|-----------|-----------|
+| **Scroll-stop** | Capa = tensão, dado concreto, contraste ou pergunta que o feed não ignora | “Hoje vamos falar…”, “X dicas de…”, meta-comentário, só logo/nome |
+| **Densidade** | 1 ideia por slide; ≤ ~5 linhas visíveis; sem parágrafo de LinkedIn | Bullet de deck, 2+ ideias, bloco denso |
+| **Arco** | Hook → desenvolve → reflexão → CTA | Só lista de fatos → CTA |
+| **CTA** | Ação específica e ligada ao tema | “Nos siga”, “link na bio”, “salve” sem motivo |
+| **Dados** | Número com fonte **ou** claramente opinião/experiência | Estatística inventada / “todo mundo sabe” |
+
+Capa: título **máx ~8 palavras**. Oferecer **3 opções** de capa no checkpoint de texto.
+
+### Sequência de capas no feed (planejamento de grade)
+
+Antes de definir a capa, considerar a **última capa publicada** pra alternar:
+- claro → próxima é foto/escuro
+- foto/escuro → próxima é cor da marca
+- cor da marca → próxima é claro
+- nunca duas capas iguais em sequência
+
+Se o usuário não souber qual foi a última, perguntar (ou default: CAPA escura / destaque da marca).
+
+### Linguagem (regra crítica)
+
+Seguir `_memoria/preferencias.md`. Frases naturais, sem jargão de marketing, sem corporativês. O público real raramente fala "ticket médio", "performance", "B2B". Falar como ele fala.
+
+Frase genérica que serve pra **qualquer** marca/tema → reescrever.
+
+### Legenda — sempre gerar junto
+
+Ao terminar de renderizar os PNGs, gerar **automaticamente** a legenda do post e salvar em `legenda.md` na mesma pasta. **Não esperar o usuário pedir.** Estrutura padrão:
+
+1. Hook (pergunta ou afirmação)
+2. Contexto (1-2 frases sobre o conteúdo)
+3. CTA pra arrastar ("Arraste pro lado e confere")
+4. Bloco de oferta (diferenciais da empresa, contato)
+5. Hashtags (10-15 — público + nicho + local se aplicável)
+
+---
+
+## Workflow
+
+### Passo 1 — Entender e planejar
+
+1. Ler `_memoria/preferencias.md` e `_memoria/empresa.md`
+2. Ler `marca/design-guide.md` pra cores, fontes e logo
+3. Identificar o tipo de conteúdo (1, 2 ou 3)
+4. Definir o tema e o ângulo
+
+### Passo 2 — Texto
+
+Escrever o conteúdo seguindo tom + **checklist de copy**.
+
+**Pra carrossel (5-10 slides):**
+- Capa: 3 opções que passam scroll-stop
+- Internos: 1 insight/slide, ≤ ~5 linhas, sem bullet de deck
+- Penúltimo: reflexão prática (“o que isso muda pra você”)
+- Final: CTA específico + logo
+
+**Pra post único:**
+- Frase principal = scroll-stop
+- Apoio curto se precisar
+- CTA sutil e específico
+
+**CHECKPOINT:** Mostrar o texto completo **e** marcar mentalmente os 5 gates (hook, densidade, arco, CTA, dados). Esperar aprovação antes do visual.
+
+### Passo 3 — Gerar fotos (se tipo 2)
+
+Só se o usuário pediu carrossel com foto IA.
+
+1. Montar prompt em inglês (a API funciona melhor em inglês)
+2. Padrão genérico de prompt:
+
+```
+Professional [TIPO] photography of [ASSUNTO],
+[DETALHES], [AMBIENTE/CONTEXTO],
+[ESTILO DE LUZ] lighting, shallow depth of field,
+shot from [ÂNGULO], [ESTILO/ESTÉTICA],
+editorial quality
+```
+
+3. Gerar via script (se `scripts/gerar-imagem.js` existir):
+```bash
+node --env-file=.env scripts/gerar-imagem.js "PROMPT" "marketing/conteudo/<pasta>/foto-<nome>.png"
+```
+
+Se não tiver o script ainda, instruir o usuário a configurar `OPENAI_API_KEY` no `.env` e criar o script (ou usar outra ferramenta de geração de imagem).
+
+4. Mostrar a foto pro usuário antes de continuar.
+
+**CHECKPOINT:** Foto aprovada → seguir. Se não, ajustar prompt e regenerar.
+
+### Passo 4 — Criar visuais (HTML + PNG)
+
+1. Criar **um único `carrossel.html`** com TODOS os slides como `<div class="slide">` dentro do mesmo arquivo. Inline CSS, Google Fonts como única dependência externa. Aplicar:
+   - Cores e tipografia de `marca/design-guide.md`
+   - Mínimo 2 layouts diferentes (não repetir o mesmo em todos os slides)
+   - Logo top-left + slide-counter top-right em todos os slides
+   - Slide final: logo + CTA, fundo na cor principal
+
+   **Pra incluir foto IA no HTML:**
+   ```html
+   <div class="slide" style="
+     background-image: linear-gradient(rgba(0,0,0,0.55), rgba(0,0,0,0.7)), url('foto-xxx.png');
+     background-size: cover;
+     background-position: center;
+   ">
+     <div class="content">
+       <h2>Texto sobre a foto</h2>
+     </div>
+   </div>
+   ```
+
+2. Criar `render.js` na mesma pasta — script Node com Playwright que abre o HTML e tira screenshot de cada `.slide` em 1080x1350. Pode reutilizar `node_modules` de uma pasta anterior (não precisa rodar `npm install` toda vez):
+```bash
+NODE_PATH="<pasta-com-node_modules>/node_modules" node render.js
+```
+
+3. Mostrar slide 1, 2 e o CTA final renderizados. Se aprovado, mostrar os intermediários.
+
+### Passo 5 — Salvar e organizar
+
+```
+marketing/conteudo/<tipo>-<tema>-<YYYY-MM-DD>/
+  texto.md              ← texto aprovado + legenda
+  foto-<nome>.png       ← fotos geradas por IA (se houver)
+  carrossel.html
+  render.js
+  instagram/
+    slide-01.png → slide-NN.png
+  tiktok/ (se pedido — formato 9:16)
+    slide-01.png → ...
+  legenda.md            ← legenda Insta+FB
+  legenda-linkedin.md   ← (se pedido, mais formal)
+```
+
+### Passo 6 — Conexão com blog (opcional)
+
+Depois de criar o conteúdo visual, perguntar:
+
+> "Esse conteúdo dá pra virar artigo no blog também. Quer que eu crie a versão blog pra SEO?"
+
+Se sim, chamar `/publicar-tema` com o mesmo tema.
+
+---
+
+## Regras
+
+- Sempre ler `marca/design-guide.md` antes de criar qualquer visual
+- Carrossel: 1080x1350 (4:5 retrato) — sempre. TikTok/Reels: 1080x1920 (9:16) — só quando pedido explicitamente
+- Linguagem segue `_memoria/preferencias.md` estritamente
+- Copy: checklist (scroll-stop, densidade, arco com reflexão, CTA específico, dados honestos) — design não salva texto fraco
+- Sempre considerar a sequência de capa no feed antes de definir capa nova
+- Sempre gerar legenda automaticamente ao final, salvando em `legenda.md`
+- Fotos IA: sempre pedir aprovação antes de usar no carrossel
+- Fotos IA: prompts em inglês
+- Fotos IA: nunca gerar fotos de pessoas/rostos identificáveis
+- HTMLs: um único arquivo `carrossel.html` com todos os slides + `render.js` na mesma pasta. Inline CSS
+- Render: reutilizar `node_modules` quando possível (não rodar `npm install` em cada pasta)
+- Não repetir layout entre slides — usar variação visual

package/kit/.agents/skills/email-profissional/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: email-profissional
+description: >
+  Rascunha um email profissional a partir de um contexto livre.
+  Calibra o tom ao destinatário e ao objetivo do email.
+  Use quando o usuário disser "escreve um email pra", "preciso mandar um email sobre",
+  "como eu respondo isso", "faz um email pra [cliente/pessoa]".
+---
+
+# /email-profissional — Rascunho de Email
+
+## Dependências
+
+- **Contexto do negócio:** `_memoria/empresa.md`
+- **Tom de voz:** `_memoria/preferencias.md`
+
+---
+
+## Workflow
+
+### Passo 1 — Coletar o contexto
+
+Se o usuário não forneceu as informações necessárias, perguntar:
+1. "Pra quem é o email? (nome, cargo, relação com você)"
+2. "Qual é o objetivo? (cobrar, propor, responder, agradecer, seguir up...)"
+3. "Tem algo específico que precisa constar ou que precisa evitar dizer?"
+
+Se o usuário deu o contexto de forma livre (mesmo que bagunçado), extrai o que der e prossegue.
+
+### Passo 2 — Escrever o email
+
+**Considerar:**
+- Tom proporcional à relação (cliente novo = mais cuidado, parceiro antigo = mais direto)
+- Objetivo claro na abertura (não enterrar o pedido no final)
+- Uma ação pedida por vez
+- Encerramento sem redundância ("Qualquer dúvida, fico à disposição" é padrão — só usar se fizer sentido)
+
+**Estrutura:**
+```
+Assunto: [linha de assunto direta, sem clicbait]
+
+[Nome],
+
+[Parágrafo 1 — contexto ou referência ao último contato]
+
+[Parágrafo 2 — o ponto principal ou o pedido]
+
+[Parágrafo 3 — próximo passo, se houver]
+
+[Assinatura]
+[Nome do usuário, de _memoria/empresa.md]
+```
+
+### Passo 3 — Apresentar opções de tom (quando fizer sentido)
+
+Se o assunto for delicado (cobrança, feedback negativo, recusa), oferecer 2 versões:
+- Versão A: mais direta
+- Versão B: mais suave
+
+Deixar o usuário escolher.
+
+---
+
+## Regras
+
+- Tom segue `_memoria/preferencias.md`
+- Nunca usar linguagem corporativa genérica sem necessidade
+- Assunto do email deve ser específico e descritivo, não vago ("Seguimento", "Proposta")
+- Se for um email de cobrança, ser direto mas sem agressividade
+- Se for resposta a algo, citar o contexto na primeira linha

package/kit/.agents/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 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