convilyn-edge 0.1.0b3__tar.gz

convilyn_edge-0.1.0b3/.gitignore

@@ -0,0 +1,18 @@
+# Build / packaging
+/dist/
+/build/
+*.egg-info/
+
+# Virtual envs
+.venv/
+venv/
+
+# Test / coverage artifacts
+.pytest_cache/
+.coverage
+coverage.xml
+htmlcov/
+
+# Byte-compiled
+__pycache__/
+*.py[cod]

convilyn_edge-0.1.0b3/CHANGELOG.md

@@ -0,0 +1,111 @@
+# Changelog
+
+All notable changes to `convilyn-edge` are documented here. The SDK's public
+surface follows Semantic Versioning; pre-1.0 minor/patch may still adjust
+surface under the alpha label.
+
+## 0.1.0b3 — unreleased (PR4: device simulator + CLI)
+
+Drive a workflow with no hardware, and scaffold new adapters/workflows.
+
+### Added
+
+- **`convilyn_edge.simulator`** — `SimulatedSource`, the first concrete
+  `EventSource` implementation: replay a JSON `Scenario` (device + ordered
+  events, with per-event `delay_ms` / `repeat`) as an `EventEnvelope` stream. The
+  moat-safe simulator half of the SDK; zero dependencies.
+- **The `convilyn-edge` CLI** (stdlib `argparse`, zero deps):
+  - `simulate <scenario.json> [--no-delay]` — replay a scenario, printing each
+    envelope as a wire-JSON line (the v0.1 device-plane dev-run; `--no-delay`
+    gives a deterministic replay).
+  - `init adapter|workflow <name> [--path DIR]` — scaffold a conventional
+    adapter / workflow skeleton (reference §十四).
+
+### Changed
+
+- Retired the POC `ainalyn_edge_runner` sample-input generators
+  (`make_samples.py`, `make_demo_jds.py`) — superseded by the `convilyn-edge`
+  simulator + scaffolds.
+
+### Deferred to v0.2
+
+- `dev run` / `trace replay` — they need the workflow executor + a trace-export
+  format that are out of v0.1 scope. `simulate --no-delay` is the deterministic
+  replay subset for now.
+
+## 0.1.0b2 — unreleased (PR3: offline queue + Event Envelope emitter)
+
+Offline-first buffering: the device keeps working when the cloud is unreachable,
+and flushes exactly once when it returns.
+
+### Added
+
+- **`convilyn_edge.offline`** — zero runtime dependencies:
+  - `DurableQueue` — a JSONL-backed, **idempotent** FIFO queue: a record whose
+    apply-once key is already queued is dropped, so a re-queue never duplicates a
+    pending item. `pending` / `enqueue` / `clear` / `replace` (atomic rewrite).
+  - `derive_idempotency_key` — the content-addressed apply-once key, a byte-exact
+    mirror of the server reconcile contract (device clock excluded), so the
+    server re-derives the same key and a re-flush is a no-op.
+  - `EventEmitter` + `EventSink` — emit an `EventEnvelope` to an injected sink;
+    when the sink is offline the envelope is buffered durably (keyed by its unique
+    `event_id`) instead of dropped, and `flush()` drains the buffer apply-once.
+    Reuses the `traceparent`-style correlation convention; the transport is
+    injected, so the package takes on no HTTP/MQTT dependency.
+
+### Changed
+
+- The POC `ainalyn_edge_runner` offline capture queue (`queue.jsonl`) now uses the
+  productized `DurableQueue` (idempotent enqueue; same file, same replay UX).
+
+## 0.1.0b1 — unreleased (PR2: client_compute keystone)
+
+The on-device extractor keystone — `convilyn-edge` now **confirms-and-consumes**
+the frozen `client_compute` interrupt contract v1, so a cloud workflow can
+delegate the extractor role to the device and the device answers with grounded
+anchors (the server re-grounds before trusting them).
+
+### Added
+
+- **`convilyn_edge.clientcompute`** — the client-compute round-trip, zero runtime
+  dependencies:
+  - `contract` — parse the frozen v1 interrupt payload (`ClientComputeRequest`,
+    `AnchorsContract`), `build_resume_answer`, and `ground_anchors` — the device
+    self-verify that mirrors the server's substring re-grounding (verbatim
+    substring or the `"Not specified"` sentinel; per-value + total caps enforced).
+  - `engine` — `LocalExtractor` Protocol + `HttpLocalExtractor` (Ollama and
+    OpenAI-compatible wires over stdlib `urllib`; transport injectable for tests).
+  - `operator` — `EdgeModelOperator`, an `edge`-placement `ModelOperator` that
+    runs the local model + grounds and returns a typed `ModelResult`.
+  - `bridge` — `ClientComputeBridge`, which drives one interrupt to resume via
+    narrow injected Protocols (`GoalClientPort`, `FileTextResolver`) — the
+    consumer SDK is injected, never imported (the core stays dependency-free).
+
+### Changed
+
+- Retired the POC `docs/research/poc/ainalyn_edge_runner/local_llm.py` (its
+  extract + self-verify logic is absorbed here); the POC runner now consumes the
+  productized package.
+
+## 0.1.0b0 — unreleased (PR1: SPI scaffold)
+
+Initial scaffold of the Edge AI Workflow SDK — the SPI only, zero runtime
+dependencies.
+
+### Added
+
+- **Event Envelope** (`convilyn_edge.envelope`): `EventEnvelope`,
+  `EventSourceRef`, `Correlation`, and the `new_envelope(...)` factory, with
+  `to_wire()` / `from_wire()` camelCase serialization. Reference-architecture §四.
+- **`Result[T, E]`** (`convilyn_edge.result`): an `Ok` / `Err` tagged union for
+  exception-free, statically-narrowable fallible outcomes.
+- **The 7-primitive SPI** (`convilyn_edge.spi`): `EventSource`, `Normalizer`,
+  `StateProvider`, `DeterministicOperator`, `ModelOperator`, `HumanReview`,
+  `ActionSink` — typed Protocols + their frozen dataclasses. Reference §三.
+- Package scaffold: `src/` layout, `py.typed`, dynamic version, `dependencies = []`.
+
+### Notes
+
+- No implementations ship in PR1 — Protocols + data shapes only. The
+  `client_compute` `ModelOperator` (PR2), offline queue + emitter (PR3),
+  simulator + CLI (PR4), and the removable retail Solution Pack (PR5) follow.

convilyn_edge-0.1.0b3/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 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 accept (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 2026 CoreNovus contributors
+
+   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.

convilyn_edge-0.1.0b3/PKG-INFO

@@ -0,0 +1,194 @@
+Metadata-Version: 2.4
+Name: convilyn-edge
+Version: 0.1.0b3
+Summary: Convilyn Edge AI Workflow SDK — the 7-primitive Device Data Plane SPI for building auditable, offline-capable edge AI workflows
+Project-URL: Homepage, https://convilyn.corenovus.com
+Project-URL: Documentation, https://docs.convilyn.corenovus.com
+Project-URL: Issues, https://github.com/CoreNovus/convilyn-python/issues
+Project-URL: Repository, https://github.com/CoreNovus/convilyn-python
+Author-email: Convilyn <sdk@convilyn.corenovus.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai,convilyn,device,edge,iot,spi,workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Hardware
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.1.0; extra == 'dev'
+Requires-Dist: pytest>=7.0.0; extra == 'dev'
+Requires-Dist: ruff==0.15.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# convilyn-edge
+
+The **Convilyn Edge AI Workflow SDK** — the Device Data Plane + Edge Runtime SPI
+for building auditable, offline-capable edge/IoT AI workflows.
+
+> **Alpha (`0.1.0b3`).** v0.1 ships the seven typed SPI Protocols + the Event
+> Envelope + a `Result` type — with **zero runtime dependencies** — plus, landed
+> across the b1–b3 betas: the `client_compute` on-device model keystone
+> (`convilyn_edge.clientcompute`), the durable offline queue + emitter
+> (`convilyn_edge.offline`), the device simulator + `convilyn-edge` CLI
+> (`convilyn_edge.simulator` / `.cli`), and a capability `probe`. The removable
+> retail Solution Pack ships as its own package
+> (`convilyn-solution-retail-cashier`). Each section below documents the module
+> as it exists in this release.
+
+## What this is (and is not)
+
+Convilyn splits an edge AI product into three planes:
+
+| Plane | Home |
+|---|---|
+| **AI Workflow Plane** — SOP lookup, explain, re-ground, HITL, escalate, gated tools + the 7 deterministic hard zones | `backend-api` (the Convilyn cloud) |
+| **Device Data Plane + Edge Runtime + adapter/provider SPI** | **this package (`convilyn-edge`)** |
+| **Vertical logic** — the barcode rules, POS state, workflows | a *removable* Solution Pack (`solution-retail-cashier`) |
+
+Convilyn ships the **SPI + a simulator + reference adapters only** — never
+hardware drivers or action connectors. Real OPOS/.NET, Zebra/Kotlin, serial /
+MQTT / camera adapters and any device actuation beyond R0/R1 are integrator /
+community work. That boundary is the moat and the anti-divergence guarantee.
+
+**Build once, run anywhere.** Workflows are authored in Convilyn's chat-driven
+**Builder** — a shared, client-agnostic capability in the AI Workflow Plane, *not*
+part of this SDK. Every client (web, desktop, or device) then *runs* that same
+compiled workflow (`uw_…`); the Edge SDK **consumes** workflows via its
+`ModelOperator` (cloud placement wraps the consumer SDK's `client.goals.run`; edge
+placement runs a local model), it never builds one.
+
+## The 7 primitives (`convilyn_edge.spi`)
+
+Each is one narrow Protocol — depend on the interface, not a runtime (DIP/ISP).
+
+| # | Primitive | Essence |
+|---|---|---|
+| 1 | `EventSource` | events enter the SDK → `AsyncIterator[EventEnvelope]` |
+| 2 | `Normalizer[Raw, Canonical]` | raw vendor payload → canonical event (`Result`, sync) |
+| 3 | `StateProvider[T]` | environment state at event time (`async`) |
+| 4 | `DeterministicOperator[In, Out]` | pure, **no-LLM** rules (`Result`, **sync**) |
+| 5 | `ModelOperator[In, Out]` | typed inference — `edge`/`cloud`/`auto` (**keystone**) |
+| 6 | `HumanReview` | structured human-in-the-loop → typed `ReviewOutcome` |
+| 7 | `ActionSink[In, Out]` | gated side effects, risk R0–R3 |
+
+Everything crosses the SDK inside one **`EventEnvelope`** (uniform id / schema
+version / correlation / ordering — the basis for dedup, replay, and audit).
+
+```python
+from convilyn_edge import new_envelope, EventSourceRef, Ok, Err
+
+env = new_envelope(
+    event_type="device.barcode.scan.received",
+    event_schema="convilyn://schemas/barcode-scan/v1",
+    source=EventSourceRef("scanner-8f-03", "opos-scanner", "0.3.1"),
+    data={"scanData": "4711234567890", "symbology": "EAN13"},
+)
+wire = env.to_wire()                    # camelCase JSON object
+assert EventEnvelope.from_wire(wire) == env
+```
+
+## Client-compute — the on-device keystone (`convilyn_edge.clientcompute`)
+
+When a cloud workflow routes the extractor role to the device, it pauses with a
+`client_compute` interrupt and hands the device a **content-free** delegation
+request (files by reference only). The device runs a local model over its **own**
+copy of the file and returns grounded anchors; the server re-grounds them before
+trusting them. `convilyn-edge` **confirms-and-consumes** that frozen contract:
+
+```python
+import os
+from convilyn import AsyncConvilyn
+from convilyn_edge.clientcompute import (
+    ClientComputeBridge, EdgeModelOperator, HttpLocalExtractor,
+)
+
+# A local inference server (Ollama / any OpenAI-compatible endpoint), chosen by env.
+operator = EdgeModelOperator(HttpLocalExtractor.from_env(os.environ))
+# `resolver.resolve(file_id) -> local text` — the device reads its OWN file copy.
+bridge = ClientComputeBridge(operator, resolver)
+
+async with AsyncConvilyn() as client:
+    job = await client.goals.wait(job_id)
+    # If the cloud delegated an extract step, fulfil it locally and resume:
+    updated = await bridge.handle_if_present(client.goals, job)
+```
+
+The consumer SDK is *injected* (a narrow `GoalClientPort` Protocol), never
+imported — so `convilyn-edge` itself stays dependency-free. Values that aren't a
+verbatim substring of the local source degrade to `"Not specified"` **on the
+device**, exactly as the server would degrade them — an ungrounded (possibly
+injected) string never crosses the boundary.
+
+## Offline-first (`convilyn_edge.offline`)
+
+The device keeps working when the cloud is unreachable — structured events buffer
+durably and flush exactly once on reconnect:
+
+```python
+from pathlib import Path
+from convilyn_edge.offline import DurableQueue, EventEmitter, event_key
+
+queue = DurableQueue(Path("edge-events.jsonl"), key_of=event_key)
+emitter = EventEmitter(sink, queue)          # sink: EventSink (your HTTP/MQTT transport)
+
+await emitter.emit(envelope)                 # delivered, or durably buffered if offline
+report = await emitter.flush()               # drain on reconnect; report.clean == True
+```
+
+Enqueue is **idempotent** (keyed by the envelope's unique `event_id`), and
+`derive_idempotency_key` reproduces the server's content-addressed reconcile key
+byte-for-byte — so a retried flush is a no-op, never a duplicate.
+
+## CLI — simulate with no hardware (`convilyn-edge`)
+
+A developer shouldn't need a real scanner to test a workflow. Replay a JSON
+scenario through the built-in simulator:
+
+```bash
+convilyn-edge simulate scenario.json --no-delay    # prints one wire-JSON envelope per event
+convilyn-edge init adapter zebra-datawedge         # scaffold a device adapter
+convilyn-edge init workflow cashier-guidance       # scaffold a workflow
+```
+
+A scenario declares a device and an ordered list of events (each with an optional
+`delay_ms` / `repeat`); `SimulatedSource` — the first concrete `EventSource` —
+replays it as an `EventEnvelope` stream. (`dev run` / `trace replay` land in v0.2
+with the workflow executor; `simulate --no-delay` is the deterministic replay.)
+
+## Design principles (enforced in code, not just docs)
+
+- **The device is never a second source of truth.** The server holds the 7 hard
+  zones and re-grounds every device value; the edge SPI inherits that contract.
+- **No LLM in `DeterministicOperator`** — a *sync* signature makes "no I/O, no
+  model" a type-level guarantee. Scenario rules live in a removable pack.
+- **One envelope, one `Result`, one observability convention.** No parallel
+  transports; no `if provider == ...`.
+
+## The litmus test
+
+> Delete the entire retail Solution Pack. Does the remaining SDK still let you
+> build another IoT AI workflow?
+
+If yes, this is a general SDK. v0.1 (PR6) turns that question into a committed CI
+lint.
+
+## Install
+
+```bash
+pip install --pre convilyn-edge
+```
+
+Python ≥ 3.10. Zero runtime dependencies. Runnable examples live in
+[`examples/`](./examples/) — start with `examples/simulate_barcode.py`.
+
+## License
+
+Apache-2.0.