kaos-office 0.1.0__tar.gz

kaos_office-0.1.0/.gitignore

@@ -0,0 +1,16 @@
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+# kaos-core VFS scratch directory created when writer tests / examples
+# instantiate a default KaosRuntime in the working tree.
+.kaos-vfs/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+*.egg-info/
+dist/
+build/
+htmlcov/
+coverage.xml

kaos_office-0.1.0/CHANGELOG.md

@@ -0,0 +1,430 @@
+# Changelog
+
+All notable changes to `kaos-office` 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-05-20
+
+### Released
+
+- 0.1.0 GA — WU-L of GA plan. First stable release. Public API frozen.
+- Pin floor raised to `>=0.1.0,<0.2` across all kaos-* runtime and
+  optional dependencies. Refreshed `uv.lock` to pick up the 0.1.0
+  line of every upstream.
+
+### Internal
+
+- WU-L of the 0.1.0 GA plan
+  (`kaos-modules/docs/plans/2026-05-20-0.1.0-ga-plan.md`).
+
+
+## [0.1.0rc1] — 2026-05-20
+
+### Changed
+
+- Pin floor raised to `>=0.1.0rc1,<0.2` across kaos-* runtime and
+  optional dependencies (`kaos-core`, `kaos-content[markdown]`,
+  `kaos-mcp`, `kaos-nlp-core`). Refreshed `uv.lock` to pick up the
+  rc1 line of every upstream.
+
+### Internal
+
+- WU-J of the 0.1.0 GA plan
+  (`kaos-modules/docs/plans/2026-05-20-0.1.0-ga-plan.md`).
+  Release candidate; freezes the public API for `kaos-office`
+  ahead of 0.1.0 GA.
+
+
+## [0.1.0a8] — 2026-05-20
+
+### Changed
+
+- Bumped minimum `kaos-core` to `0.1.0a12` (post-URI-redesign +
+  Capability type). kaos-office does not use the URI redesign
+  directly — the bump aligns the supported floor with the rest of
+  the kaos-* DAG ahead of 0.1.0 GA.
+- Refreshed `uv.lock` to pick up `kaos-core 0.1.0a12` and
+  `kaos-nlp-core 0.1.0a8`.
+
+### Internal
+
+- WU-F.5 of the 0.1.0 GA plan
+  (`kaos-modules/docs/plans/2026-05-20-0.1.0-ga-plan.md`):
+  catch-up to kaos-core 0.1.0a12.
+
+## [0.1.0a7] — 2026-05-18
+
+### Added
+
+- **`kaos_office.docx.numbering` is now a package**, replacing the
+  single-file module of the same name. New public surface:
+  - `NumberingDefinitions` — the parsed schema. Resolves
+    `(num_id, ilvl)` to a `LevelDefinition`, honoring
+    `<w:lvlOverride>` / `<w:startOverride>`.
+  - `NumberingState` — running counter machine. Emits the rendered
+    visible label (`"11."`, `"(a)"`, `"11(a)(i)"`) for each numbered
+    paragraph as the reader streams the document.
+  - `parse_numbering_xml(numbering_xml_bytes) -> NumberingDefinitions`
+    — replaces ad-hoc XML parsing scattered across the resolver.
+  - `format_number(value, num_fmt)` and `format_lower_letter`,
+    `format_lower_roman`, `format_upper_letter`, `format_upper_roman`,
+    `format_ordinal`, `format_decimal_zero` — converters for visible
+    numerals. Excel-style letter wraparound (`z → aa`) and Roman
+    boundary cases are explicitly tested.
+  - `is_ordered_format`, `BULLET_CHAR` re-exported for convenience.
+- **`NumberingResolver`** preserves its 0.1.0a6 public API
+  (`from_xml`, `is_ordered`, `get_format`, `has_numbering`) as a thin
+  shim over `NumberingDefinitions` so existing callers continue to
+  work unchanged. New code should prefer `NumberingDefinitions` +
+  `NumberingState` because they expose the rendered label, not just a
+  list-type boolean.
+- **OOXML namespace constants** for the newly-parsed elements:
+  `W_LVL_TEXT`, `W_START`, `W_LVL_RESTART`, `W_LVL_OVERRIDE`,
+  `W_START_OVERRIDE`, `W_IS_LGL`, `W_SUFF`, `W_LVL_JC`.
+- **`<w:pStyle>`-linked numbering** — paragraphs that inherit
+  numbering through their paragraph style (no inline `<w:numPr>`)
+  now pick up the rendered label. Firm templates routinely link
+  "Heading 1" to a numbering definition so document authors get
+  "Article 1.", "Article 2." automatically without manual numPr
+  maintenance; before this change those headings parsed without
+  labels. `NumberingDefinitions.resolve_pstyle(style_id)` does the
+  lookup; `_handle_paragraph` consults it when no inline numPr is
+  present.
+- **International numbering formats** added to the converter table:
+  `hebrew1`, `arabicAlpha`, `chineseCounting` (also
+  `chineseCountingThousand`), `aiueo`, and `iroha`. Each is
+  exercised by the formatter unit tests and the `format_number`
+  dispatch test. Remaining Word formats (`hindi*`, `korean*`,
+  `thai*`, `vietnamese*`, `ordinalText`, etc.) fall through to the
+  decimal fallback with a structured warning, ready for incremental
+  addition when fixtures surface.
+- **`kaos-office-search` and `kaos-office-search-pptx` result dicts**
+  now include `path: list[str]` per hit — the structural breadcrumb
+  (root-first, INCLUDING the immediate section) for the matched
+  paragraph or slide. Empty list is the explicit "no enclosing
+  heading" contract; downstream agents MUST NOT invent section
+  identifiers for hits with empty `path`. See
+  `kaos-modules/docs/plans/persona-matrix-followups.md` §4.
+
+### Changed
+
+- **kaos-content floor raised to `>=0.1.0a12`** to pick up the
+  structural-breadcrumb contract on `SearchResult.path` /
+  `DocumentView.block_path()` AND the new `numbering_label` field on
+  `Paragraph` / `Heading` / `ListItem`. The DOCX reader populates
+  `numbering_label` with the rendered visible numeral from
+  `word/numbering.xml` (e.g. `"Section 11."`, `"(a)"`, `"11(a)(i)"`),
+  the writer round-trips them as plain-text run prefixes, and the
+  serializers in kaos-content emit them verbatim.
+- **DOCX reader populates `numbering_label`** on `Heading`,
+  `Paragraph`, and `ListItem` AST nodes. `ParseContext` now carries
+  a `NumberingState` alongside the existing `NumberingResolver`; for
+  each paragraph carrying `<w:numPr>` with a non-zero `numId`, the
+  rendered visible label is resolved in document order and attached
+  to the AST node. Headings that inherit numbering through Word's
+  auto-numbering machinery (the common legal pattern: `Section 11.
+  GOVERNING LAW`) now carry the attorney-citable label that the
+  previous reader silently dropped. List items receive the same
+  treatment, replacing the silent fall-through to position-based
+  recomputation downstream.
+- **DOCX writer preserves `numbering_label` round-trip.** When a
+  `Heading`, `Paragraph`, or `ListItem` carries a rendered numbering
+  label (set by the reader from `numbering.xml`), the writer bakes
+  the label as a plain-text run prefix on the paragraph so the
+  round-tripped DOCX renders the same attorney-citable token. The
+  pragmatic trade-off (versus reconstructing a full `<w:abstractNum>`
+  per pattern) is that Word's edit-time renumbering no longer
+  applies to imported sections — acceptable for review / redline
+  workflows where the document is the source of truth, not a
+  regenerable template. Round-trip tests under
+  `tests/unit/test_docx_numbering_roundtrip.py` exercise all three
+  fixture shapes (decimal / NDA / legal-outline).
+
+Stages 1c (search-path) + 2-7 (docx-numbering-resolution) of the
+respective plans under `kaos-modules/docs/plans/`.
+
+## [0.1.0a6] — 2026-05-17
+
+### Changed
+
+- **kaos-core floor raised to `>=0.1.0a10`** to pick up the URI
+  contract redesign (bare names route through
+  `context.default_vfs_namespace`; `file://` and `vfs://` schemes).
+  See `kaos-modules/docs/plans/uri-contract-redesign.md`. The 15
+  file-input tools route through `resolve_input_path` as
+  pass-throughs; no synthetic bare names internally.
+- **Tests migrated to the new URI contract.** Test fixtures and
+  nonexistent-path literals in `tests/unit/test_tools.py`,
+  `tests/unit/test_pptx_tools.py`,
+  `tests/integration/test_mcp_office_pipeline.py`, and
+  `tests/integration/test_mcp_xlsx_pipeline.py` now supply
+  `file:///abs/path` URIs (via `Path.as_uri()`) instead of bare
+  absolute strings, mirroring how MCP clients will pass
+  trusted-source filesystem paths under the new contract. No
+  production code change in `kaos-office` itself — `tools.py` was
+  already a pure pass-through to `resolve_input_path`.
+
+## [0.1.0a5] — 2026-05-17
+
+### Changed
+
+- **All 15 file-input MCP tools now route their `path` parameter
+  through `kaos_core.path_resolver.resolve_input_path()`** via a new
+  internal adapter `kaos_office._path_resolver.resolve_office_input()`.
+  Previously every tool ran `Path(path_str).exists()` against the
+  process CWD, which made files uploaded into `KaosRuntime.vfs` by a
+  host UI (e.g. `kaos-ui`'s single-user-chat SPA) invisible — agents
+  saw an unbroken sequence of "File not found" errors and were at risk
+  of hallucinating answers from zero successful reads. Affected tools:
+  `kaos-office-parse-docx`, `kaos-office-get-text`,
+  `kaos-office-get-markdown`, `kaos-office-metadata`,
+  `kaos-office-search` (DOCX); `kaos-office-parse-pptx`,
+  `kaos-office-list-slides`, `kaos-office-get-slide`,
+  `kaos-office-search-pptx`, `kaos-office-get-slide-notes` (PPTX);
+  `kaos-office-parse-xlsx`, `kaos-office-list-sheets-xlsx`,
+  `kaos-office-get-sheet-xlsx`, `kaos-office-xlsx-metadata` (XLSX);
+  and `kaos-office-write-pptx`'s optional `template_path`. Each tool's
+  `path` schema description now advertises that
+  `kaos://artifacts/<id>` URIs and session-VFS paths are accepted in
+  addition to filesystem paths. Parse-* tools that materialise a new
+  derived artifact now thread `source_artifact_id` / `source_body_uri`
+  into their `structuredContent` when the input came from the
+  artifact store, so the SPA's ArtifactCard renders the original
+  upload's id rather than a fresh derived one. Stage 1 of
+  `kaos-modules/docs/plans/vfs-blind-tools-audit-and-fix-plan.md` —
+  upstream fix for the production hallucination incident where every
+  SPA-uploaded `.docx` was invisible to the entire office tool set.
+  Behavior for absolute filesystem paths is unchanged (the resolver's
+  filesystem branch is a passthrough). New unit tests:
+  `tests/unit/test_vfs_path_resolution.py` (15 cases — one per
+  affected read tool plus the WritePptx template path).
+- **Pinned `kaos-core>=0.1.0a9,<0.2`** (was `>=0.1.0a1`). The 0.1.0a9
+  release ships `kaos_core.path_resolver`, which the new adapter
+  depends on.
+
+## [0.1.0a4] — 2026-05-15
+
+### Added — documents + authoring registration entry points (PRD PR 1)
+
+- **`register_office_documents_tools(runtime)`** — registers the 14
+  read-only Office tools (DOCX / PPTX / XLSX parsers, listers,
+  getters, metadata inspectors, BM25 searchers). Pins the
+  SessionToolSet `documents` group entry point.
+- **`register_office_authoring_tools(runtime)`** — registers the 3
+  Office writers (`kaos-office-write-docx` /
+  `kaos-office-write-pptx` / `kaos-office-write-xlsx`). Pins the
+  SessionToolSet `authoring` group entry point: denied by default
+  at the ceiling and opted into per-session for drafting workflows.
+- **`register_office_tools(runtime)`** is now a backward-compatible
+  union — every existing caller continues to see the same 17 tools
+  with the same names and schemas.
+
+Motivated by `kaos-modules/docs/internal/dynamic-tool-planning-prd.md`
+§4 ("PR 1 — catalog expansion"). Purely additive: no tool name,
+schema, or behavior changes.
+
+## [0.1.0a3] — 2026-05-15
+
+### Fixed
+
+- **`kaos-office-parse-xlsx`'s `sheets` parameter now declares its
+  element type.** Previously the schema was `type=array` with no
+  `items`, which OpenAI's strict JSON Schema validator rejected
+  with HTTP 400 `invalid_function_parameters`. The whole tool
+  catalog for the turn was lost. Now `items: {type: "string"}` so
+  the LLM gets a precise contract for sheet names. kaos-core
+  0.1.0a7's defensive `items: {}` floor is belt + suspenders.
+
+### Added
+
+- **`[mcp]` extra restored.** kaos-office's pyproject originally
+  declared the `[mcp]` extra absent at 0.1.0a1 because `kaos-mcp`
+  wasn't on PyPI yet and `uv lock` refuses to resolve unresolvable
+  declared extras (F009 #4). `kaos-mcp` shipped (now at 0.1.0a3), so
+  the extra is back: `pip install kaos-office[mcp]` (or
+  `uv add kaos-office[mcp]`) now pulls in
+  `kaos-mcp>=0.1.0a3,<0.2` for the FastMCP-backed
+  `kaos-office-serve` runner and the MCP integration tests.
+
+### Fixed
+
+- **CI: nightly integration tests now install the `mcp` extra.** The
+  scheduled-only `integration tests` job in `security.yml` failed
+  collection on `test_mcp_office_pipeline.py` /
+  `test_mcp_xlsx_pipeline.py` with
+  `ModuleNotFoundError: No module named 'kaos_mcp'` because the
+  job ran `uv sync --group dev` without the (then-missing) extra.
+  Now syncs with `--group dev --extra mcp` so the MCP-bridge tests
+  can import `kaos_mcp`. Push/PR runs are unchanged (the integration
+  job is `if: github.event_name == 'schedule' || workflow_dispatch`).
+
+
+### Fixed
+
+- **Tests: Windows-x64 leg failed on hardcoded POSIX tempfile path.**
+  ``tests/unit/test_reader.py::_parse_from_body`` wrote its synthetic
+  DOCX to ``Path("/tmp/test_reader.docx")``. On Windows this resolved
+  to ``\\tmp\\test_reader.docx`` (a non-existent drive-root path) so
+  every DOCX reader test failed with ``FileNotFoundError``. Switched
+  to ``tempfile.mkstemp(suffix=".docx")`` so the path lives under
+  ``%TEMP%`` on Windows and ``/tmp`` on POSIX. No production code
+  change. Files: ``tests/unit/test_reader.py``.
+### Security
+
+- **vulture (dead-code scan) now runs in pre-commit + CI alongside
+  the existing bandit job.** New `vulture` hook in
+  ``.pre-commit-config.yaml`` mirrored by a new ``vulture (dead-code
+  scan)`` job in ``security.yml``. `--min-confidence 100` with the
+  shared `--ignore-names` list for names vulture can't infer from
+  the import graph (framework callbacks, OAuth/OIDC field names,
+  signal handlers, MCP `_meta` keys). Also lands the existing
+  bandit hook in pre-commit (it was only in CI before). Both pass
+  clean. Mirrors the rollout from kaos-core.
+### Changed
+
+- **uv.lock is now tracked in git.** Previously gitignored at v0.1.0a1
+  because the ``[mcp]`` optional extra (and the ``kaos-mcp`` dev
+  dependency) referenced a sibling not yet on PyPI; ``uv lock``
+  couldn't resolve them. ``kaos-mcp`` shipped (0.1.0a2), so the
+  original gating reason no longer applies. Tracking the lockfile
+  gives reproducible local dev environments, lets Dependabot surface
+  sibling-version bumps as PRs, and makes the supply-chain pin set
+  publicly auditable. Mirrors the org-wide convention being adopted
+  across all 16 kaos-* repos.
+
+## [0.1.0a2] — 2026-05-08
+
+CI supply-chain hardening (audit-02 F7) and SECURITY.md polish (audit-02
+F8). No source code or public API changes.
+
+### Security
+
+- **F7: CI supply-chain hardening.** `.github/workflows/security.yml`
+  pins the gitleaks Docker image to `v8.21.2` (no longer tracking
+  `:latest`), adds a Bandit static-analysis job (medium severity /
+  medium confidence; `B101,B404,B603,B607` skipped), and runs the
+  integration suite on `schedule` and `workflow_dispatch` so
+  cross-package regressions surface against `main` even though the
+  unit gate stays the PR fast path. SHA-pinning of GitHub Actions
+  themselves remains a follow-up; the existing
+  `.github/dependabot.yml` `github-actions` ecosystem PRs continue to
+  keep tag-pinned actions current.
+
+### Changed
+
+- **F8: `SECURITY.md` scope polished.** Added a one-paragraph preamble
+  describing what `kaos-office` does, listed the actual Tool boundary
+  (`ParseDocxTool`, `WriteDocxTool`, `ParseXlsxTool`, …), called out
+  that MCP transport security lives in `kaos-mcp` rather than here.
+  Existing OPC / OOXML / writer-path scope kept verbatim — it was
+  already accurate for this module.
+
+## [0.1.0a1] — 2026-05-07
+
+First public alpha. Office document extraction (DOCX, PPTX, XLSX) into
+the kaos-content typed AST, with native lxml round-trip writers and 17
+MCP tools. Closes every finding in `docs/audit-01/kaos-office.md`
+(KO-001..KO-008).
+
+### Added
+
+- **`LICENSE`, `NOTICE`, `CHANGELOG.md`** seeded for the public
+  release. License flips from `LicenseRef-Proprietary` to Apache-2.0
+  via PEP 639 (`license = "Apache-2.0"`, `license-files =
+  ["LICENSE", "NOTICE"]`). PEP-639-superseded `License ::` classifier
+  removed.
+- **Aggregate `[xlsx]` extra** — `python-calamine` + `openpyxl`. The
+  default native lxml reader needs no extras; this aggregate is for
+  callers who want the calamine fast-path *and* openpyxl-backed
+  formula extraction in one install. Closes audit-01 KO-004.
+- **`kaos_office.pptx.OverflowMode` re-export** plus `parse_pptx`,
+  `get_slide_count`, `get_slide_text`, `get_slide_notes`, and
+  `list_slides` at the `kaos_office.pptx` package level.
+  `kaos_office.xlsx` now also re-exports `parse_xlsx` + `list_sheets`
+  next to the writer entry points. Closes audit-01 KO-007.
+- **External fixtures opt-in mechanism** — `tests/conftest.py`
+  exposes `external_fixture()` + `skip_without_external_fixture()`
+  driven by the `KAOS_OFFICE_EXTERNAL_FIXTURES_DIR` env var, for
+  real-world documents too large to vendor in-repo
+  (e.g. multi-MB legal decks). Closes audit-01 KO-006.
+- **`IEO2021_ChartLibrary_Industrial.pptx`** vendored under
+  `tests/fixtures/pptx/` (447 KB; previously read from an absolute
+  `kelvin-modules` path on the maintainer's workstation). Same
+  reproducibility fix.
+
+### Changed
+
+- **`parse_docx()` resolves the input path before `Path.as_uri()`.**
+  Pre-fix, any relative DOCX path crashed the reader with
+  `ValueError: relative path can't be expressed as a file URI` —
+  ordinary CLI / MCP usage that handed a filename in the current
+  working directory was broken before the file was even opened.
+  Mirrors the existing PPTX/XLSX behavior. Closes audit-01 KO-001.
+  Regression coverage: `tests/unit/test_reader.py::TestRelativePaths`.
+- **`kaos_office.pptx` writer entry points are typed lazy wrappers.**
+  The previous `try/except ImportError: write_pptx = None` pattern
+  failed `ty check` (`invalid-assignment` — `None` is not assignable
+  to a callable returning `Path` / `bytes`) and exposed `None`
+  callables when `python-pptx` was absent. Replaced with thin
+  wrappers that defer the writer import until call time and raise
+  `ImportError` with the `[pptx]` install hint instead. Public
+  signatures and behavior are unchanged when `python-pptx` is
+  installed. Closes audit-01 KO-002. Regression coverage:
+  `tests/unit/test_pptx_writer.py::TestPptxLazyWrappers` (including
+  a monkeypatched missing-dep path).
+- **DOCX vMerge continuation cells use a typed marker class.**
+  `_handle_table` previously emitted `Cell(content=(), row_span=0,
+  col_span=col_span)` for `<w:vMerge/>` continuation cells. The
+  `row_span=0` sentinel was rejected after kaos-content 0.1.0a1
+  tightened `Cell` validation to require span ≥ 1, so real-world
+  documents with vertical merges (e.g. the audit's Toro 2022 Term
+  Loan and MCS Redline fixtures) failed to parse. Continuation cells
+  now carry `row_span=1` and `attr=Attr(classes=("vmerge-continue",))`,
+  preserving the grid geometry while letting downstream consumers
+  detect the merge without a magic-value sentinel. Closes audit-01
+  KO-003.
+- **XLSX tool errors follow the KAOS three-part contract.** Every
+  `ToolResult.create_error()` site in the four XLSX tools
+  (`ParseXlsxTool`, `ListSheetsXlsxTool`, `GetSheetXlsxTool`,
+  `XlsxMetadataTool`) now states what went wrong, how to fix it, and
+  which sibling tool to try next. Shared `_XLSX_IMPORT_ERROR` and
+  `_xlsx_file_not_found()` helpers keep the messages consistent and
+  unit-testable. Errors no longer falsely claim that "XLSX requires
+  python-calamine" — the default native lxml reader has no extras.
+  Closes audit-01 KO-008.
+- **`xlsxwriter`** is no longer a published `[xlsx-write]` extra; it
+  remains in `[dependency-groups].dev` where it belongs (it is the
+  cross-validator the test suite uses to verify the native lxml
+  writer's output, not a production code path). The reference
+  implementation in `kaos_office.xlsx._xlsxwriter_reference` (private
+  per the leading underscore) updates its docstring + ImportError to
+  point at the dev group. Closes audit-01 KO-005.
+- **`tests/conftest.py`** rewritten to use in-repo vendored fixture
+  roots as primary; the legacy `KELVIN_FIXTURES` /
+  `KELVIN_PPTX_FIXTURES` symbols are preserved as aliases pointing at
+  the local copies so existing test imports keep working. The two
+  benchmark scripts under `tests/` are env-overridable
+  (`KAOS_OFFICE_BENCHMARK_{DOCX,PPTX}_DIR`) and default to the
+  vendored corpora. No `/home/<user>/...` paths remain in tracked
+  files. Closes audit-01 KO-006.
+
+### Project metadata
+
+- `[project.urls]` adds `Issues` + `Changelog`; `Repository` switches
+  to `https://github.com/273v/kaos-office`.
+- `keywords` populated; `Operating System :: OS Independent`
+  classifier added.
+- `[tool.hatch.build.targets.sdist]` includes `LICENSE`, `NOTICE`,
+  and `CHANGELOG.md`.
+- `[mcp]` extra (which depended on `kaos-mcp`, not yet on PyPI) is
+  stripped from the per-module repo's `pyproject.toml` per
+  `docs/oss/checklists/per-package-release.md` Phase B5; it will be
+  re-added in `0.1.0a2` once `kaos-mcp` ships.
+
+[Unreleased]: https://github.com/273v/kaos-office/compare/v0.1.0a1...HEAD
+[0.1.0a1]: https://github.com/273v/kaos-office/releases/tag/v0.1.0a1

kaos_office-0.1.0/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_office-0.1.0/NOTICE

@@ -0,0 +1,8 @@
+kaos-office
+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.