roboz 0.1.2a1__tar.gz

roboz-0.1.2a1/.gitignore

@@ -0,0 +1,54 @@
+# Python bytecode
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Virtual environments and local configuration
+.venv/
+venv/
+.env
+.env.*
+!.env.example
+
+# Tests, coverage, and static analysis
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+junit.xml
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.pyright/
+.hypothesis/
+.tox/
+.nox/
+
+# Packaging and generated documentation
+build/
+dist/
+wheels/
+*.egg-info/
+.eggs/
+site/
+
+# Local font sources used to generate outlined branding
+/*.otf
+/*.ttf
+
+# Editors and operating systems
+.idea/
+.vscode/
+.VSCodeCounter/
+*.swp
+*.swo
+*~
+.DS_Store
+Thumbs.db
+
+# Robozium local runtime output
+rbz_data/
+worktrees/
+
+# CI diagnostics
+reports/

roboz-0.1.2a1/CHANGELOG.md

@@ -0,0 +1,261 @@
+# Changelog
+
+## Unreleased
+
+## 0.1.2a1 - 2026-09-23
+
+- Add password-encrypted `.env.encrypt` output beside an untouched `.env`,
+  with a hidden-password CLI command, explicit loading, and deferred endpoint
+  loading. Plaintext dotenv files remain supported.
+
+- Breaking: replace the endpoint inventory `export`, `import`, and `reset`
+  commands with `init` and `generate`. Project JSON remains the editable source;
+  generated Python refreshes without `--force` while unrelated files remain
+  protected. Bundled and generated catalogues retain typed model autocomplete.
+
+## 0.1.2.dev12 - 2026-09-21
+
+- Breaking: consolidate core, Shed, and Endpoints into the `roboz`
+  distribution. Replace `roboshed` imports with `roboz.shed` and
+  `roboz_endpoints` imports with `roboz.endpoints`; no compatibility packages
+  or forwarding namespaces are provided.
+- Install the OpenAI SDK as a required dependency while retaining deferred
+  endpoint client construction and credential-free imports. Remove package
+  extras and the `roboz-endpoints` executable; manage catalogues with
+  `python -m roboz.endpoints inventory`.
+- Exclude Proton Bridge from the consolidated distribution. Its pre-migration
+  implementation and development setup remain preserved on the
+  `wip/proton-bridge` branch.
+- Consolidate package documentation into the main README and move the detailed
+  project catalogue guide to `docs/catalogues.md`.
+
+## 0.1.2.dev11 - 2026-09-21
+
+- Ship the simple and complex examples in `roboz.examples`, so installed users
+  can run the credential-free agent demo with `python -m roboz.examples.simple`
+  without cloning the repository.
+
+## 0.1.2.dev10 - 2026-09-21
+
+- Define default tools as scheduler-owned chain roots: downstream tools can now
+  reference a default-only parent with `chained_to`, while defaults that are
+  themselves chained downstream are rejected during agent construction.
+
+## 0.1.2.dev9 - 2026-09-20
+
+- Remove the leftover `proton-bridge-beta` installation extra. Install
+  `roboz-proton-bridge` directly, consistently with the other independently
+  published companion distributions.
+
+- Make images and links in the published package description resolve outside
+  the GitHub repository.
+
+## 0.1.2.dev8 - 2026-09-20
+
+- Breaking: remove the legacy agent master tool. Model-driven agents run
+  their configured default tools followed by the built-in `prompt_agent` tool;
+  deterministic agents require and run only their configured default tools.
+  Use `default_tools` to configure deterministic steps instead of relying on
+  the removed `master_tool` attribute.
+
+- Show every displayed tool's external dependency IDs and kinds in
+  `Agent.show_agent_info()`.
+
+## 0.1.2.dev7 - 2026-09-20
+
+- Breaking: replace the `is_agentic` boolean with the string-valued
+  `AgentMode.DETERMINISTIC`, `.STEERABLE`, or `.AUTONOMOUS` enum (the default
+  remains steerable). Autonomous agents use model-driven scheduling without a
+  user-input tool or direct user-interaction sidecar; their tools communicate
+  through the event pipe. Remove `interaction_mode` arguments and
+  `set_interaction_mode` calls: invocation uses a bound host channel, defaulting
+  to CLI, and restores the previous binding automatically. Registering a
+  `UserIO` adapter selects `Output.API` for the binding's lifetime.
+  `AgentMode` now lives in `roboz.models`; the existing `roboz.agent` export
+  remains available for compatibility.
+
+- Run each configured default tool exactly once per cycle for deterministic agents.
+  Model-driven agents retain their master-tool step.
+
+- Filter conversation history with `roboz.models.filter_messages` by role,
+  requested action, or result caller while retaining message order and metadata.
+
+- Call `get_completion(endpoint=..., messages=...)` directly without an API
+  callback. `MockLLMEndpoint` now accepts literal text responses as well as JSON
+  objects and exceptions.
+- Breaking: completions without an output model or tool list now return raw text
+  verbatim instead of attempting action validation. Supply `LlmOutputModel=...`
+  or `active_tools=...` to retain structured dictionary results and repair retries.
+  Endpoint and callback arguments are mutually exclusive. See the
+  [completion guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/tool-authoring.md#standalone-llm-backed-tools).
+
+## 0.1.2.dev6 - 2026-09-15
+
+- Breaking: make the `roboz` root a lazy authoring facade. It now exports only
+  `Agent`, `Skill`, `Tool`, `Factory`, `tool`, and `factory` alongside discoverable
+  domain namespaces. Import models from `roboz.models`, agent helpers from
+  `roboz.agent`, built-in tools from `roboz.tools`, and context protocols from
+  `roboz.tooling`. See [the import migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/imports.md).
+
+## 0.1.2.dev5 - 2026-09-13
+
+- Add `LLMEndpointRoute`, a typed live-selection layer above concrete chat
+  endpoints. Routes retain a caller-owned endpoint getter, report the current
+  selected resource without initializing clients, and resolve once per model
+  operation so in-flight calls retain their endpoint. Request and OpenRouter
+  policies support routes while keeping fixed endpoint use unchanged.
+
+- Inspect a configured deployment with `DeployableAgent.external_dependencies()`.
+  It builds fresh, unstarted agents without event sinks and delegates to their
+  existing tool inspection, including child agents and skill resources. Capability
+  construction still runs normally; no additional dependency declaration is required.
+
+- Initialize factory contexts lazily on invocation through the optional
+  `Materializable.materialize() -> Self` protocol. Binding, copying, and inspection
+  stay side-effect free. Endpoints support explicit early `materialize()` calls
+  while preserving their identity; prompt contexts delegate initialization.
+  Breaking: OpenAI-compatible client protocols now require `close() -> None` for
+  typed cleanup. See [the lifecycle contract](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
+
+- Make resource-inspection declarations explicit: aggregate contexts and agents
+  implement the `HasExternalDependencies` protocol, renamed from `Context` with
+  no compatibility alias. Authors can inherit it to require
+  `external_dependencies()`; missing implementations fail type checking and
+  instantiation. Plain contexts remain unrestricted, and direct resources inherit
+  inspection from `ExternalDependency`.
+
+- Breaking: migrate core interaction and agent factories to concrete contexts.
+  Bind interaction factories to strings, `run_subagent` to the child `Agent`,
+  and background/prompt factories to `BackgroundAgentContext`/`PromptAgentContext`
+  from `roboz.agent`. Background constructors own fresh state; rebinding and copies
+  share supplied state. Agent inspection uses live tool methods, and deployment
+  builders use the same bindings. Restore top-level agent, skill, and built-in
+  tool exports; removed dependency and `Ctx` APIs stay removed. See
+  [the primitive migration](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
+
+- Breaking: core endpoints require synchronous OpenAI-compatible clients instead
+  of an untyped client. Client methods and request controls are checked statically;
+  the real `openai.OpenAI` client satisfies the protocols without a wrapper or an
+  SDK dependency in core. Replace placeholder or incompatible clients with a
+  conforming chat/transcription client. See [the client contract](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
+
+- Breaking: external resource implementations must provide `check() -> bool` for
+  explicit availability checks. Executables check PATH; core endpoints use model
+  discovery without generating output. Results are uncached, absent resources
+  return `False`, and check errors propagate. Binding, copying, and inspection
+  never invoke checks. Plain contexts need no check method. See
+  [resource inspection and availability](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
+
+- Accept any concretely typed factory context, including plain objects and lists.
+  Contexts without resource inspection are passed through unchanged and their
+  tools report no dependencies. Wrong context types remain static binding errors.
+
+- Bind core chat and transcription endpoints directly as typed factory contexts,
+  retaining their identity and client for execution and inspection. Endpoint
+  request helpers and the selector now use concrete endpoints; lazy construction
+  and companion migrations remain deferred. Scripted endpoints report no external
+  resources. See [typed contexts and resource inspection](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
+- Fix `@factory()` input inference so parenthesized factories retain the same
+  concrete input, output, and context types as bare `@factory` declarations.
+
+- Breaking checkpoint: bind factories directly to concrete typed resources or
+  contexts with optional `external_dependencies()`, preserving the supplied object and
+  inspecting it live. Replace `Ctx` and tool dependency properties with concrete
+  contexts and `tool.external_dependencies()`. Dependency extension primitives
+  stay in `roboz.dependencies`; the top-level API now exposes only data and
+  tool/factory/context primitives. Remove legacy dependency bases, lazy/reference
+  helpers, and checker registration. Agent, built-in tool, and companion consumers
+  remain unmigrated; this checkpoint is not release-ready. See [typed contexts and resource inspection](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md)
+  for the contract, removed APIs, and migration boundary.
+
+## 0.1.2.dev4 - 2026-09-12
+
+- Breaking: make `DeployableAgent` an explicitly configured class. Constructor
+  capabilities are protected defaults; append capabilities and child agents with
+  the add methods, configure endpoints and runtime values separately, and unpack
+  `(agent, background_agents)` from `build()`. `build_graph()` is removed.
+- Breaking: capability builders now declare concrete `required_attributes` and
+  receive `build(agent, pipe)`. Builds validate the complete graph before
+  constructing sinks, pipes, or tools and aggregate missing, `None`, and
+  incorrectly typed owner attributes.
+
+## 0.1.2.dev3 - 2026-09-11
+
+- Breaking: remove the redundant `roboz[shed]` installation extra. Install
+  `roboshed` directly; it installs its compatible core Roboz dependency.
+
+- Add `DeployableAgent.build_graph()` to return the root agent and all background
+  handles for host lifecycle control. `build()` still returns the root alone.
+
+- Breaking: replace `AgentDefinition` and `SubAgentSpec` with recursive
+  `DeployableAgent` definitions. Put child definitions directly in `subagents`
+  or `background_agents`; delegation tools use the child's name and description,
+  and background agents start through default tools. Construct generic
+  definitions directly with `DeployableAgent(...)`.
+  Sandbox-aware `Deployment` lives in `roboshed.deployments`, not core.
+  See [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md) for migration.
+
+## 0.1.2.dev2 - 2026-09-09
+
+- Breaking: remove the `roboz[openai]` extra. Install
+  `roboz-endpoints[openai]` directly for the endpoint catalogue and SDK adapter;
+  it installs core automatically.
+
+- Breaking: move dependency primitives from `roboz.tooling.dependencies` and
+  `roboz.tooling` to `roboz.dependencies`. Update those imports; the existing
+  top-level `roboz` authoring API remains available. See [the archived context migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/context-migration.md).
+
+- Add `DependencyRoute` for live caller-owned selections. Materialization and discovery delegate to the current target without introducing a separate identity or caching the selection.
+
+- Breaking: capability builders receive `build(pipe, *, default_endpoint)`.
+  Capabilities own their tool-specific endpoint choices and receive the agent
+  endpoint as a fallback, independently of runtime controls. Lazy/live
+  references retain identity and deferred resolution. See
+  [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md) for builder migration.
+
+- Breaking: move the Librarian and its memory/summarization tools out of core into `roboshed.agents` and `roboshed.tools`. Use `librarian(sandbox, agent_names, agent_endpoint=...)` instead of `LibrarianConstructor` and its path record; see [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md). Core retains control, interaction, and generic construction primitives.
+
+- Add generic `AgentDefinition`, `AgentCapability`, `Capability`, and `SubAgentSpec` in `roboz.deployment`. Configure all tools and skills through capabilities, with fresh agent pipes and explicit sink configuration; definitions select no project, memory, or persistence conventions. See [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md).
+
+- Breaking: `roboz[shed]` now installs `roboshed` instead of `roboz-shed`. Update direct requirements to `roboshed` and imports from `roboz_shed` to `roboshed`; no compatibility package is provided.
+
+### Added
+
+- Select lazy model endpoints with `ModelSelector` from `roboz.llm` or
+  `roboz.llm.endpoints`, without requiring Shed or constructing clients.
+
+- Bind exact dependency registrations with `roboz.dependencies`, independently
+  of Shed. Registration types, checker callbacks, and contract errors now live
+  alongside dependency discovery and resolution primitives.
+
+- Add `ExternalDependencyReference` for replaceable resources. Endpoint helpers
+  preserve live selection and discovery through contexts, tools, and agents,
+  while lazy resources retain their identity validation and cached clients.
+
+- Inspect resources before binding tools with `Ctx.external_dependencies()`.
+  Contexts implement `ExternalDependencySource`, preserving resource identity
+  and reflecting live nested contexts, agents, and catalogs without resolving
+  lazy resources. `external_dependencies` is now a reserved context field name;
+  see [the archived context migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/context-migration.md).
+
+### Fixed
+
+- Refresh lifecycle endpoint metadata when invoking an agent again after a live
+  reference switches models, while retaining each lazy dependency's client cache.
+
+### Changed
+
+- **Breaking:** Construct tool contexts with `Ctx(**values)` and pass resources
+  directly. Remove `FactoryCtx`, specialized context classes, `ToolDependency`,
+  and endpoint binding wrappers; `Tool.dependencies` now returns resources.
+  See [the archived context migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/context-migration.md) for replacements and state ownership.
+
+- Define and enforce Google-style source docstrings, and normalize tool
+  docstrings before including them in agent prompts.
+
+## 0.1.1
+
+- Preserve concrete nested model types across in-memory tool handoffs while
+  keeping field projection, excluded fields, validation, and detached inputs.
+- Add optional companion extras and independent package release workflows.
+- Keep the core's runtime dependency set unchanged.

roboz-0.1.2a1/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.