contextsage 0.1.0__tar.gz

contextsage-0.1.0/.env.example

@@ -0,0 +1,16 @@
+# Copy to .env and fill in the API key(s) below. `.env` is gitignored so
+# your key is never committed. The bundled examples use the
+# experientiallabs.ai OpenAI-compatible endpoint by default (see
+# examples/_llm.py) and only require EXPLABS_API_KEY.
+
+# Required for running examples/*.py
+EXPLABS_API_KEY=
+# Optional overrides (defaults shown)
+# EXPLABS_BASE_URL=https://api.experientiallabs.ai/v1
+# EXPLABS_MODEL=gpt-5.6-luna
+
+# Example: OpenAI (only needed if you swap a real OpenAI model in yourself)
+OPENAI_API_KEY=
+
+# Example: Anthropic
+ANTHROPIC_API_KEY=

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

@@ -0,0 +1,43 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install package with dev extras
+        run: pip install -e ".[dev]"
+
+      - name: Lint (ruff check)
+        run: ruff check src tests examples
+
+      - name: Format check (ruff format)
+        run: ruff format --check src tests examples
+
+      - name: Type check (pyrefly)
+        run: pyrefly check
+
+      - name: Test (pytest)
+        run: pytest tests -q
+
+      - name: Build docs (mkdocs --strict)
+        run: mkdocs build --strict
+
+      - name: Build package
+        run: pip install build && python -m build

contextsage-0.1.0/.gitignore

@@ -0,0 +1,20 @@
+.venv/
+venv/
+__pycache__/
+*.pyc
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.pyrefly_cache/
+site/
+node_modules/
+package.json
+package-lock.json
+.env
+uv.lock.bak
+*.log
+.coverage
+htmlcov/

contextsage-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,28 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.0
+    hooks:
+      - id: ruff
+        name: ruff check
+        args: [--fix]
+        files: ^(src|tests|examples)/
+      - id: ruff-format
+        name: ruff format
+        files: ^(src|tests|examples)/
+
+  - repo: local
+    hooks:
+      - id: pyrefly
+        name: pyrefly check
+        entry: pyrefly check
+        language: system
+        pass_filenames: false
+        types: [python]
+
+      - id: pytest
+        name: pytest
+        entry: pytest tests -q
+        language: system
+        pass_filenames: false
+        types: [python]
+        stages: [pre-push]

contextsage-0.1.0/ARCHITECTURE_INTERNALS.md

@@ -0,0 +1,192 @@
+# Architecture internals
+
+> **Internal engineering artifact.** This is a guided tour of ContextSage's
+> internal pipeline stages/classes, kept for contributors and maintainers
+> debugging summarization behavior. It is intentionally **not** part of the
+> published documentation site (`docs/`) — per the project's design
+> principle, users of `IntelligentSummarizationMiddleware` should never
+> need to know about `ContextUnit`, engines, or any of the internals below
+> to use the package. See [`docs/architecture.md`](docs/architecture.md)
+> for the user-facing architecture overview, and
+> [`docs/api-reference.md`](docs/api-reference.md) for the supported
+> public surface.
+
+This page is a guided tour of ContextSage's internal pipeline stages. These
+classes are implementation details (see the module docstrings, or
+`docs/api-reference.md`) but are documented for contributors and anyone
+debugging summarization behavior.
+
+## `ContextObserver`
+
+`contextsage.context.observer.ContextObserver` — the entry point. Counts
+tokens for the full incoming message list and produces an observation used
+by the budget analyzer; this is the cheapest possible pre-check so the
+expensive pipeline stages below only run when actually needed.
+
+## `BudgetAnalyzer`
+
+`contextsage.budget.analyzer.BudgetAnalyzer` implements an explicit,
+inspectable budget model:
+
+```
+maximum_context_tokens
+reserved_output_tokens
+system_tokens
+tool_schema_tokens
+current_input_tokens
+safety_margin_tokens
+available_input_tokens
+overflow_tokens
+```
+
+`infer_max_context_tokens(model)` looks up known context-window sizes for
+common providers/models, falling back to a conservative default when the
+model is unrecognized.
+
+## `ContextDecomposer`
+
+`contextsage.context.decomposition.ContextDecomposer` converts a heterogeneous
+message list into a flat list of `ContextUnit`s. It never
+treats one message as one content type:
+
+1. Fenced code blocks (`` ``` ``) are extracted as `CODE` regions.
+2. Embedded JSON values inside the remaining text are located with
+   `json.JSONDecoder.raw_decode`, which can find a JSON value starting at a
+   given index without needing to pre-guess where it ends.
+3. Remaining text is segmented into contiguous log-like vs. plain-text runs.
+
+## `StructuralSignalDetector`
+
+`contextsage.classification.signals.StructuralSignalDetector`
+assigns a `RegionKind` (or custom string kind — see below) and a confidence
+score to each unit, plus lightweight `ContentSignals` (identifiers found,
+whether an error/severity marker is present, table-likeness, etc.).
+Detection is conservative by design: e.g. log-line detection requires a
+leading timestamp pattern, so unlabeled plain text is never misclassified
+as a log purely because it contains the word "error".
+
+Kind-detection itself is delegated to a pluggable
+`contextsage.parsers.ParserRegistry` — an ordered collection of
+`ContentParser` implementations, tried in turn, first non-`None` result
+wins. The built-in registry (`default_registry()`) contains:
+
+1. `JSONParser` / `TableParser` — the most structurally unambiguous, so
+   they run first.
+2. `CodeParser` — fenced code blocks are trusted directly; a stated
+   language tag or a line-shape heuristic match is then *validated/refined*
+   with real `tree-sitter` parsing (a core dependency), never blind-guessed.
+3. `LogParser` / `ErrorParser` — anchored to the public ELK/Logstash "grok"
+   pattern vocabulary (`contextsage.parsers.grok_patterns`) rather than ad hoc
+   regexes; `ErrorParser` runs last since it deliberately overlaps with
+   ERROR-severity log lines.
+
+Every built-in parser's default patterns/thresholds are overridable via
+constructor keyword arguments (e.g. `LogParser(timestamp_pattern=...)`),
+and a fully custom `ParserRegistry` can be passed to
+`StructuralSignalDetector(registry=...)` — an internal-but-supported
+extension point, not a public plugin-registration API.
+
+## `ImportanceEngine`
+
+`contextsage.importance.engine.ImportanceEngine` computes a
+composite, bounded `[0, 1]` importance score per unit from independent
+signals — recency, user corrections, active constraints, decision language,
+error severity, identifiers (especially identifiers co-occurring with an
+error), and repetition-group membership. Every contribution is recorded in
+a `reasons` tuple so behavior is auditable and testable, not an opaque
+score.
+
+## `RelationshipEngine`
+
+`contextsage.relationships.engine.RelationshipEngine`
+detects `Relationship`s between units: `CONTRADICTS` (same key, conflicting
+values, e.g. two RAG sources disagreeing), `CORRECTED_BY` (a user
+correction referencing an earlier value), and tool-call pairing via
+`pair_tool_calls` (an `AIMessage`'s `tool_calls` matched to their
+`ToolMessage` results by `tool_call_id`), which the planner and validator
+use to keep AI-tool-call / tool-result pairs intact together.
+
+## `PreservationEngine`
+
+`contextsage.preservation.engine.PreservationEngine` converts
+importance + relationships into an explicit `PreservationLevel`
+(`MUST_PRESERVE`, `SHOULD_PRESERVE`, `COMPRESSIBLE`, `REDUNDANT`,
+`SAFE_TO_DROP`) per unit, and extracts concrete literal
+`must_preserve_facts` (identifiers, correction referents, constraint
+sentences) that `SummaryValidator` later checks the produced summary text
+for. Its thresholds are tunable via the `policy` constructor argument
+(`"balanced"` / `"maximum_preservation"` / `"maximum_compression"`) — see
+[`docs/configuration.md`](docs/configuration.md#policies). Certain reasons (user
+correction, contradiction participant, identifier-in-error-context) are
+*always* `MUST_PRESERVE` regardless of policy, because they are
+structurally important, not just numerically important.
+
+## `SummarizationPlanner`
+
+`contextsage.planning.planner.SummarizationPlanner` is the
+core intelligence: given classified units, it decides which units become
+`transform_deterministic` targets (structured/log/table content with a
+compressible/redundant preservation level), which are routed to
+`semantic_summarize` (left for the LLM), and which are `preserve_untouched`
+(must/should-preserve content, or content belonging to a protected
+message).
+
+## `ContextTransformationEngine`
+
+`contextsage.transformation.engine.ContextTransformationEngine`
+applies per-kind deterministic transformers
+(`contextsage.transformation.logs.reduce_log_block` for repetitive/verbose log
+blocks, `contextsage.transformation.structured.compact_json` for JSON) only to
+units the planner explicitly targeted. If a transformer raises
+`TransformationError`, or produces a result that isn't actually smaller, the
+unit is left completely untouched — deterministic transformation is always
+an optimization, never a requirement.
+
+## `LangGraphSummarizationAdapter`
+
+`contextsage.integrations.langgraph.adapter.LangGraphSummarizationAdapter`
+wraps LangChain's `SummarizationMiddleware` directly — it
+does not fork it or reimplement LLM summarization. It configures the
+wrapped middleware with an always-eligible trigger (ContextSage has already
+decided summarization is required upstream) and the user's `keep`
+parameter, then invokes its `before_model`/`abefore_model` hooks against
+the prepared (post-transformation) message list.
+
+## `SummaryValidator`
+
+`contextsage.validation.validator.SummaryValidator` checks
+the produced summary text for every literal must-preserve fact, for tool
+call/result pairing integrity, and for contradiction survival (both
+conflicting values must be simultaneously discoverable — a summary that
+silently drops both sides of a contradiction, or collapses to just one
+side, fails validation just as surely as one that fabricates false
+certainty).
+
+## `RecoveryManager`
+
+`contextsage.recovery.manager.RecoveryManager` implements
+the staged recovery process: on validation failure, it restates missing
+facts in an appended message without re-invoking the LLM; on a hard
+summarization failure (timeout, malformed response, rate limit), it falls
+back to a deterministic trim of the most recent `keep` messages with a
+preserved-facts message prepended, and never silently discards
+`MUST_PRESERVE` content.
+
+## `LineageManager`
+
+`contextsage.lineage.manager.LineageManager` records a
+`SummaryLineage` per operation (source unit/message IDs, generation number,
+token counts, compression ratio, validation/recovery/fallback status) and
+`find_prior_summary_ids` walks prior `RemoveMessage`/summary markers so a
+summary-of-a-summary retains lineage back to its original sources, rather
+than degrading silently across repeated summarizations.
+
+## `ObservabilityHook`
+
+`contextsage.observability.events.ObservabilityHook` is the
+structured-events interface. `LoggingObservabilityHook` (default) logs a
+`SummarizationEvent` per operation at `INFO` level — trigger reason, token
+counts, selected targets, compression ratio, validation/recovery/fallback
+status, latency — and never logs raw message content. `NullObservabilityHook`
+disables this. Supply your own `ObservabilityHook` implementation to forward
+events to your own telemetry system.

contextsage-0.1.0/CHANGELOG.md

@@ -0,0 +1,40 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-09-23
+
+### Added
+
+- Initial public release of `contextsage`.
+- `IntelligentSummarizationMiddleware`: a production-grade, information-aware
+  replacement for LangGraph's `SummarizationMiddleware`.
+- Heterogeneous context decomposition (`context/decomposition.py`) — a
+  single message is split into independently-classified regions instead of
+  being treated as one content type.
+- Pluggable structural content parsers (JSON, table, code, log, error) via
+  `ContentParser` / `ParserRegistry`, with a public `parsers` constructor
+  parameter for domain-specific extensions (see `examples/sql_parser.py`).
+- Budget analysis, importance scoring, relationship/dependency tracking,
+  preservation classification, planning, and deterministic transformation
+  engines feeding a single LangGraph summarization call.
+- Post-summarization validation and staged recovery on summarization
+  failure.
+- Summary lineage tracking and optional `langgraph-xai` provenance
+  integration.
+- Structured observability events via a pluggable `ObservabilityHook`.
+- Full parameter overridability: every internal default (token budget
+  fractions, encoding name/timeout/cache size, classification patterns,
+  parser patterns) is exposed through `IntelligentSummarizationMiddleware`'s
+  public constructor — no subclassing required for common customization.
+- Documentation site (`mkdocs`), requirements traceability matrix, and a
+  runnable example suite (`examples/`) exercising every constructor
+  parameter against a real LLM.
+
+[Unreleased]: https://github.com/smuniharish/contextsage/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/smuniharish/contextsage/releases/tag/v0.1.0

contextsage-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,63 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in
+our community a harassment-free experience for everyone, regardless of
+age, body size, visible or invisible disability, ethnicity, sex
+characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open,
+welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our
+  mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior that they deem
+inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces (issues, pull
+requests, discussions) and also applies when an individual is officially
+representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may
+be reported to the maintainer listed in `pyproject.toml` (`authors`). All
+complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the
+[Contributor Covenant](https://www.contributor-covenant.org), version 2.1,
+available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.

contextsage-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# Contributing to ContextSage
+
+Thanks for your interest in contributing! ContextSage is a focused,
+production-grade package — see [`REQUIREMENTS_TRACEABILITY.md`](REQUIREMENTS_TRACEABILITY.md)
+for the architectural contract every change is expected to respect (in
+particular: no public plugin architecture, no forced heavyweight
+dependencies, and no new top-level product surface beyond
+`IntelligentSummarizationMiddleware`), and
+[`ARCHITECTURE_INTERNALS.md`](ARCHITECTURE_INTERNALS.md) for a guided tour
+of the internal pipeline engines (`ContextDecomposer`, `ImportanceEngine`,
+`SummarizationPlanner`, etc.) if you're extending or debugging one of them.
+
+## Getting started
+
+```bash
+git clone https://github.com/smuniharish/contextsage.git
+cd contextsage
+pip install -e ".[dev,examples]"
+pre-commit install
+```
+
+## Development workflow
+
+Before opening a pull request, run the same checks CI runs
+(`.github/workflows/ci.yml`):
+
+```bash
+ruff check src tests examples
+ruff format --check src tests examples
+pyrefly check
+pytest tests -q
+mkdocs build --strict
+```
+
+`pre-commit run --all-files` runs the lint/format checks automatically on
+every commit once installed.
+
+## Making changes
+
+- **Tests are required** for any behavioral change. Unit tests live in
+  `tests/unit/` (one file per engine), integration tests in
+  `tests/integration/`, and failure-injection tests in `tests/failure/`.
+- **Public API changes** (anything on `IntelligentSummarizationMiddleware`'s
+  constructor) must update `docs/api-reference.md` and
+  `docs/configuration.md`, and should extend `examples/all_parameters.py`
+  to exercise the new parameter against a real LLM call.
+- **New default values or hardcoded patterns/thresholds** should be
+  exposed as overridable constructor keyword arguments, following the
+  `DEFAULT_*` module-constant convention used throughout `src/contextsage/`.
+- Keep [`REQUIREMENTS_TRACEABILITY.md`](REQUIREMENTS_TRACEABILITY.md) in
+  sync when a change affects a numbered requirement's implementation or
+  test coverage.
+- Update `CHANGELOG.md` under `[Unreleased]` for any user-facing change.
+
+## Reporting bugs / requesting features
+
+Open a GitHub issue with a minimal reproduction (a message list and the
+`IntelligentSummarizationMiddleware` constructor arguments used) where
+possible.
+
+## Security issues
+
+Do not open a public issue for a security vulnerability — see
+[SECURITY.md](SECURITY.md).
+
+## Code of conduct
+
+This project follows the [Code of Conduct](CODE_OF_CONDUCT.md).

contextsage-0.1.0/LICENSE

@@ -0,0 +1,190 @@
+                                 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
+
+   Copyright 2026 S MUNI HARISH
+
+   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.