streamdouble 0.1.0__tar.gz

streamdouble-0.1.0/.gitattributes

@@ -0,0 +1,9 @@
+# Normalise text to LF in the repository. CI runs the same test suite on
+# Windows and Linux, and the golden-file test pins exact bytes, so line-ending
+# drift between platforms would show up as a spurious failure.
+* text=auto eol=lf
+
+# Audio fixtures are binary and must never be touched. A single CRLF
+# substitution inside a WAV corrupts the audio silently -- it still loads, it
+# just sounds wrong, which is the hardest possible way to find this bug.
+*.wav binary

streamdouble-0.1.0/.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,39 @@
+name: Bug report
+description: Something in streamdouble itself is wrong
+labels: ["bug"]
+body:
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: How to reproduce
+      description: >
+        The exact command, please. If it involves network impairment, include
+        `--chaos-seed` — impairments are seeded precisely so a failing run can be
+        replayed, and without the seed we are guessing.
+      render: shell
+    validations:
+      required: true
+
+  - type: textarea
+    id: output
+    attributes:
+      label: Output
+      description: >
+        `--json` output is ideal. It carries the pacing statistics, which say
+        whether the timing figures can be trusted at all.
+      render: shell
+
+  - type: input
+    id: environment
+    attributes:
+      label: OS and Python version
+      placeholder: "Windows 11, Python 3.12"
+    validations:
+      required: true

streamdouble-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Is my agent any good?
+    url: https://github.com/shaswat28/streamdouble#how-this-compares
+    about: >
+      streamdouble tests the transport seam, not what your agent says. For
+      conversation quality, personas or transcript scoring, the comparison table
+      points at tools that do that well.

streamdouble-0.1.0/.github/ISSUE_TEMPLATE/protocol-difference.yml

@@ -0,0 +1,47 @@
+name: Protocol difference
+description: streamdouble behaves differently from real Twilio
+labels: ["protocol"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This is the most valuable report this project can receive.
+
+        streamdouble claims an agent cannot tell it from Twilio, and that claim
+        is only as good as our reading of a specification that does not cover
+        everything. Several behaviours are inferences, marked as such in the
+        code. If you have watched a real call do something we do not, we want to
+        know.
+
+  - type: textarea
+    id: real-behaviour
+    attributes:
+      label: What real Twilio does
+      description: >
+        A frame capture, a log line, a screenshot of Twilio's debugger —
+        anything showing the real behaviour beats a description, because what
+        the real thing does is the entire question. If you cannot share a
+        capture, describe what you saw and how you saw it; that is still useful.
+    validations:
+      required: true
+
+  - type: textarea
+    id: streamdouble-behaviour
+    attributes:
+      label: What streamdouble does instead
+    validations:
+      required: true
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: What breaks because of the difference
+      description: >
+        For example "our agent hangs waiting for a mark" or "our VAD never
+        fires". This tells us whether the difference is cosmetic or load-bearing.
+
+  - type: input
+    id: version
+    attributes:
+      label: streamdouble version
+      placeholder: "0.1.0"

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

@@ -0,0 +1,52 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: py${{ matrix.python }} on ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        # Windows and Linux both run the full matrix because the golden-file
+        # test pins exact bytes, and that claim is only worth anything if it
+        # holds across platforms. 3.13 matters specifically: audioop was
+        # removed there, so it is the run that proves the codec stands on its
+        # own rather than leaning on the stdlib reference.
+        os: [ubuntu-latest, windows-latest]
+        python: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+          cache: pip
+
+      - name: Install
+        run: python -m pip install --upgrade pip && python -m pip install -e ".[dev]"
+
+      - name: Lint
+        run: python -m ruff check .
+
+      - name: Test
+        run: python -m pytest -q
+
+      - name: Fixtures regenerate identically
+        # The golden file is only meaningful if the fixtures it pins are
+        # reproducible. Regenerating and diffing proves the generator is
+        # deterministic across platforms and numpy versions, rather than
+        # merely deterministic on the machine that first ran it.
+        run: |
+          python fixtures/make_fixtures.py
+          git diff --exit-code -- fixtures/

streamdouble-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,68 @@
+name: Release
+
+# Deliberately manual. There is no push or tag trigger, so nothing publishes by
+# accident while the project is still private: a release happens because someone
+# went to the Actions tab and asked for one.
+#
+# `publish: false` is the default, so the ordinary run builds the artifacts,
+# validates them, and installs the wheel into a clean environment without
+# uploading anything. That is worth doing on its own -- it is the check that
+# caught PyYAML being used but never declared, which passed every local test and
+# failed on a machine that did not already have it.
+on:
+  workflow_dispatch:
+    inputs:
+      publish:
+        description: "Actually upload to PyPI (leave false to build and verify only)"
+        type: boolean
+        default: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build
+        run: |
+          python -m pip install --upgrade pip build twine
+          python -m build
+
+      - name: Validate metadata
+        run: python -m twine check dist/*
+
+      - name: Install the wheel into a clean environment
+        # The point is what is *not* here: no dev extras, no editable install,
+        # nothing the repository checkout would otherwise provide. If a runtime
+        # dependency is undeclared, this is where it shows.
+        run: |
+          python -m venv /tmp/clean
+          /tmp/clean/bin/python -m pip install dist/*.whl
+          /tmp/clean/bin/streamdouble --version
+          /tmp/clean/bin/python -c "
+          from streamdouble import audio, chaos, metrics, protocol, scenario
+          print('imports ok')
+          print(len(audio.wav_to_ulaw_frames('fixtures/speech_8k.wav')), 'frames')
+          "
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        if: ${{ inputs.publish }}
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+        run: |
+          if [ -z "$TWINE_PASSWORD" ]; then
+            echo "PYPI_API_TOKEN is not set in this repository's secrets." >&2
+            echo "Add it under Settings > Secrets and variables > Actions." >&2
+            exit 1
+          fi
+          python -m twine upload dist/*

streamdouble-0.1.0/.gitignore

@@ -0,0 +1,16 @@
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+*.wav
+!fixtures/*.wav
+!tests/data/*.wav
+.DS_Store
+fixtures/speech/

streamdouble-0.1.0/CLAUDE.md

@@ -0,0 +1,97 @@
+# CLAUDE.md
+
+Guidance for Claude Code when working in this repository.
+
+## The directory name is wrong
+
+This folder is called `dialtone`, but the project is **`streamdouble`**. The
+package was renamed on 2026-09-10 — `dialtone` turned out to be an active
+package on PyPI. The folder kept its old name; nothing else did.
+
+## Read PLAN.md first
+
+`PLAN.md` is the authority on what this project is, how it is built, and where
+it currently stands. Its **Progress** section is written as a handover: what
+exists, what each review gate found, what is owed, and what to do next. Start
+there rather than inferring state from the code.
+
+## How work proceeds here
+
+The project is built in phases, with a **mandatory review gate between each
+one** (`/code-review high`, plus `/security-review` at gate 4). Gates are not
+optional and are not to be skipped or deferred — every gate so far has found
+real bugs, including two that were introduced by the previous gate's own fixes.
+
+When a gate finds something, fix it *and* write a regression test that fails
+against the old behaviour. `tests/test_review_gate_1.py` and
+`tests/test_review_gate_2.py` follow that pattern.
+
+## What this project is unusually strict about
+
+These are not stylistic preferences; each one exists because of a specific bug
+that reached the repo.
+
+- **Verify protocol details against the live Twilio docs, never from memory.**
+  The original plan's protocol table was wrong in three ways. Cite the source in
+  a docstring.
+- **`None` is not zero.** An agent that never spoke has
+  `time_to_first_audio = None`. Rendering that as "0 ms" turns the worst outcome
+  into the best one on screen.
+- **Measurement honesty over clean-looking numbers.** Pacing lateness is
+  reported alongside the latency it could have distorted. A latency tool that
+  reports wrong latency is worse than no tool, because people trust it.
+- **Warnings are errors** (`filterwarnings = ["error"]`). Several real bugs
+  surfaced first as warnings. The few ignores are third-party and each is
+  annotated with why.
+- **The golden file pins exact bytes.** Regenerate it (`UPDATE_GOLDEN=1`) only
+  deliberately, with a reason in the commit message. Nothing feeding it may
+  depend on `np.random` — NumPy does not guarantee `Generator` streams across
+  builds, machines or CPUs.
+- **`protocol.py` and `audio.py` stay pure.** No network, no clock. If a bug
+  there needs a WebSocket to reproduce, the layering is wrong.
+- **Time is `time.perf_counter`.** It must be monotonic — an NTP step mid-call
+  would otherwise produce a negative latency reported with a straight face —
+  *and* high resolution. `time.monotonic` looks right and is not: on Windows it
+  is `GetTickCount64` at 15.625 ms, coarser than the 20 ms frame being measured.
+  Gate 3 found it quantising every latency and turning the pacer's lateness
+  statistics into a readout of the clock.
+
+## Commands
+
+```bash
+pip install -e ".[dev]"
+pytest                      # the session tests use a real socket
+ruff check .
+python fixtures/make_fixtures.py    # only if a fixture definition changed
+```
+
+Run the example agent and call it:
+
+```bash
+python examples/echo_agent.py --port 8000
+streamdouble call ws://localhost:8000/media-stream --audio fixtures/speech_8k.wav --out reply.wav
+```
+
+The echo agent takes query parameters to misbehave on purpose: `mode=silent`,
+`delay_ms=`, `hangup_after=`, `garbage_after=`, `clear_after=`.
+
+## Testing against a real agent
+
+The example agent is enough for most work, but it is *our* code, written from
+the same reading of the Twilio docs as `protocol.py` -- a shared misreading
+would leave every test green. Validating against an implementation we did not
+write is what catches that, and it has already found things the example agent
+structurally could not.
+
+Point streamdouble at the agent's own `/media-stream`. Agents commonly
+authenticate on `start.customParameters` rather than the URL, so
+`--param key=...` is usually what is needed.
+
+**Disable whatever the agent touches on hangup first** -- CRM pushes, webhooks,
+billing, notifications. A simulated call is a real call to everything downstream
+of the socket. The first time this was done for real, a completed test call
+wrote records to a live CRM for a made-up phone number.
+
+Two things a real agent taught us that the example agent could not, both in
+PLAN.md: agents batch outbound audio into frames of roughly 8000 bytes rather
+than 160, and mark echo is load-bearing for hangup.

streamdouble-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,104 @@
+# Contributing
+
+The most valuable contribution to this project is **telling us where the
+simulation is wrong.**
+
+`streamdouble` claims that an agent cannot tell it from Twilio. That claim is
+only as good as our reading of the protocol, and the Twilio documentation does
+not cover everything — several behaviours here are inferences, marked as such in
+the code. If you have watched a real Twilio call do something this tool does
+not, that is the bug report we most want.
+
+## Reporting a protocol difference
+
+Include what Twilio actually did. A frame capture, a log line, a screenshot of
+Twilio's debugger — anything that shows real behaviour beats a description of
+it, because the whole question is what the real thing does.
+
+If you cannot share a capture, say what you observed and how you observed it.
+"Our agent works on real calls but hangs against streamdouble" is a useful
+report even without a capture; it tells us where to look.
+
+Known inferences, each documented at the code that makes them:
+
+- **Packet loss** is modelled as audio Twilio never received, so a lost frame is
+  never sent and `media.timestamp` jumps. Twilio might instead substitute
+  silence. See `chaos.py`.
+- **Mark echo timing** is derived from a playback clock we maintain. Twilio's
+  real timing may differ under load. See `session.py`.
+- **Frame size**: we always send 160 bytes. Twilio does too, as far as we know,
+  but this is not documented as a guarantee. See `audio.py`.
+
+## Working on the code
+
+```bash
+pip install -e ".[dev]"
+pytest
+ruff check .
+```
+
+The session tests start a real server on a real socket; they are slower than the
+rest and that is deliberate — the lifecycle bugs worth catching do not exist
+without one.
+
+### Things this project is strict about
+
+Each of these exists because of a specific bug that reached the repository, and
+each is written up in `PLAN.md` with the story attached.
+
+- **Verify protocol details against the live Twilio docs, never from memory.**
+  The original plan's protocol table was wrong in three ways.
+- **`None` is not zero.** An agent that never spoke has no latency measurement.
+  Rendering that as `0 ms` turns the worst outcome into the best one.
+- **Measurement honesty over clean-looking numbers.** Pacing lateness is
+  reported alongside the latency it could have distorted. A latency tool that
+  reports wrong latency is worse than no tool, because people trust it.
+- **Time is `time.perf_counter`.** `time.monotonic` is `GetTickCount64` on
+  Windows, at 15.6 ms — coarser than the frame being measured. This was found
+  quantising every number the tool produced.
+- **Warnings are errors.** The few ignores are third-party and each is annotated
+  with why.
+- **`protocol.py` and `audio.py` stay pure.** No network, no clock.
+
+### Tests
+
+A fix needs a test that fails against the old behaviour. If the bug was in
+timing or concurrency, prefer a test that reproduces the condition over one that
+asserts on structure — `tests/test_review_gate_*.py` are written that way, and
+each names the failure it prevents.
+
+Property tests and mutation checks are welcome. There is a mutation-testing
+habit in this repository rather than a tool: deliberately break something, and
+confirm a test written for it fails. Several fixes here have been verified that
+way, and one of them found that a fix had introduced a new bug.
+
+## Adding a scenario
+
+Scenarios in `scenarios/` are examples as much as tests. Keep clips small, and
+write the comments for someone who has not read the source.
+
+If the scenario depends on the agent *understanding* the caller — barge-in,
+anything answering a question — it needs real speech. Use
+`python fixtures/make_speech.py`, which synthesises transcribable clips from the
+OS's own TTS into the gitignored `fixtures/speech/`. The committed synthetic
+fixtures are speech-like and no transcription service will turn them into words,
+so a scenario driven by one fails for reasons that have nothing to do with the
+agent under test.
+
+## What is out of scope
+
+Stated to save you the work, not to be unwelcoming:
+
+- LLM-as-judge or transcript scoring
+- Multi-turn conversation simulation
+- A web UI or dashboard
+- Being a voice agent framework
+
+The [comparison table](README.md#how-this-compares) says who does those well.
+`streamdouble` does one thing, and the narrowness is the point.
+
+## Not affiliated with Twilio
+
+This project is not affiliated with, endorsed by, or sponsored by Twilio. It
+simulates the publicly documented Twilio Media Streams protocol. Please do not
+contribute anything obtained under an NDA or from a private beta.

streamdouble-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 2026 Shaswat Sharma
+
+   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.