@bestagentkits/render 0.1.1-next.1 → 0.3.0

package/README.md

@@ -1,37 +1,303 @@
 # @bestagentkits/render
 
-Declarative page compiler for AgentKit: a constrained JSON/YAML **Page Spec**
-in, a deterministic, self-contained, interactive **standalone HTML** out.
+A declarative page compiler for coding agents. An agent writes a short YAML or
+JSON **Page Spec**; `ak-render` compiles it into one deterministic,
+self-contained, interactive **HTML file**.
+
+[![The AK Render landing page, itself compiled from a Page Spec](./docs/assets/landing.webp)](https://render.agentkit.best)
+
+**[render.agentkit.best](https://render.agentkit.best)** · [Gallery](https://render.agentkit.best/gallery/) · [Agent guide](./docs/agent-guide.md) · [npm](https://www.npmjs.com/package/@bestagentkits/render)
 
 Agents describe meaning and composition. The compiler owns HTML, CSS,
-interaction, accessibility, responsive layout, theming, asset bundling, security
-policy, and byte-for-byte determinism.
+interaction, accessibility, responsive layout, theming, fonts, security policy
+and byte-for-byte determinism. The agent spends tokens on the content instead
+of on markup, and the result looks designed every time.
+
+- **Offline by default.** The file opens from disk (`file://`) and makes zero
+  network requests. Fonts are embedded; nothing loads from a CDN.
+- **Deterministic.** The same spec and compiler version produce the same bytes.
+- **No escape hatch.** A spec cannot carry raw HTML, CSS or JavaScript, so a
+  page cannot drift off the design system or smuggle in a script.
+- **Local is canonical.** No account, no server, no API key.
+
+## Quick start
+
+Requires Node.js >= 20.11.
+
+1. Write a spec, `plan.yaml`:
+
+   ```yaml
+   version: 1
+   meta:
+     title: Migration plan
+     description: How we move the API to the new gateway.
+   theme:
+     preset: editorial
+   blocks:
+     - type: hero
+       eyebrow: Plan
+       title: Migration plan
+       description: Move the public API to the new gateway without downtime.
+     - type: section
+       title: Steps
+       blocks:
+         - type: steps
+           items:
+             - title: Mirror traffic
+               text: Send a copy of production requests to the new gateway.
+             - title: Switch reads
+               text: Route read endpoints once error rates match.
+     - type: callout
+       tone: info
+       title: Rollback
+       text: Point DNS back to the old gateway; no data migrates.
+   ```
+
+2. Validate it, then compile it:
+
+   ```bash
+   npx -y @bestagentkits/render validate plan.yaml
+   npx -y @bestagentkits/render plan.yaml --out plan.html
+   ```
+
+3. Open `plan.html` in any browser. It is one file you can attach, email or
+   commit.
+
+## Usage guide
+
+### Find the blocks you need
+
+There are 83 block types in eight categories (layout, content, data,
+interaction, media, showcase, engineering, product), from primitives (`section`,
+`grid`, `split`, `text`) to semantic blocks that carry the design for you
+(`hero`, `steps`, `timeline`, `kpi`, `data-table`, `chart`, `kanban`,
+`pricing`, `cta`). Find the ones you need, then read only their contracts:
+
+```bash
+ak-render catalog                        # every block by category, and every action
+ak-render catalog --category data        # one category
+ak-render search-catalog sortable table  # rank block types by intent words
+ak-render describe kpi chart --compact   # one line per prop, for several types
+ak-render describe timeline --json       # one full contract: defaults, bounds, a11y notes
+```
+
+Containers (`section`, `grid`, `split`, `stack` and the page layouts
+`sidebar-layout`, `main-aside`, `rail-layout`) take their children under
+`blocks:`. Tabs, accordion sections, carousel slides and bento tiles hold
+blocks too, under `items[i].blocks`.
+
+Text is plain text, with one exception: in prose props such as `text`, a step's
+or list item's `text`, a `description` or a `caption`, a pair of backticks
+renders as inline code, so `` `ak-render catalog` `` reads as a command. Nothing
+else is parsed as markup, an unpaired backtick stays literal, and titles, code
+and terminal lines are never changed. `describe` marks each prop that does this.
+
+### Start from a page recipe
+
+A recipe is a complete, valid starter spec for a common page: a dashboard, a
+benchmark report, an architecture review, an incident report, a product
+showcase, a case study, a release recap, an implementation plan, a research
+report or a decision memo. Replace its placeholder text and data, then validate.
+
+```bash
+ak-render recipes                          # names, summaries and the blocks each uses
+ak-render recipe dashboard > page.yaml     # the starter spec as YAML
+```
+
+### Datasets and state
+
+Declare a table once under `datasets` and bind charts, tables and widgets to it
+with `dataRef`, reshaped by a bounded `transform`. Native controls write page
+`state`, `visibleWhen` switches views from it, and `filter-bar` filters a table,
+board or log. All of it is data, and every page still reads completely with
+scripts off. See [docs/data-and-state.md](./docs/data-and-state.md).
+
+### Validate and fix
 
 ```bash
-npx @bestagentkits/render page.yaml --out page.html
+ak-render validate plan.yaml --json
 ```
 
-The emitted file opens directly from disk (`file://`) and makes zero network
-requests by default. The local compiler is canonical: no account, no network, no
-server.
+The result is `{ ok, diagnostics[] }`. Each diagnostic has a stable `code` and
+the JSON `path` to fix, such as `$.blocks[1].blocks[0].items[2].title`. Exit
+code `1` means "fix and retry"; `2` means the input could not be read or the
+output could not be written.
 
-> **Status:** pre-1.0, in active construction. This repository is being built in
-> milestones. The package skeleton, ADR, CI, and fixture corpus exist; the
-> schema, compiler, themes, runtime, catalog, and cloud service land in the
-> milestones described in [docs/adr/0001-page-spec-compiler-boundary.md](./docs/adr/0001-page-spec-compiler-boundary.md)
-> and the [changelog](./CHANGELOG.md). Nothing below is advertised as available
-> before it exists.
+### Compile
 
-## Why
+```bash
+ak-render plan.yaml --out plan.html            # compile is the default command
+ak-render plan.yaml --out plan.html --json     # print bytes, hash, features, warnings
+ak-render - --out plan.html < plan.yaml        # read the spec from stdin
+ak-render plan.yaml --theme blueprint          # override the spec's theme
+```
 
-AgentKit's HTML-producing skills each carried the presentation layer in model
-context: layout, CSS, JavaScript, charts, responsive rules, theming, and
-verification. That costs tokens, adds latency, invites retries after
-HTML/CSS/JS mistakes, and lets skills drift against each other.
+### Themes
+
+Ten built-in presets, each with a light and a dark scheme and an embedded
+display face: `blueprint`, `data-console`, `editorial`, `executive-report`,
+`paper-ink`, `product-studio`, `research-notebook`, `swiss-clean`,
+`terminal-mono` and `warm-signal`. Presets also choose component recipes, such
+as ledger tables or outlined cards, from closed lists. Pick one under
+`theme.preset`, or extend one with validated tokens:
+
+```yaml
+theme:
+  preset: team-theme
+  extends: editorial
+  tokens:
+    color-accent: "#b8860b"
+    motion-policy: none     # a still page, as under reduced motion
+```
+
+`ak-render themes` lists the presets it can see, including project and user
+presets. See [docs/themes.md](./docs/themes.md).
+
+### Interaction
+
+Tabs, accordions, carousels, native form controls, filter bars, sortable
+tables, dialogs, copy buttons and the theme toggle come from a small trusted
+runtime. A spec wires them with a closed
+set of declarative actions (`ak-render catalog` lists them); there is no
+JavaScript field. Every page reads completely with scripts off, with motion
+reduced, in print and in a screenshot.
+
+### Images, video and the network
+
+Local paths (`assets/shot.png`) always work. A remote URL renders as a labelled
+fallback with a link unless the spec opts in. A remote video `poster` is the
+exception: it has no fallback, so `validate` rejects it at its own path until
+the page allows remote `images`:
+
+```yaml
+policy:
+  network:
+    allow: [images, media]
+```
 
-`ak:diagram` already proved the alternative for diagrams: typed IR, deterministic
-compiler, trusted fragment boundary. AK Render applies the same pattern to whole
-pages.
+The page's Content Security Policy is derived from that policy. See
+[docs/media-policy.md](./docs/media-policy.md).
+
+## Use it from an agent
+
+Agents follow one loop: find blocks with `catalog` or `search-catalog`, start
+from a `recipe` when one fits, `describe --compact` the blocks they use,
+`validate` and fix diagnostics by JSON path, then compile. The
+[agent guide](./docs/agent-guide.md) has the details and [llms.txt](./llms.txt)
+is the LLM-facing index.
+
+### Install the agent skill
+
+The `ak-render` skill ([skills/ak-render/SKILL.md](./skills/ak-render/SKILL.md))
+teaches an agent that loop.
+
+**Any agent**, with the [skills CLI](https://github.com/vercel-labs/skills):
+
+```bash
+npx skills add bestagentkits/ak-render
+```
+
+**Claude Code**, as a plugin that also registers the MCP server:
+
+```bash
+claude plugin marketplace add bestagentkits/ak-render
+claude plugin install ak-render@ak-render
+```
+
+**Codex and ChatGPT**, as a plugin:
+
+```bash
+codex plugin marketplace add bestagentkits/ak-render
+codex plugin add ak-render@ak-render
+```
+
+### Three ways to run it
+
+All three serve the same tools with the same contracts, backed by the same
+compiler, so a spec renders to the same bytes whichever an agent picks.
+
+| Mode | Needs | `render` returns | Network |
+| --- | --- | --- | --- |
+| Local CLI | Node 20.11+ | writes `--out`, prints a summary with `--json` | none |
+| Local MCP (stdio) | Node 20.11+ | writes `out`, returns a summary | none |
+| Remote MCP (Streamable HTTP) | an AgentKit token | stores the page, returns a summary and `artifactUrl` | yes |
+
+Local is canonical and needs no account. The remote server exists for agents
+that cannot install Node or need a URL to hand someone.
+
+**Local CLI.** The loop above, with `ak-render` on the path or through `npx`.
+
+**Local MCP over stdio.** `ak-render mcp` serves `catalog`, `search-catalog`,
+`describe`, `recipes`, `recipe`, `validate`, `render` and `themes` as MCP
+tools. `render` writes the HTML to disk
+and returns only a summary, so the page never enters the agent's context.
+
+```json
+{
+  "mcpServers": {
+    "ak-render": { "command": "npx", "args": ["-y", "@bestagentkits/render", "mcp"] }
+  }
+}
+```
+
+**Remote MCP over Streamable HTTP.** `https://render.agentkit.best/mcp` serves
+`catalog`, `search-catalog`, `describe`, `recipes`, `recipe`, `validate`,
+`render` and `themes` with the same contracts. A remote server cannot write into your filesystem, so
+`render` takes no `out`: it stores the page and returns the same summary plus an
+`artifactUrl` that lives for one hour, or a share link that lives for 30 days
+with `share: true`. The HTML still never enters the agent's context.
+`catalog`, `search-catalog`, `describe`, `recipes`, `recipe` and `themes`
+answer without a token; `validate` and `render` need an AgentKit bearer token.
+
+```json
+{
+  "mcpServers": {
+    "ak-render": {
+      "type": "http",
+      "url": "https://render.agentkit.best/mcp",
+      "headers": { "Authorization": "Bearer ${AGENTKIT_TOKEN}" }
+    }
+  }
+}
+```
+
+Details, limits and the REST routes are in
+[apps/cloud/README.md](./apps/cloud/README.md).
+
+## Token cost
+
+The compiled page goes to disk, never through the model. What the agent pays
+is guidance it reads, the spec it writes, and a one-line summary it reads back.
+
+| Part of a page task | Hand-written HTML | AK Render |
+| --- | ---: | ---: |
+| Presentation guidance read | 25.0k (baseline mean) | 10.6k (shared contract, skill, catalog, `describe --json`) |
+| Written by the agent | 13.9k (median legacy page) | 7.2k (projected spec) |
+| Returned into context | the written page is already there | 0.1k (render summary) |
+| **Total, estimated** | **38.9k** | **17.9k (−54%)** |
+
+With the compact workflow the agent guide recommends,
+`describe <types...> --compact`, the guidance read is 5.7k and the total
+13.1k (−66%). The spec written and the summary returned are the same.
+
+- **Benchmarked:** presentation context drops 64–68%, from 23.7k–26.6k tokens
+  of AgentKit's legacy HTML guidance to 7.9k–8.5k on the `ak-render` skill
+  route: the shared AgentKit contract, the skill, `catalog`, and the
+  `describe --json` output of the blocks a task uses
+  ([render benchmark](./docs/artifacts/benchmark-render.md)). The `ak:preview`
+  diff task (68%) follows AgentKit's reference-loading table directly; the
+  explain, brainstorm and plan rows use the `ak-preview` reference set as a
+  proxy for their hand-written HTML route.
+- **Measured on 12 HTML pages agents wrote in real projects:** a median of 26%
+  of each page is visible text; the rest is markup, CSS and script. The
+  projected median output saving is 52%. A page that is mostly prose saves
+  little or nothing: one of the twelve grew by 35%.
+- **Not measured yet:** live model token counts, repair loops, wall time and
+  output quality.
+
+Characters are measured; tokens are estimated at 4 characters per token. Method
+and per-page data: [agent token cost](./docs/artifacts/agent-token-cost.md),
+produced by `benchmarks/agent-token-cost.mjs`.
 
 ## Design in one screen
 
@@ -55,29 +321,26 @@ Six decisions define the boundary, argued in
    model-friendly spec normalizes into a flat node graph with stable IDs for
    rendering, future diff/patch/editor tooling, and MCP surfaces.
 2. **Catalog and registry are separate.** `catalog()` is compact and cheap;
-   `describe(type)` carries the full contract. Discovery stays out of the token
+   `describe(type)` carries the full contract, and `--compact` one line per
+   prop. Discovery stays out of the token
    budget until a block is actually selected.
 3. **The interaction runtime is trusted and declarative.** A closed action
    vocabulary, one small event-delegation script, native HTML controls first,
    and only the feature modules a page uses.
 4. **Themes are typed data, never CSS.** Built-in presets plus user presets that
    `extends` them. No CSS escape hatch, no CDN fonts.
-5. **Local is canonical; cloud is opt-in.** The hosted renderer reuses the same
-   compiler and is never the source of truth.
-6. **Optional capabilities arrive as adapters.** Diagrams delegate to the
-   existing `ak:diagram` compiler where installed; the public package never
-   copies paid or Engineer-only implementation.
+5. **Local is canonical; cloud is opt-in.** The hosted renderer and the remote
+   MCP server reuse the same compiler and tool contracts and are never the
+   source of truth.
+6. **Optional capabilities arrive as adapters.** Diagrams can delegate to an
+   installed diagram compiler; without one, a structured fallback renders.
 
-## Install
+## Install as a dependency
 
 ```bash
 pnpm add @bestagentkits/render
-# or run without installing
-npx @bestagentkits/render --help
 ```
 
-Requires Node.js >= 20.11.
-
 ## Library API
 
 ```ts
@@ -98,32 +361,41 @@ import {
 | `render(spec, options)` | Compile a spec to a standalone HTML artifact | Available |
 | `validate(spec)` | Report spec diagnostics without rendering | Available |
 | `normalize(spec)` | Produce the flat internal IR | Available |
-| `catalog()` | Compact list of available blocks and actions | Available |
+| `catalog(options)` | Compact list of blocks and actions, optionally one `category` | Available |
+| `searchCatalog(query)` | Block types ranked by intent words | Available |
 | `describe(type)` | Full machine-readable contract for one entry | Available |
+| `describeMany(types, options)` | Up to 12 contracts, full or `compact` | Available |
+| `recipes()`, `recipe(name)` | Page recipe list, and one recipe's starter spec | Available |
 | `loadTheme(input)` | Validate and resolve a theme preset | Available |
 | `buildThemeCatalog(options)` | Discover built-in, user, project, and explicit presets | Available |
 
-## CLI
+## CLI reference
 
 ```bash
 ak-render page.yaml --out page.html
+ak-render - --out page.html < page.yaml   # read the spec from stdin
 ak-render validate page.json
-ak-render catalog
-ak-render describe carousel
+ak-render catalog [--category <c>]
+ak-render search-catalog <terms...>
+ak-render describe <type...> [--compact]
+ak-render recipes
+ak-render recipe <name>                   # YAML by default
 ak-render themes
+ak-render mcp                             # MCP server over stdio
 
-ak-render --help
+ak-render <command> --help
 ak-render --version
 ```
 
-The CLI only advertises commands it can actually run; the compiler subcommands
-are registered by the milestones that implement them.
+Every command accepts `--json` and never prompts.
 
 ## Fixtures and snapshots
 
 `fixtures/pages/` holds the representative corpus the compiler is built
-against: plan, explain, recap, diff, dashboard, media, interactive, and theme
-showcase pages. `fixtures/snapshots/` holds one committed artifact per built-in
+against: plan, explain, recap, diff, dashboard, media, interactive and theme
+showcase pages, one page per widget family, layout, data and theme feature,
+and six composition pages (a dashboard, a benchmark report, a research report,
+a product case study, a data explorer and an incident report). `fixtures/snapshots/` holds one committed artifact per built-in
 preset. See [fixtures/README.md](./fixtures/README.md) and
 [docs/themes.md](./docs/themes.md). Fixtures are the specification: a new
 capability is not done until a fixture exercises it.
@@ -139,16 +411,24 @@ capability is not done until a fixture exercises it.
 | `benchmarks/` | Reproducible measurement harnesses |
 | `docs/adr/` | Architecture decision records |
 | `docs/artifacts/` | Captured measurements and evidence |
-| `apps/cloud/` | Opt-in Cloudflare renderer (cloud milestone) |
+| `skills/`, `.claude-plugin/`, `.agents/plugins/`, `plugin.json`, `mcp.json` | Agent skill and plugin manifests |
+| `assets/` | Embedded font licences and the plugin icon (`icon.svg` is the source of `logo.png` and `composer-icon.png`) |
+| `site/` | Landing page spec, build script output and Cloudflare config |
+| `src/mcp/` | MCP protocol, shared tool contracts, stdio and Streamable HTTP transports |
+| `apps/cloud/` | Opt-in Cloudflare renderer: REST routes and the remote MCP endpoint |
 
 ## Development
 
 ```bash
 pnpm install
-pnpm verify          # lint + typecheck + unit tests + build
+pnpm verify          # lint, typecheck, font and recipe checks, unit tests, build
 pnpm test:browser    # Playwright, after: pnpm exec playwright install chromium
 pnpm test:package    # pack, install into a temp project, exercise API and bin
 pnpm bench:baseline  # re-run the legacy presentation-context measurement
+pnpm bench:spec      # spec compression for the composition fixtures
+pnpm build && pnpm bench:render --agentkit ../agentkit --repeat 9  # committed render artifact
+pnpm site:build      # compile the landing page and gallery into site/dist
+pnpm site:deploy     # build, then deploy site/dist with wrangler
 ```
 
 See [CONTRIBUTING.md](./CONTRIBUTING.md) for the determinism, trust, and testing

package/assets/fonts/bricolage-grotesque/OFL.txt

@@ -0,0 +1,93 @@
+Copyright 2022 The Bricolage Grotesque Project Authors (https://github.com/ateliertriay/bricolage)
+
+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:
+http://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+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/assets/fonts/fraunces/OFL.txt

@@ -0,0 +1,93 @@
+Copyright 2020 The Fraunces Project Authors (github.com/undercasetype/Fraunces) Fraunces-Italic[SOFT,WONK,opsz,wght].ttf: Copyright 2020 The Fraunces Project Authors (github.com/undercasetype/Fraunces)
+
+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:
+http://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+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.