kaos-web 0.1.0a1__tar.gz

kaos_web-0.1.0a1/.gitignore

@@ -0,0 +1,36 @@
+# Build / dist
+build/
+dist/
+*.egg-info/
+
+# Caches
+.benchmarks/
+.coverage
+.coverage.*
+.kaos-vfs/
+.kaos-vfs-*/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.ty_cache/
+.venv/
+__pycache__/
+coverage.xml
+htmlcov/
+*.pyc
+
+# OS / editor scratch
+.DS_Store
+Thumbs.db
+.idea/
+.vscode/
+
+# Secrets — never commit
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+*.p12
+*.pfx
+.kaos-credentials.json

kaos_web-0.1.0a1/CHANGELOG.md

@@ -0,0 +1,273 @@
+# Changelog
+
+All notable changes to `kaos-web` 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]
+
+### Security
+
+- **SSRF gate at every outbound URL/host site** (WEB5-001). Wires
+  ``kaos_core.security.validate_outbound_url`` (and the host-only
+  ``is_loopback`` / ``is_private_ip`` / ``is_metadata_service``
+  primitives) into every kaos-web fetch site so a misconfigured
+  caller — especially the HTTP-mode MCP server fronting multiple
+  agents — cannot reach link-local cloud-metadata services
+  (``169.254.169.254``), loopback, RFC1918 private networks, or
+  block-listed schemes (``file://``, ``javascript:``, ``data:``,
+  ``vbscript:``). New ``kaos_web.security`` module exposes
+  ``validate_url(url)`` and ``validate_host(host)`` thin wrappers
+  that translate ``UnsafeURLError`` into a new
+  ``UrlPolicyError(WebError)`` whose message includes the specific
+  policy field that fired plus the env var the operator can flip to
+  relax it. **Strict by default**: blocks private/loopback/metadata
+  and limits schemes to ``http``/``https``. Operators relax via
+  ``KAOS_SECURITY_BLOCK_PRIVATE_NETWORKS=0`` /
+  ``KAOS_SECURITY_BLOCK_LOOPBACK=0`` /
+  ``KAOS_SECURITY_BLOCK_METADATA_SERVICES=0`` /
+  ``KAOS_SECURITY_ALLOWED_HOSTS=["host","10.0.0.0/24",".example.com"]``.
+  Sites wired (4 URL gates + 12 host gates):
+  - URL: ``HttpClient._raw_fetch``, ``BrowserClient.fetch`` /
+    ``screenshot`` / ``evaluate``, ``analyze_headers``,
+    ``ExtractOrgTool.execute``.
+  - Host: ``probe_port`` / ``probe_ports`` / ``probe_banner`` /
+    ``probe_banners``, ``inspect_tls``, ``probe_dns`` / ``probe_ntp``
+    / ``probe_snmp`` / ``probe_syslog``, ``whois_lookup``, ``lookup``
+    / ``lookup_many`` / ``enumerate_dns`` / ``attempt_zone_transfer``
+    / ``reverse_ptr``.
+  Known gap: ``follow_redirects=True`` on httpx only validates the
+  original URL — the redirect target is not re-validated. Closing
+  this requires a connect-time hook on the HTTP client (kaos-core
+  follow-up). Hostname-only inputs (most DNS / WHOIS use cases)
+  pass through; the gate fires on IP literals where the policy
+  classification is unambiguous.
+
+- **Browser contexts are now session-scoped** (WEB5-002). Every entry
+  in ``BrowserClient._contexts`` / ``_pages`` / ``_request_logs`` /
+  ``_response_bodies`` / ``_logging_config`` is keyed by the tuple
+  ``(KaosContext.session_id, context_id)``. Previously, the shared
+  process-global client keyed by raw ``context_id`` strings — any
+  caller who knew or guessed a context_id could click/fill/screenshot
+  another caller's pages, read their cookies, or download captured
+  fetch/XHR bodies. With the MCP HTTP server fronting multiple
+  agents, that is a cross-tenant browser session takeover. Cross-
+  session lookups now miss uniformly with the same "No active page" /
+  "No context '<id>'" error a missing context returns — never
+  disclosing existence in another session. ``close_context`` from a
+  different session is a silent no-op. ``BrowserClient.active_contexts``
+  changed from a property to a ``method(session_id) -> list[str]``
+  that returns only the calling session's context IDs. Library
+  callers that omit ``session_id`` fall back to a module-level
+  ``ANONYMOUS_SESSION_ID`` sentinel so the original single-user stdio
+  surface keeps working without churn.
+
+- **`SaveAuthStateTool` no longer accepts a caller-supplied filesystem
+  path** (WEB5-004). The previous implementation passed an MCP-input
+  ``path`` straight to Playwright's ``context.storage_state(path=...)``
+  — path-traversal / arbitrary-write to anywhere the server process
+  could write, plus a credentials-leak persistence path. Rewritten to:
+  capture the storage state in-memory via new
+  ``BrowserClient.get_storage_state(context_id)``, write to a
+  session-scoped VFS path, and persist as a kaos-core artifact via
+  ``KaosContext.runtime.artifacts.create_from_path`` (auto-bound to
+  the caller's ``session_id``). Returns an ``ArtifactManifest`` the
+  agent retrieves via standard artifact MCP tools. **Breaking change
+  for the MCP tool input schema**: the ``path`` parameter is removed
+  and replaced with an optional ``name`` parameter (artifact name).
+  Library users with their own filesystem authority can still call
+  ``BrowserClient.save_storage_state(path)`` directly.
+
+- **Observed third-party traffic redacts sensitive headers by default**
+  (WEB5-003). When ``kaos-web-browser-log-requests`` captures network
+  traffic, the recorded request and response headers now mask values
+  for ``Authorization``, ``Proxy-Authorization``, ``Cookie``,
+  ``Set-Cookie``, ``X-API-Key``, ``X-Auth-Token``, ``X-CSRF-Token``,
+  plus any header whose name matches the catch-all
+  ``(?i).*(?:secret|token|api[_-]?key|password|auth).*``. Mask format
+  ``<redacted: N bytes>`` preserves length information without leaking
+  the value. New ``KAOS_WEB_REDACT_OBSERVED_TRAFFIC`` env var
+  (default ``true``); set ``false`` for explicit security-research
+  workflows. The agent's OWN session cookies (returned by
+  ``kaos-web-browser-cookies`` / ``GetCookiesTool``) are NOT
+  redacted — they're the agent's own state.
+
+- **Response-body size cap enforced at every fetch site** (WEB5-007).
+  New `KaosWebSettings.max_body_bytes` (env: `KAOS_WEB_MAX_BODY_BYTES`,
+  default 50 MB) bounds memory usage on hostile or misconfigured
+  endpoints. Enforced at three sites:
+  - `HttpClient._raw_fetch` switched to `client.stream() +
+    aiter_bytes()` with a pre-check on the declared `Content-Length`
+    header and a running tally over the streamed bytes. Aborts with
+    `BodyTooLargeError` before materialization.
+  - `BrowserClient.fetch` post-checks `len(page.content())` (Playwright
+    has no streaming variant) — protects downstream parsers and
+    artifact storage from operating on absurd strings.
+  - `kaos_web.discover.sitemap._decompress_gzip` switched to
+    `gzip.GzipFile.read(max_bytes + 1)` (gzip-bomb protection — a
+    small gzipped payload can decompress to gigabytes; bounded read
+    is the only memory-safe pattern).
+  New `BodyTooLargeError(WebError)` carries `size_bytes`,
+  `max_bytes`, and an agent-friendly recovery hint pointing at the
+  env var.
+
+- **URL filter regexes now use the Rust regex engine when available**
+  (WEB5-008). `kaos_web.discover.discovery._compile_patterns` previously
+  built `re.compile(...)` patterns from caller-supplied include /
+  exclude regex strings and applied `pattern.search(...)` to every
+  discovered URL path. Stdlib `re` is a backtracking engine —
+  pathological patterns like `(a+)+b` against `"a" * N` run in
+  exponential time and block the asyncio event loop (ReDoS).
+  Compiled patterns now route through a `_SafePattern` shim that
+  prefers `kaos_nlp_core.matching.RegexMatcher` (Rust regex, linear
+  time, no backtracking) when the `[nlp]` optional extra is installed,
+  with stdlib `re` as a fallback (one-shot warning logged so operators
+  see the path). Install `kaos-web[nlp]` to get the protection by
+  default.
+
+- **CacheMiddleware bypasses any request bearing auth-shaped headers**
+  (WEB5-009). Cache key is `method:url` only — without this gate, an
+  authenticated request would either return another caller's cached
+  anonymous response (read-leak) or poison the cache for subsequent
+  anonymous callers (write-leak). The bypass is conservative: if the
+  request includes any of `Authorization`, `Proxy-Authorization`,
+  `Cookie`, `X-API-Key`, `X-Auth-Token`, `X-CSRF-Token`
+  (case-insensitive), the cache is skipped entirely (no LOOKUP, no
+  STORE) and the request always hits upstream. Anonymous requests
+  still benefit from the cache normally.
+
+- **TLS verification on domain-intelligence probes now defaults to ON**
+  (WEB5-006). The two probes that explicitly disable verification
+  (`kaos-web-http-headers`, `kaos-web-extract-org`) previously
+  defaulted to `KAOS_WEB_DOMAIN_VERIFY_TLS=false` (audit-02 WEB2-001
+  shipped the setting with that default; WEB5-006 flips it to `true`).
+  Secure-by-default: the typical use case is observing healthy public
+  sites where CA validation is correct. Set
+  `KAOS_WEB_DOMAIN_VERIFY_TLS=false` to inspect hosts whose cert is
+  itself the subject of inspection (self-signed, expired, mismatched
+  SAN, staging environments). **Migration**: anyone scraping such
+  hosts will see new TLS errors; explicitly opt out via the env var.
+  Content-extraction tools (`HttpClient` / `BrowserClient`) keep TLS
+  verification on independently of this flag.
+
+- **Browser interaction tools now declare `destructiveHint=True`**
+  (WEB5-005). Click / fill / type / press / select / evaluate run
+  inside an authenticated browser session and CAN trigger real actions
+  (form submit, settings change, JS-driven side effects). The prior
+  shared `_BROWSER_WRITE_ANNOTATIONS` annotation said
+  `destructiveHint=False` for all of them, which weakened any MCP
+  client that gates auto-approval on the annotation. Split into
+  `_BROWSER_INTERACT_ANNOTATIONS` (destructive=True for the 6
+  interaction tools) and the existing `_BROWSER_WRITE_ANNOTATIONS`
+  (destructive=False for local-state tools that do not trigger remote
+  actions: set-cookie, save-auth-state, enable-request-logging,
+  close-context, navigate). No behavior change — annotation
+  correctness only.
+
+### Changed
+
+- **Refactored package layout** for better cohesion (per
+  `docs/python/design/modules.md`):
+  - New `kaos_web.discover` subpackage groups the BFS-discovery
+    subsystem: `batch`, `crawl`, `discovery`, `sitemap` (formerly four
+    top-level modules with mutual imports). Re-exports the canonical
+    public API at the package level (e.g. `from kaos_web.discover
+    import batch_fetch, crawl_site, discover_urls, parse_sitemap`).
+  - `kaos_web.browser_page_prep` → `kaos_web.clients.page_prep`. Only
+    consumer was `clients/browser.py`; the helper is logically a
+    browser-client primitive.
+  - The four `*_tools.py` files (`tools.py`, `browser_tools.py`,
+    `crawl_tools.py`, `domain_tools.py`) **stay top-level** per the
+    explicit KAOS convention documented in
+    `docs/python/design/modules.md` ("split tool files by domain when
+    they would otherwise exceed ~1500 lines"). No tools/ subpackage.
+
+  Pre-0.1.0a1 — no published version pins these import paths, so no
+  back-compat shims are shipped. If you imported from these paths in
+  pre-release builds, update to the new locations.
+
+## [0.1.0a1] — 2026-05-08
+
+First public alpha release.
+
+### Added
+
+- Web content extraction for the KAOS (Kelvin Agentic Operating System)
+  platform. Fetches HTML from URLs over HTTP or a headless browser and
+  produces `kaos-content` `ContentDocument` AST with provenance on every
+  block.
+- **Dual-client architecture**: `HttpClient` (httpx, async, HTTP/2,
+  connection pooling, auth, SSL, proxy, structured error mapping) and
+  `BrowserClient` (Playwright, lazy launch, named-context page tracking,
+  cookie-banner dismissal for 8 known consent-management platforms).
+- **HTML-to-AST extraction** (`html_to_document`): lxml element tree to
+  Block/Inline `ContentDocument` with `SourceRef` + `Provenance` on
+  every node. Supports headings, paragraphs, lists, blockquotes, code
+  blocks, tables, figures, definition lists, thematic breaks, and the
+  full inline grammar (text, strong, emphasis, code, link, image,
+  strikethrough, sub/superscript, line break).
+- **Level-3 learned readability** (`extract.readability_l3`): pre-trained
+  logistic regression over 35 DOM-node features. Default extractor with
+  a `content_scope` parameter (0.0–1.0) controlling
+  precision/recall tradeoff. Heuristic readability and semantic
+  container detection (`<main>` → `<article>` → `[role=main]` → `<body>`)
+  remain as fallbacks when the L3 extraction returns `< 50` words.
+- **Composable middleware chain** (`middleware/`): `RetryMiddleware`
+  (exponential backoff with jitter, honors `Retry-After`),
+  `RateLimitMiddleware` (per-domain token bucket), `RobotsMiddleware`
+  (stdlib `robotparser`, cached per domain), `CacheMiddleware`
+  (in-memory LRU, RFC 7231 compliant). Wired into `HttpClient.fetch()`
+  via `MiddlewareChain`; configurable per-client.
+- **Search backends** (`search/`): SerpAPI, DuckDuckGo, Exa, Brave —
+  unified async interface with auto-detection from configured API keys.
+- **Domain intelligence** (`domain/`): TCP probing + banner grab,
+  TLS cert inspection, HTTP header analysis with CDN detection and
+  security scoring, DNS lookup/enumeration/zone-transfer/security
+  posture, stdlib WHOIS client (55-TLD server map with referral
+  following), UDP protocol-aware probes (DNS / NTP / SNMPv1 / syslog),
+  pure banner→ServiceIdentity fingerprinting, and Schema.org
+  organization-entity extraction.
+- **Multi-page workflows**: `discovery` (sitemaps + page links with
+  pattern filtering), `batch` (concurrent URL fetching with
+  `asyncio.Semaphore`), `crawl` (BFS site crawl with depth/page limits
+  and sitemap-first discovery).
+- **45 MCP tools across 4 servers**:
+  - `register_web_tools()` — 7 extraction tools (fetch-page, get-text,
+    get-markdown, get-metadata, search-page, get-links, get-images).
+  - `register_browser_tools()` — 19 browser interaction tools
+    (navigate, click, fill, type, press, select, screenshot, evaluate,
+    snapshot, content, cookies, set-cookie, save-auth, log-requests,
+    requests, get-request, captured-responses, list-contexts,
+    close-context).
+  - `register_crawl_tools()` — 3 multi-page tools (discover-urls,
+    batch-fetch, crawl-site).
+  - `register_domain_tools()` — 14 domain-intelligence tools
+    (tcp-probe, tcp-banner, tls-inspect, http-headers, service-detect,
+    fingerprint-service, dns-lookup, dns-enumerate, dns-zone-transfer,
+    dns-security, whois-lookup, domain-profile, extract-org,
+    udp-probe). Enabled with `kaos-web-serve --domain`.
+- **Typed module settings** (`KaosWebSettings`): `KAOS_WEB_*` env prefix
+  with legacy fallbacks (`SERPAPI_API_KEY`, `EXA_API_KEY`,
+  `BRAVE_API_KEY`, `KAOS_BROWSER_*`, `KAOS_SEARCH_*`). API keys use
+  `pydantic.SecretStr`. Knobs cover browser (type/headless/channel),
+  search (backend selection + per-backend timeouts + DDG user-agent),
+  discovery, sitemap, crawl, and middleware behavior.
+- **CLI** (`kaos-web`): `extract`, `metadata`, `serve` subcommands with
+  `--json` envelope output for piping/agents.
+- **Standalone MCP server** (`kaos-web-serve`): stdio (default) or
+  streamable HTTP (`--http --port`); `--browser`, `--crawl`, `--domain`
+  flags compose the registered tool surface; `--debug` enables verbose
+  logging.
+- **Optional extras**: `[browser]` adds Playwright for JS-heavy pages;
+  `[dns]` adds dnspython for the domain-intelligence DNS tools; `[mcp]`
+  adds `kaos-mcp` for serving tools as a FastMCP bridge; `[nlp]` adds
+  `kaos-nlp-core` for BM25 search inside extracted documents.
+
+### License
+
+This release is the first to ship under the Apache License 2.0. Earlier
+internal versions were proprietary.
+
+[Unreleased]: https://github.com/273v/kaos-web/compare/v0.1.0a1...HEAD
+[0.1.0a1]: https://github.com/273v/kaos-web/releases/tag/v0.1.0a1

kaos_web-0.1.0a1/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 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 273 Ventures LLC
+
+   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.

kaos_web-0.1.0a1/NOTICE

@@ -0,0 +1,8 @@
+kaos-web
+Copyright 2026 273 Ventures LLC.
+
+This product includes software developed at 273 Ventures LLC
+(https://273ventures.com).
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file
+distributed with this software for the full text of the license.