@kontourai/flow-agents 0.1.1

package/CONTEXT.md

@@ -0,0 +1,300 @@
+# Flow Agents Context
+
+## Glossary
+
+### Flow Agents
+
+An operating layer that helps agents route natural user requests into the right procedures, tools, state, evidence, knowledge, and follow-ups without requiring the user to remember implementation details. Flow Agents is a product that applies Flow and Veritas discipline inside the agent tools people already use.
+
+### User
+
+The person asking Flow Agents for an outcome. Use `end user` only when contrasting the user's vocabulary with Flow Agents internals.
+
+### Work Mode
+
+A user-facing category of intent, such as Build, Understand, Capture, Prepare, or Follow Up. Work modes help Flow Agents decide which operating path to use.
+
+### Build
+
+The work mode for creating, changing, fixing, verifying, publishing, or shipping software and other buildable artifacts.
+
+### Builder Kit
+
+The first Kontour-authored Flow Kit for opinionated AI-assisted building work. The Builder Kit owns shaping, probing, planning, execution, verification, merge readiness, PR readiness, and learning workflows.
+_Avoid_: Development pack, generic coding workflow
+
+### Initiative
+
+A larger product, platform, governance, or dogfood outcome that groups related executable work. Initiatives are optional first-class Kontour Resource Contracts for planning and traceability, not executable units. Initiatives explain why related work belongs together; dependency links explain what must happen before other work can proceed.
+_Avoid_: Epic, Feature as the generic term
+
+### Understand
+
+The work mode for explaining what exists, researching context, comparing options, or making accumulated information understandable.
+
+### Capture
+
+The work mode for turning raw input into durable memory, such as notes, decisions, meetings, transcripts, source material, and useful pointers.
+
+### Prepare
+
+The work mode for getting ready for a meeting, review, planning session, customer conversation, or decision.
+
+### Follow Up
+
+The work mode for tracking commitments, open loops, tasks, reminders, activity logging, and next actions.
+
+### Capability
+
+Something a work mode needs from the outside world or from Flow Agents infrastructure, such as a backlog, knowledge store, CRM, calendar, email, docs store, CI system, or code host.
+
+### Provider
+
+A configured implementation of a capability, such as GitHub for backlog, Obsidian for knowledge storage, or Google Calendar for calendar access.
+
+### Provider Contract
+
+The declared capabilities, defaults, conventions, and limits of a provider type. Provider contracts make integrations predictable and testable without requiring the live provider.
+
+### Kontour Resource Contract
+
+A versioned Kontour record shape for durable machine-readable configuration, scope, run state, evidence, provider output, and cross-product interchange. Kontour Resource Contracts are the default for new pre-public durable contracts unless a product records why a native shape is clearer.
+_Avoid_: Manifest as the generic term, Kubernetes resource when Kubernetes is not the runtime
+
+### Local-First Default
+
+A baseline provider choice that works with local files before hosted integrations are configured. Local-first defaults should preserve durable records, relationship links, source pointers, follow-ups, status, searchability, and migration paths.
+
+### Relationship Link
+
+A durable connection between records, people, customers, projects, initiatives, issues, meetings, follow-ups, or source systems. Local-first providers may store relationship links as Markdown links or pointers; richer providers may map them to backlinks, graph edges, CRM relationships, or issue links.
+
+### Skill
+
+A reusable procedure Flow Agents can invoke to carry out part of a work mode. Skills are implementation details from the user's perspective.
+
+### Flow Kit
+
+An installable, authorable bundle of Flow-backed workflows and optional supporting assets, such as Flow Definitions, docs, skills, adapters, provider contracts, and evals. Flow Kits are runtime-neutral: skills are one supported asset type, not a requirement.
+_Avoid_: Pack, plugin, marketplace package
+
+### Flow Kit Repository
+
+A local folder or remote repository with a Flow Kit manifest at its root. A Flow Kit Repository can be installed by Flow or Flow Agents from a local path, git URL, GitHub shorthand, or package registry source.
+_Avoid_: Skill repository as the generic term
+
+### Workflow
+
+A stateful multi-step path with gates, handoffs, evidence, and next actions. Not every task or skill needs a workflow.
+
+### Gate
+
+A workflow checkpoint that decides whether a Workflow Run can advance, must stop, or should route back. Gates record structured evidence, gaps, authority, actors, attempts, and route decisions, while exposing Status Condition summaries for shared reporting rather than relying on hidden agent confidence.
+
+### Status Condition
+
+A current, inspectable statement about the lifecycle state of a Kontour Resource Contract, Gate, Workflow Run, or Delivery Run. Status Conditions summarize status, reason, message, evidence pointers, and transition time without replacing the underlying evidence record. Static definitions do not need Status Conditions unless they are installed or applied into an environment.
+
+### Core Condition Vocabulary
+
+The small shared set of Status Condition meanings Flow Agents standardizes for interoperability, reporting, Console views, evals, and analytics. Flow Kits may add domain-specific condition reasons, but shared conditions such as ready, blocked, in progress, scope overlap, scope changed, configuration gap, missing evidence, and route-back required should keep the same meaning across kits.
+
+### Scope Overlap
+
+A Status Condition indicating that one Workflow Run's active Selected Scope intersects with another active Workflow Run or provider-backed work record. Scope Overlap supports Alignment Gate coordination without implying distributed lock, lease, or reservation semantics.
+_Avoid_: Scope Reservation, Lease, Lock
+
+### Gate Role
+
+Optional metadata that describes the kind of decision a Gate is making, such as alignment, readiness, review, verification, evidence, publication, release, or approval. Gate Roles provide shared language for reporting and adapters; Workflow or Flow Kit definitions decide the required evidence and route-back behavior.
+_Avoid_: Gate Type when implying rigid core behavior
+
+### Alignment Gate
+
+A Gate that confirms intent, selected scope, assumptions, authority, or user decisions before a Workflow Run advances. Alignment Gates may be satisfied from context, provider state, explicit approval, or a kit-specific interaction such as a Probe.
+
+### Publication Gate
+
+A Gate that makes a Workflow Run output externally inspectable or consumable through a provider or durable artifact. Publication Gates are core; Builder Kit's Prepare PR is the code-host pull request implementation.
+
+### Release Gate
+
+A Gate that decides whether a published Workflow Run output can be accepted, merged, released, deployed, held, or rolled back. Release Gates are core; Builder Kit's Merge Readiness is the code-host pull request implementation.
+
+### Gate Actor
+
+The person, agent, provider, automation, or authority allowed to evaluate, satisfy, or approve a Gate. Gate Actors are separate from Gate Roles because a verification, release, or approval gate may require different actors in different Workflows.
+_Avoid_: Gate Role for permission semantics
+
+### Required Capability
+
+The provider, tool, or runtime capability needed to evaluate a Gate, such as CI checks, a code host pull request, browser automation, a calendar provider, a CRM, a governance adapter, or a Surface trust provider.
+
+### Required Evidence
+
+The proof a Workflow or Flow Kit says a Gate needs before it can pass. Flow Agents owns the evidence mechanics; the Workflow or Flow Kit defines which evidence is required for each Gate.
+
+### Route Back
+
+The workflow transition selected when a Gate cannot advance and the next useful action is an earlier step. Flow Agents owns route-back recording and loop-protection mechanics; the Workflow or Flow Kit defines the route reasons and target steps.
+
+### Attempt
+
+A deterministic count of how many times a Workflow Run has evaluated or retried a Gate, Step, or Route Back path. Flow owns attempt counting for workflow enforcement; Flow Agents records attempt metadata for agent workflow analysis, evals, and learning.
+
+### Reason Code
+
+A stable explanation for why a Gate passed, failed, could not be verified, or routed back. Flow Agents provides a small shared reason vocabulary for analytics and interoperability, while Flow Kits may define domain-specific reason codes.
+
+### Workflow Run
+
+One execution of a Workflow from selected scope through its gates, evidence, route-backs, and terminal outcome. A Workflow Run references its canonical Selected Scope and snapshots the selected subject identifiers for audit history. Builder Kit Delivery Runs are a build-specific kind of Workflow Run.
+_Avoid_: Delivery Run as the generic term
+
+### Run Plan
+
+The core workflow-level plan for a Workflow Run. Run Plans describe intended gate order, selected scope, required capabilities, required evidence, route-back policy, and learning points without assuming the work is software delivery.
+_Avoid_: Execution Plan as the generic term
+
+### Selected Scope
+
+The first-class Kontour Resource Contract that declares the explicit subject or set of subjects a Workflow Run is authorized to operate on. Selected Scope may include Work Items, files, documents, customers, meetings, research sources, or other provider-backed records, and it should be narrow enough for the workflow's gates to evaluate coherently. Material Selected Scope changes route back to an Alignment Gate.
+_Avoid_: Work Item Group as the generic term
+
+### Scope Change
+
+A recorded event or Status Condition describing a change to the Selected Scope of a Workflow Run. Material Scope Changes route back to an Alignment Gate so coordination, authority, overlap, and downstream Work Item impact can be evaluated before continuing.
+_Avoid_: Boundary Crossing as the generic Flow Agents term
+
+### Work Item
+
+An executable backlog or queue unit selected by a workflow. Work Items are provider-backed when a backlog provider is configured, and Flow Agents keeps a portable local-first Kontour Resource Contract shape for local use, tests, kit demos, and migration. A Work Item is smaller than an Initiative and large enough to move through one coherent Workflow Run with clear acceptance evidence.
+_Avoid_: Task as the generic term, Issue as the provider-neutral term
+
+### Work Item Group
+
+A Builder Kit Selected Scope containing multiple related Work Items delivered through one Delivery Run because grouping reduces coordination risk and preserves one coherent acceptance and evidence story. Work Item Groups are exceptions justified by `pull-work`; they do not replace Initiatives.
+_Avoid_: Initiative, Execution Wave, batch as the generic term
+
+### Delivery Run
+
+One attempt to deliver a selected Work Item or justified Work Item Group through alignment, planning, execution, review, verification, publication, evidence, release readiness, and learning.
+_Avoid_: Task, issue, wave
+
+### Execution Plan
+
+The Builder Kit delivery-specific plan for a selected Work Item or Work Item Group. An Execution Plan specializes a Run Plan with implementation approach, file ownership, verification strategy, publication strategy, and how work is divided into Execution Waves.
+_Avoid_: Run Plan as the generic term, Backlog plan, Initiative plan
+
+### Execution Wave
+
+A subdivision inside one Execution Plan used to organize implementation work, often for parallel workers. Execution Waves are not backlog units and do not create new Work Item scope.
+_Avoid_: Work Item, Work Item Group
+
+### Prepare PR
+
+The Builder Kit Publication Gate that turns a locally verified Delivery Run into a reviewable external code-host change. Prepare PR includes commits, branch push, pull request creation or update, Work Item links, PR body evidence, and CI trigger preparation.
+_Avoid_: Evidence Gate, Release Readiness
+
+### Merge Readiness
+
+The Builder Kit Release Gate that decides whether a published code-host change is ready to merge. Merge Readiness may use provider state such as pull request mergeability and CI checks, and may also use optional governance evidence such as Veritas when configured.
+_Avoid_: Veritas readiness as the only meaning
+
+### Provider Mergeability
+
+The code-host provider's merge signal for a published change, such as pull request existence, mergeable state, branch protection, review state, and CI or status checks. Provider Mergeability is one sub-check of Builder Kit Merge Readiness.
+
+### Governance Readiness
+
+Optional policy or trust-backed readiness evidence for a published change, such as Veritas readiness, Surface trust claims, repo standards, protected area authority, evidence freshness, or boundary checks. Governance Readiness is one sub-check of Builder Kit Merge Readiness when configured.
+
+### Configuration Gap
+
+A reason code for a Gate that cannot be evaluated or cannot pass because a required provider, capability, or setting is missing, invalid, unavailable, or incompatible. Required Configuration Gaps block advancement; optional Configuration Gaps should be recorded as advisory or not verified with remediation.
+
+### Probe
+
+A Builder Kit Alignment Gate that explores context, challenges assumptions, and records aligned decisions before the process continues. A Probe asks one question at a time, recommends an answer, and uses repository context before asking when the answer can be discovered.
+_Avoid_: Grill, interrogation
+
+### Flow
+
+Kontour AI's process transparency and gate enforcement layer. Flow owns steps, gates, transitions, Flow Runs, exceptions, continuation, and Flow Reports. Flow Agents consumes Flow for agent-facing workflows rather than owning the generic enforcement kernel.
+
+### Project Settings
+
+Settings that apply to a repo, folder, team workspace, customer effort, writing effort, or personal initiative. Project Settings override Global Settings for that project.
+
+### Global Settings
+
+The user's default Flow Agents setup across projects.
+
+### Runtime Adapter
+
+The translation layer that turns Flow Agents source configuration and operating concepts into a specific runtime's native shape.
+
+### Framework Adapter
+
+A Runtime Adapter for API- or framework-based agents such as LangGraph, Strands, CrewAI, VoltAgent, or direct model-inference systems. Framework Adapters map framework events, state, and tool calls into Flow Runs, gates, and evidence.
+_Avoid_: Skill, hook, plugin as the generic term
+
+### Runtime Portability
+
+The requirement that Flow Agents provide a consistent operating experience across agent runtimes such as Pi, Claude Code, Codex, Kiro CLI, Droid, Hermes, and future runtimes. Flow Agents should not depend on owning the chat interface or agent runtime.
+
+### Workflow Enforcement
+
+The Flow Agents principle that important work should move through explicit gates without hidden shortcuts. Each gate should expose inspectable evidence, gaps, or user decisions before the workflow advances.
+
+### Learning
+
+The feedback loop that turns workflow outcomes, friction, failures, user corrections, and evidence gaps into durable improvement candidates. Learning is a core capability, but not every terminal Workflow Run needs a Learning record.
+_Avoid_: Retrospective as the generic term
+
+### Traceability
+
+The ability to inspect what the agent was asked to do, which operating path it followed, what evidence was collected, which gates passed or failed, and why the next action is trustworthy or blocked.
+
+### Governance Adapter
+
+An optional integration that supplies policy, proof, or trust evidence without making Flow Agents own the external tool's rule semantics. Veritas is the first known governance adapter candidate.
+
+### Claim Expectation
+
+A gate-level expectation for a Surface claim type, accepted trust statuses, and whether missing or rejected evidence should block the transition. Claim Expectations describe what a Flow gate needs without naming the producer that will satisfy it.
+_Avoid_: Provider-specific requirement, Veritas requirement
+
+### Trusted Producer
+
+A Surface producer accepted by a project or runtime config as authoritative for one or more claim types. Trusted Producers satisfy Claim Expectations by emitting Surface claims with acceptable trust status and authority trace.
+_Avoid_: Hardcoded provider, tool name inside a Flow Definition
+
+### Flow Agents Source Config
+
+The portable Flow Agents configuration owned by Flow Agents itself.
+
+### Kit Catalog
+
+The Flow Agents index that lists available Flow Kits and the runtime assets each kit installs. The Kit Catalog points to Flow Kit content; it does not define workflow gate semantics itself.
+_Avoid_: Pack manifest, global workflow spec
+
+### Runtime Config
+
+Configuration generated or maintained for a specific runtime such as Codex, Claude Code, or Kiro.
+
+### Console
+
+The optional visual setup, status, usage, and improvement surface for Flow Agents. Flow Agents should work without opening the Console, but the Console helps users configure modes and providers, inspect global and project settings, view active workflow state, review telemetry and eval outcomes, and act on suggested improvements.
+
+### Project Console
+
+The default Console view when launched from a workspace. It shows effective settings, provider overrides, active workflow state, usage, evals, and improvement opportunities for the current project while also explaining inherited Global Settings.
+
+### Global Console
+
+The Console overview for global setup, registered projects, cross-project usage, global providers, and system-wide improvement opportunities.
+
+### Control API
+
+The shared tool layer used by the Console, CLI, AI agents, and automation. The Control API owns operations such as reading effective settings, explaining provider resolution, testing provider health, previewing config changes, writing config, inspecting workflow state, and reporting usage or eval outcomes.

package/CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing
+
+This file is intentionally short.
+
+The main docs in this repo are written for people installing and using Flow
+Agents. This file is the footnote for people developing the product itself.
+
+## Development Rules
+
+- keep the core product generic — no machine-specific paths, usernames, or
+  private workspace assumptions in tracked source
+- the public bundle ships the `core` and `development` packs; keep new work
+  inside that scope
+- prefer install/use clarity over maintainer cleverness
+- update the relevant docs, `packaging/packs.json`, and `packaging/manifest.json`
+  whenever you add or remove a skill, agent, or power
+- keep `docs/context-map.md` current with `npm run context-map`
+- run `npm run build && npm run validate:source && bash evals/ci/run-baseline.sh`
+  before opening a PR
+
+## Docs Site Preview
+
+The GitHub Pages site is built from `docs/` by the `Publish Docs` workflow
+using Jekyll. To preview locally, install Jekyll 3.9 with the github-pages
+default plugins and build into the ignored `_site/` directory:
+
+```bash
+gem install --user-install jekyll -v 3.9.5 jekyll-optional-front-matter \
+  jekyll-relative-links jekyll-readme-index jekyll-titles-from-headings \
+  kramdown-parser-gfm
+"$(ruby -e 'print Gem.user_dir')/bin/jekyll" build --source docs --destination _site
+```
+
+Set `FLOW_CLI_ROOT` to a Flow checkout or installed `@kontourai/flow` package
+root to enable full Flow Definition validation in `npm run validate:source`.
+
+## Validation
+
+- `npm run validate:source` — source-tree integrity (paths, packs, manifests)
+- `npm run context-map:check` — context map is current
+- `bash evals/ci/run-baseline.sh` — deterministic CI baseline
+- `npm run check:content-boundary` — no private/internal content leaks
+
+All projects are Apache-2.0.

package/LICENSE

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