kanso 0.1.0__tar.gz

kanso-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,49 @@
+name: ci
+
+# Every milestone is gated on this workflow, so it lands in the first commit.
+# It runs the offline suite only: no credential is available to it and none is added,
+# which is what proves the core works with every vendor credential unset.
+
+on:
+  push:
+    branches: ["main", "feat/**", "fix/**", "docs/**", "chore/**"]
+  pull_request:
+    branches: ["main"]
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: ${{ matrix.os }} · py${{ matrix.python }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        # macOS 26+ arm64 and Linux x86_64 are the supported hosts; the pinned engine
+        # publishes no wheel for an older macOS.
+        os: [macos-26, ubuntu-24.04]
+        python: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Sync
+        run: uv sync --locked --python ${{ matrix.python }}
+
+      - name: Format
+        run: uv run ruff format --check
+
+      - name: Lint
+        run: uv run ruff check
+
+      - name: Types
+        run: uv run mypy src
+
+      - name: Tests
+        run: uv run pytest --cov-fail-under=85

kanso-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,36 @@
+name: publish
+
+# Trusted publishing: the job requests an OIDC token and stores no credential.
+# The index-side registration must name this repository, this workflow filename
+# and the `pypi` environment exactly; a mismatch fails as an authentication error.
+
+on:
+  push:
+    tags: ["v*.*.*"]
+
+jobs:
+  publish:
+    runs-on: ubuntu-24.04
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Tag matches the package version
+        run: |
+          set -euo pipefail
+          tag="${GITHUB_REF_NAME#v}"
+          proj=$(uv run python -c "import tomllib,pathlib;print(tomllib.loads(pathlib.Path('pyproject.toml').read_text())['project']['version'])")
+          pkg=$(uv run python -c "import kanso;print(kanso.__version__)")
+          echo "tag=$tag project=$proj package=$pkg"
+          test "$tag" = "$proj" && test "$tag" = "$pkg"
+
+      - name: Build
+        run: uv build
+
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

kanso-0.1.0/.gitignore

@@ -0,0 +1,24 @@
+# Build and packaging
+dist/
+build/
+*.egg-info/
+
+# Credentials — resolved from here at the moment of use, never committed
+.env
+.env.*
+
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+
+# Tooling caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+htmlcov/
+
+# macOS
+.DS_Store

kanso-0.1.0/.python-version

@@ -0,0 +1 @@
+3.12

kanso-0.1.0/AGENTS.md

@@ -0,0 +1,203 @@
+# kanso — instructions for changing this package
+
+This repository is the `kanso` framework: a released Python package, versioned by semver.
+It is its own reference. `docs/` states what every part of it guarantees and refuses, the
+tests state it again in a form that fails when it stops being true, and the two are changed
+together or not at all. There is no design document, no decision log and no build plan; if
+something is true of kanso and is written down nowhere, that is a gap in `docs/` or in the
+suite, and the fix is to close it rather than to write a note.
+
+`docs/maintainers.md` is the other side of this file: repositories, the development loop,
+promoting an extension upstream, releases, and running the daemon as a service. Maintainer
+skills live in `skills/` — link that directory into your tool's skills path.
+
+## The standing invariants
+
+These are the properties the rest of the package is built on. Each one would be easy to
+lose in a change that looks local, so each is enforced somewhere you can read.
+
+**kanso never invokes git.** No `git` subprocess, in a workspace or anywhere else — no
+`init`, commit, branch, tag, worktree, reset or object write, by itself or on an operator's
+behalf. Committing a workspace is the operator's business; versioning the file research
+mutates is kanso's own, content-addressed in the state store. `tests/workspace/test_no_git.py`
+and `tests/cli/test_no_git.py` spy on every process launch and fail the moment one is git.
+
+**The core knows no vendor and no broker.** Every outside party lives in exactly one
+package — `data/adapters/<vendor>/` for data and reference, `nautilus/adapters/<broker>/`
+for execution and live feeds — and nothing outside it names a vendor, an endpoint, a vendor
+field or a vendor symbology. Mapping to engine types and kanso schemas happens at the
+adapter boundary. Provider specifics stay inside `models/` the same way. The isolation
+tests (`tests/data/adapters/`, `tests/nautilus/adapters/`, `tests/models/`) are a source
+scan and an import-graph check, and they read the names from the adapter directories rather
+than from a list, so a new adapter is scanned without anyone remembering to add it.
+
+**An adapter is enabled by its credentials, never by installation.** There are no extras.
+The full suite, `kanso doctor` and the demo are green with every vendor and broker
+credential unset, and CI has no credential at all, which is what proves it. A test that
+genuinely needs a real key carries the `live` marker, is deselected by default and never
+runs in CI.
+
+**Availability, not observation.** Every catalog point's `ts_init` is the instant its
+information became public and `ts_event` is its economic reference time; `ts_init >=
+ts_event` always, and the engine orders by `ts_init`. Never derive `ts_init` from
+`ts_event` or from ingest time. A delayed dataset whose `ts_init` does not come from a
+declared publication rule is refused at write (`data/publication.py`).
+
+**Costs are applied once, by the runner, in the extraction.** Commission, slippage and half
+the spread each side are deducted per fill in `nautilus/backtest.py` and nowhere else. One
+application means one number: a card, a certification gate, a composition expectation and a
+realised paper objective all read the same arithmetic, and a cost model can be re-applied to
+recorded fills without re-running anything. The simulated venue charges nothing to keep it
+that way — and it charges nothing because kanso's resolved instruments leave their maker and
+taker rates at zero, not because the venue is configured fee-free, so an instrument that
+arrives with a non-zero rate double-counts silently.
+
+**The embargo is code.** A backtest request may name only a window the hypothesis declares,
+and the card path accepts only the research window. A card runs in a child process with no
+path to any catalog — the parent reads the window and serialises the points across, and the
+child re-checks them against the window it was asked for. Never add a route by which
+research could reach the certification window, and never replace the refusal with an
+instruction to a model.
+
+**Only `strategy.py` is mutable by the research loop.** Everything fixed lives in the
+package. A proposal that names another file, does not apply, or changes nothing is a wrong
+answer that takes the retry ladder; it never becomes a card.
+
+**Real capital moves only on a named, recorded approval.** `promote --live --as NAME` is the
+only path, `--as` has no default and no environment fallback, and the approval is recorded
+against the exact version before anything moves. Paper promotion and demotion are automatic;
+this one is not, and no convenience is worth making it so.
+
+**One strategy class, one data model, one evaluation path.** Backtest, replay, paper and
+live run the same generated implementation, and a version pins the engine version it was
+certified under. `kanso replay parity` compares the two code paths element by element and
+exists to be run at a tolerance of zero.
+
+**A run optimises exactly one scalar.** Constraints are gates, never terms in an objective.
+
+**Agents decide, the framework evaluates.** Which gates, which thresholds, which constraints
+and which construct are chosen at runtime by a model from catalogues that declare
+capabilities and ranges. There are no default plans, no default thresholds and no non-LLM
+fallback for a decision an agent is supposed to make: with no model configured the step
+exits 2. The framework's own opinions are structural invariants and the construct taxonomy,
+and nothing else.
+
+**Runtime dependencies are exhaustive.** `nautilus_trader`, `pydantic`, `typer`, `pyyaml`,
+`httpx`, `numpy`, and the standard library. `pyarrow`, `pandas` and `msgspec` are reachable
+only as the engine's own transitive dependencies and only where its API hands them to you.
+`httpx` serves `models/` only. Adding a runtime dependency is a deliberate change to
+`pyproject.toml` argued in the commit body; an adapter that would need one is not
+admissible.
+
+**Pure Python.** kanso ships no compiled artefact of its own. The only Rust it executes is
+NautilusTrader's, through `nautilus_trader.core.nautilus_pyo3` — adapter network I/O uses
+its `HttpClient` and `WebSocketClient` with `Quota` rate limits.
+
+**Secrets live only in environment variables**, resolved by standard name from the
+workspace `.env` and then the ambient environment, sent in a request header and never in a
+URL path or query string, because URLs reach logs, manifests and `doctor --report`. No
+credential appears in anything kanso writes.
+
+**No notes, learnings, summaries or progress reports** — not in this repository, not in a
+workspace. The tests, the diff, the cards, the certificates and the state store are the
+record.
+
+## Toolchain
+
+`uv` for everything.
+
+```bash
+uv sync
+uv run pytest --cov-fail-under=85    # the gate CI runs; drop the flag for a partial run
+uv run ruff format
+uv run ruff check
+uv run mypy src
+```
+
+Python ≥3.12; `nautilus_trader>=1.231.0,<1.232`, one requirement for every supported host
+(macOS 26+ arm64, Linux x86_64). Tests use `pytest`, `pytest-cov` and `hypothesis`, make no
+network call and are deterministic; the `synthetic` loader and the `mock` model protocol are
+the fixtures.
+
+## Conventions
+
+- Every CLI command takes `--json` and prints exactly one object under it, exits with the
+  codes `docs/cli.md` lists, and has at least one integration test.
+- Every schema is a pydantic v2 model in `schemas/` with one property test.
+- Docstrings state the contract a module implements in words, and record the
+  NautilusTrader facts it relies on with the engine version. They never point at a document
+  outside this repository.
+- `from __future__ import annotations` everywhere. No `print()` outside `cli/`. Raise
+  `kanso.errors.{PreconditionError, ValidationError, ApprovalError}` — each carries the
+  message and, wherever there is one to give, a remedy that is a command the reader can run.
+- A new state table ships as a new file in `src/kanso/state/migrations/`, never as an edit
+  to an existing one, with the `schema_version` bump beside it.
+- Conventional commits (`feat:`, `fix:`, `test:`, `docs:`, `chore:`) on a branch named for
+  the change. Semver per `docs/maintainers.md`.
+
+## Two rules paid for in defects
+
+Both were learned the expensive way during the build and are cheap to keep.
+
+**A fixture is a claim about the world, and is worth what its evidence is worth.** Eight
+defects in the first data adapter reached a suite of 3,492 tests at 100% line coverage,
+because every fixture recorded what its author expected the vendor to do rather than what
+the vendor was measured doing: an option key asked of the wrong reference endpoint, a
+listing requested under a version prefix that answers 404, a page four times wider than the
+endpoint serves, a signed `Host` forwarded to a transport that sets its own, an empty page
+read as an entitlement refusal — which tells an operator to buy what they already own. Every
+one was invisible offline and obvious in one live call. So: record the measured response,
+say where it came from, and drive an adapter against its real source before calling the work
+done. Coverage tells you which lines ran, never whether the fixture resembles the source.
+
+**A test that recomputes a timestamp the product already took is asserting that no clock
+moved between them.** Five did, and one failed CI at 00:13 UTC when a definition was
+resolved either side of midnight and the two checksums differed. Pin the input, freeze the
+clock, or accept either instant the call spanned — never leave it to the hour the suite
+happens to run at.
+
+## Definition of done
+
+1. `uv run ruff format --check`, `uv run ruff check` and `uv run mypy src` clean.
+2. `uv run pytest` green. The enforced floor is 85% of lines in `src/kanso`; the tree is at
+   100%, and a change that lowers it has shipped lines nothing runs.
+3. `kanso doctor` green in a fresh workspace, and the demo sequence in `README.md` runs end
+   to end with every `KANSO_*` and vendor variable unset.
+4. `docs/` changed in the same commit as any operator-visible behaviour — a command, a
+   workspace file, a refusal, a skill — and the tests with it. The PR body says why.
+5. CI green on macOS arm64 and Linux x86_64, on both Python versions, before it merges.
+
+## Working style
+
+- Small commits, each green. Prefer deleting code to adding it. If a component can be a
+  function, it is not a class.
+- When the engine's API is unclear, read the installed source rather than guessing:
+  `uv run python -c "import nautilus_trader, inspect; ..."`. Check
+  `src/kanso/nautilus/facts.py` first — it asserts what this build relies on, and
+  `kanso doctor` re-checks every claim against the installed engine and names the ones that
+  no longer hold.
+- **A fixture is a claim about an outside party, and it is worth what its evidence is
+  worth.** Eight defects reached a green suite at 100% line coverage during the build
+  because the fixtures encoded what an author expected instead of what the vendor did.
+  Coverage says which lines ran, never whether the fixture resembles the source. Drive an
+  adapter against the real thing before trusting it, and record the measured response.
+- Prose fails the same way. Every command a document shows must have been run, and if the
+  code and the explanation disagree, the code is what happened.
+
+## Where things are
+
+| directory | what it holds |
+|---|---|
+| `cli/` | every command, its `--json` object and its exit codes |
+| `schemas/` | a pydantic model for every file kanso reads or writes |
+| `state/` | the store and its migrations |
+| `data/` | the catalog, manifests, snapshots, loaders, instruments, `adapters/<vendor>/` |
+| `nautilus/` | the strategy base, the runner, the venue, the node, replay, `facts.py`, `adapters/<broker>/` |
+| `classify/` | the construct catalogue and the classifier |
+| `criteria/` | objectives and gates, with the declared toolbox in `library/` |
+| `hyp/`, `research/` | registration, the loop, the driver, the daemon, alignment |
+| `certify/`, `strategy/` | the planner, certificates, composition and versions |
+| `portfolio/`, `monitor/`, `replay/` | stages, deployment, promotion, surveillance, the two code paths |
+| `models/` | the register, the router, the two wire protocols and the mock |
+| `inbox/` | the five escalation kinds and the append-only file |
+| `skills/`, `templates/` | what ships into an operator's workspace |

kanso-0.1.0/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Changelog
+
+One line per user-visible change, newest release first. The format is the one
+`docs/maintainers.md` §4 and the `kanso-release` skill require; versions are semver.
+
+## Unreleased
+
+- `kanso doctor` grades a state database written by a later kanso as a failure rather than reporting it up to date, so it no longer disagrees with every other command about whether a workspace is usable.
+
+- `kanso data sync` extends only the **newest** dataset of each series, so a series with a chunked backfill behind it can be continued at all; `--dataset` still names one directly, newest of its series or not.
+- `kanso data instruments resolve` builds the `[data] reference` adapter only once an id is actually left unresolved, so a wholly manual universe resolves with that adapter's credential unset.
+- A baseline that did not run reports the remedy of the failure that ended it — rows the catalog no longer holds send an operator to `kanso data load` — where every cause alike used to say `fix hypotheses/<id>/strategy.py`.
+- `kanso hyp validate` and `kanso hyp add` refuse a construct parameter the construct does not declare, or a value outside its declared set (exit 3); the refusal used to arrive inside a run's first card.
+- `kanso hyp validate` and `kanso hyp add` refuse `portfolio` as a hypothesis id (exit 3): it is how a construct attached to the book names its host.
+- `kanso portfolio deploy` and `kanso replay run --strategy` hash every file under `strategies/<id>/impl/<version>/` against the `strategy_sha` its manifest records, and refuse an edited, truncated or deleted source by name (exit 3), naming the certified copy to restore it from.
+- `kanso portfolio show` reads `portfolio.yaml` against the record: a stage entry no deployment wrote prints as `not deployed · in portfolio.yaml only`, carries `"recorded": false` under `--json`, and counts towards neither the stage's allocation nor its P&L nor whether its node is up.
+- `kanso cert plan` warns when the paper window the plan implies is under a tenth of the certification window the hypothesis declares, and pins the plan either way; `warnings` under `--json`.
+- A `kanso_ext` module declaring `gates` or `objectives` in `PROVIDES` is refused where it is declared: no registry reads either kind, and a criterion is written in the package.
+- `kanso doctor`'s shadow check reads one registry per kind a declaration may carry — the packaged constructs, the custom data types and the framework's own `sandbox` execution client included — where it read three kinds out of seven.
+- `[adapters.alpaca] poll_interval_s` sets the live feed's sweep cadence, `1` to `3600` seconds and still 15 by default, refused out of range when the table is read; it was a constructor argument no workspace could reach.
+
+## v0.1.0 — 2026-09-06
+
+First release.
+
+- `kanso init [--demo]`: a workspace is a plain directory; `--demo` runs end to end with no credential of any kind.
+- `kanso doctor [--report] [--check-adapters]`: thirteen checks over the workspace, the install, the engine, the credentials, the adapters, the execution clients and the lanes.
+- Data: `data load`, `show`, `snapshot`, `backfill`, `sync`, `instruments resolve|show`, `adapters [--check]`; one catalog, manifests recording the span a source *served*, immutable snapshots.
+- Availability: every point carries `ts_init` (public) and `ts_event` (economic), `ts_init >= ts_event`; a delayed dataset with no declared publication rule is refused at write.
+- Hypotheses: `hyp new|validate|add|show|retire` and `classify`; a hypothesis is pinned by the sha256 of its bytes and its progress lives in `state.db`.
+- Constructs: seven in the catalogue, four runnable — `sleeve`, `filter`, `overlay` on a sleeve, `exit`; `alpha`, `execution` and portfolio-hosted `allocation` classify and refuse at `research begin` naming their seam.
+- Research: `research begin|card|run|end|show`, the keep rule with its noise floor and complexity clause, `align check`, and the daemon (`research start|stop|status|queue`).
+- The embargo is code: a card runs in a child process with no path to any catalog, and the `strategy_integrity` syntax-tree check runs before the backtest.
+- Certification: `cert plan|run|show`; no default plan and no non-LLM fallback, gates chosen at runtime inside the toolbox's declared ranges, certificates immutable and pinned to plan, snapshot and engine version.
+- Strategies and the portfolio: `strat compose|show|retire`, `portfolio show|clients|deploy`, `promote --live --as NAME`, `demote`, `monitor run`; one generated `impl/<version>/` loaded by backtest, replay and node alike.
+- Real capital moves only on a named, recorded approval; `deploy` refuses six things with exit 2 and two with exit 4.
+- Replay: `replay run|parity|show`, comparing the live and research code paths element by element at a tolerance meant to be zero.
+- Models: `models check`, a register routed by task class and tier, every call ledgered including a retry's failed attempts.
+- Operating: `status`, `inbox [ack]`, `migrate`, `skills sync`, `env detect`, `ext show`.
+- Adapters: one first-party data vendor and one first-party broker, both enabled by their credentials and never by installation; the core knows neither.
+- Extensions: `kanso_ext/` provides loaders, constructs, custom data types, data adapters and execution clients; a packaged id always wins.
+- Eleven operator skills and the workspace templates ship inside the wheel.
+- Python ≥3.12 on macOS 26+ arm64 and Linux x86_64; `nautilus_trader>=1.231.0,<1.232`; no compiled artefact of kanso's own.
+- A state database this kanso cannot correctly write is refused in both directions, by the command layer and by the daemon entry point a service unit starts: behind the package names the migration to run, ahead of it names how far, and neither is silently written to.

kanso-0.1.0/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

kanso-0.1.0/LICENSE

@@ -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.