okf 1.0.0

data/.okf/format/cross-links.md

@@ -0,0 +1,52 @@
+---
+type: Format
+title: Cross-links (spec §5)
+description: Plain Markdown links between concepts that become the knowledge graph's directed edges.
+resource: lib/okf/markdown/links.rb
+tags: [format, links, graph, diagram]
+timestamp: 2026-07-11T12:00:00Z
+---
+
+# Overview
+
+A cross-link is an ordinary Markdown link from one concept's body to another
+concept file. `OKF::Markdown::Links` extracts them, and that is the whole edge
+mechanism: the [graph](../model/graph.md) is *emergent* — you never declare it,
+it arises from the links you write. Good linking is good knowledge modelling.
+
+```mermaid
+flowchart LR
+  orders["orders.md"] -->|prose link| customers["customers.md"]
+  orders -->|prose link| refunds["refunds.md"]
+  refunds -->|prose link| customers
+```
+
+Files are the nodes; the Markdown links in their bodies are the directed edges.
+Nobody declared this graph — it fell out of three files linking each other.
+
+# Untyped on purpose
+
+A Markdown link asserts only "these two relate." The *kind* of relationship —
+depends-on, supersedes, derived-from — lives in the **prose around the link**,
+never in a made-up typed-edge syntax. Both a human and an agent already
+understand a Markdown link, which is the point of the [dual audience](../overview.md).
+
+# What counts as an edge
+
+- **Bundle-relative links** (e.g. `/model/graph.md`) resolve to another concept
+  and become a directed edge. Absolute bundle-relative targets are preferred so
+  links survive file moves.
+- **External links** — `http(s)://`, `mailto:` — are surfaced separately and are
+  *not* graph edges.
+- A link to a concept that does not exist yet is **not an error** (§5.3): it is
+  not-yet-written knowledge, which consumers MUST tolerate and the
+  [linter](../capabilities/linter.md) surfaces as backlog demand.
+
+The [graph server](../capabilities/graph-server.md) draws these edges; a
+degree-0 concept (no links in or out) is a *loose* file the
+[read views](../capabilities/read-views.md) flag.
+
+# Citations
+
+[1] [lib/okf/markdown/links.rb](https://github.com/serradura/okf-gem/blob/main/lib/okf/markdown/links.rb) — link extraction.
+[2] [SPEC.md §5](https://github.com/serradura/okf-gem/blob/main/lib/okf/skill/reference/SPEC.md) — cross-links and tolerance of broken targets.

data/.okf/format/frontmatter.md

@@ -0,0 +1,38 @@
+---
+type: Format
+title: Frontmatter (spec §4)
+description: The YAML header on every concept, parsed through the gem's single, hardened YAML gateway.
+resource: lib/okf/markdown/frontmatter.rb
+tags: [format, yaml, frontmatter]
+timestamp: 2026-07-11T12:00:00Z
+---
+
+# Overview
+
+Every [concept](../model/concept.md) opens with a YAML frontmatter block delimited
+by `---` lines. `OKF::Markdown::Frontmatter` parses it and is the inverse of
+`Concept#to_markdown`. The only **required** key is
+[`type`](../format/okf-format.md); `title`, `description`, `resource`, `tags`, and
+`timestamp` are recommended, and producers may add any other keys — consumers
+preserve unknown keys and never reject a document for having them.
+
+# The one YAML gateway
+
+All YAML in the gem flows through this one class. That is a deliberate security
+and portability boundary, not an accident of layering:
+
+- it uses `safe_load` — permitting `Date`/`Time`, forbidding aliases — so a
+  bundle can never execute arbitrary Ruby on load;
+- it carries the Psych `<3.1` positional-argument shim, so the gem parses
+  identically on the old Ruby versions the [2.4 floor](../design/ruby-floor.md)
+  targets;
+- `stringify_keys` lives here so the gem needs no ActiveSupport (see
+  [runtime dependencies](../design/runtime-dependencies.md)).
+
+The rule is enforced by convention: `YAML.safe_load` / `YAML.load` appear
+**nowhere else** in the codebase.
+
+# Citations
+
+[1] [lib/okf/markdown/frontmatter.rb](https://github.com/serradura/okf-gem/blob/main/lib/okf/markdown/frontmatter.rb) — the parser and the Psych shim.
+[2] [SPEC.md §4](https://github.com/serradura/okf-gem/blob/main/lib/okf/skill/reference/SPEC.md) — concept documents and frontmatter.

data/.okf/format/index.md

@@ -0,0 +1,9 @@
+# The format
+
+What Open Knowledge Format v0.1 is — the substrate the gem reads, validates, and
+serves. The gem operates on this format; it does not extend it.
+
+* [OKF v0.1](okf-format.md) - portable knowledge as a directory of Markdown + YAML frontmatter files.
+* [Frontmatter](frontmatter.md) - the YAML header on every concept (spec §4) and the gem's one YAML gateway.
+* [Cross-links](cross-links.md) - plain Markdown links that become the knowledge graph's edges (spec §5).
+* [Citations](citations.md) - the provenance convention that keeps a bundle trustworthy (spec §8).

data/.okf/format/okf-format.md

@@ -0,0 +1,43 @@
+---
+type: Format
+title: Open Knowledge Format v0.1
+description: Portable knowledge as a directory of Markdown files with YAML frontmatter that humans and agents both read.
+resource: lib/okf/skill/reference/SPEC.md
+tags: [okf, format, conformance]
+timestamp: 2026-07-11T12:00:00Z
+---
+
+# Overview
+
+OKF is a bundle: a directory of UTF-8 Markdown files. Each non-reserved file is
+one **concept** with two parts — a [YAML frontmatter block](frontmatter.md) and a
+Markdown body. Knowledge is the files; the graph is
+[how they link](cross-links.md). There is no schema registry, no runtime, no
+SDK — the format is minimal on purpose, and the gem is what gives it leverage.
+
+# Reserved files
+
+Two filenames are reserved and are never concepts:
+
+| File | Role | Constraint |
+|------|------|------------|
+| `index.md` | a directory listing for progressive disclosure | carries **no** frontmatter — except the bundle-root `index.md`, which may carry *only* `okf_version` |
+| `log.md` | a dated change history, newest first | date headings are ISO `YYYY-MM-DD` |
+
+# §9 conformance is narrow and tolerant
+
+The spec makes only three conditions **hard**, and the
+[validator](../capabilities/validator.md) fails a bundle on any of them:
+
+1. **§9.1** — every non-reserved `.md` file has a parseable frontmatter block;
+2. **§9.2** — every such block has a **non-empty `type`**;
+3. **§9.3** — every reserved file present is well-formed.
+
+Everything else is soft guidance a consumer MUST tolerate: missing optional
+fields, unknown [`type`](../model/concept.md) values, and **broken cross-links**.
+Judging those is the [linter](../capabilities/linter.md)'s job, held separate on
+purpose.
+
+# Citations
+
+[1] [SPEC.md](https://github.com/serradura/okf-gem/blob/main/lib/okf/skill/reference/SPEC.md) — the OKF v0.1 specification, authored by Google Cloud Platform, redistributed under Apache 2.0.

data/.okf/index.md

@@ -0,0 +1,18 @@
+---
+okf_version: "0.1"
+---
+
+# okf-gem capabilities
+
+What the `okf` gem does over an Open Knowledge Format v0.1 bundle: read it,
+validate it, lint it, serve it, and let an agent author it. Start here.
+
+* [Overview](overview.md) - the gem at a glance: the five capabilities and the design ethos behind them.
+* [Command line](cli.md) - the `okf` executable — the one layer that parses argv, prints, and exits.
+
+# Areas
+
+* [The format](format/) - what OKF v0.1 is — the Markdown + YAML frontmatter the gem operates on.
+* [The model](model/) - the pure in-memory data structures: concept, bundle, graph.
+* [Capabilities](capabilities/) - the five things the gem does: validate, lint, serve, the library, the skill.
+* [Design constraints](design/) - the enforced boundaries that keep the gem light and honest.

data/.okf/log.md

@@ -0,0 +1,9 @@
+# Update Log
+
+## 2026-07-12
+* **Sync**: caught the bundle up with the CLI at 1.0.0 — documented the new `index` command (the §6 progressive-disclosure map, the read view that sees the reserved `index.md` layer), compact-by-default JSON with `--pretty`, and `--fields`/`--except` projection on the list views, in [read views](capabilities/read-views.md) plus the `index`-verb enumerations in the [CLI](cli.md), the [overview](overview.md), and the [capabilities](capabilities/) index listing.
+
+## 2026-07-11
+* **Creation**: seeded the bundle documenting okf-gem's capabilities at version 0.1.0 — the [overview](overview.md), the [CLI](cli.md), and the [format](format/), [model](model/), [capabilities](capabilities/), and [design](design/) areas.
+* **Update**: added Mermaid diagrams (tagged `diagram`) to five concepts — [overview](overview.md), the [core/shell split](design/core-shell-split.md), the [graph server](capabilities/graph-server.md), the [library API](capabilities/library-api.md), and [cross-links](format/cross-links.md).
+* **Sync**: caught the bundle up with the CLI — documented the new `types` command, the cross-view `--type`/`--area`/`--tag` filters, and `tags --by type|area` in [read views](capabilities/read-views.md), the [CLI](cli.md) front end, the [graph](model/graph.md) indexes, and the [capabilities](capabilities/) index listing.

data/.okf/model/bundle.md

@@ -0,0 +1,38 @@
+---
+type: Component
+title: OKF::Bundle
+description: The pure in-memory collection of concepts that validate, lint, and graph run over.
+resource: lib/okf/bundle.rb
+tags: [model, bundle, pure]
+timestamp: 2026-07-11T12:00:00Z
+---
+
+# Overview
+
+`OKF::Bundle` is a set of [concepts](concept.md) held together in memory, with no
+disk involved. It is the object the three judging capabilities operate on:
+`#validate`, `#lint`, and `#graph` each hand the bundle to a dedicated pure
+class and return a result. A bundle also carries the reserved files
+(`index.md`, `log.md`) and — importantly — an `unparseable` list.
+
+# Best-effort by construction
+
+When a bundle is built from disk, files that fail to parse do not vanish and do
+not abort the build: they are collected in `bundle.unparseable`. That is what
+lets [graph](graph.md), the [server](../capabilities/graph-server.md), and the
+[read views](../capabilities/read-views.md) render everything that *is* valid
+while the [CLI](../cli.md) notes the skips on stderr — §9's best-effort posture,
+made structural.
+
+# Build it from data, not only from files
+
+Because the bundle is pure, an embedding application can construct concepts
+straight from its own records — no Markdown round-trip — and still get validate,
+lint, and graph for free. This is the surface the
+[library API](../capabilities/library-api.md) exposes to, say, a Rails store that
+already holds knowledge as rows. It also feeds the shared `#catalog`, the data
+behind every read view.
+
+# Citations
+
+[1] [lib/okf/bundle.rb](https://github.com/serradura/okf-gem/blob/main/lib/okf/bundle.rb) — the in-memory collection and its `#validate` / `#lint` / `#graph` entry points.

data/.okf/model/concept.md

@@ -0,0 +1,44 @@
+---
+type: Component
+title: OKF::Concept
+description: The pure in-memory model of a single OKF file — frontmatter, body, and a stable id.
+resource: lib/okf/concept.rb
+tags: [model, concept, pure]
+timestamp: 2026-07-11T12:00:00Z
+---
+
+# Overview
+
+`OKF::Concept` is the atomic node: a `path`, a parsed
+[`frontmatter`](../format/frontmatter.md) hash, and a Markdown `body`. It is
+[pure](../design/core-shell-split.md) — it holds no file handle and does no I/O.
+The on-disk counterpart is `OKF::Concept::File`, part of the
+[library API](../capabilities/library-api.md).
+
+# The id is the concept's identity
+
+`#id` is the `path` minus `.md` (e.g. `model/graph.md` → `model/graph`). That id
+is the concept's **stable identifier** across the whole system — it is the graph
+node key, the link target, and the thing you name a concept for. Name a file for
+what it *is*, not where it sits, because the id follows the path.
+
+# What it derives from its own content
+
+The concept parses its body on demand into the structural facts the rest of the
+gem consumes:
+
+- `#type`, `#title`, `#description`, `#resource`, `#tags`, `#timestamp` — typed
+  reads over the frontmatter;
+- `#links` — the bundle-relative [cross-links](../format/cross-links.md) (edges);
+- `#external_links` — URLs and `mailto:` (not edges);
+- `#citations` — the [`# Citations`](../format/citations.md) entries;
+- `#to_markdown` — the inverse of the frontmatter parser;
+- `#lint` — the concept-scoped [lint](../capabilities/linter.md) checks in isolation.
+
+A concept never decides conformance alone; a [bundle](bundle.md) does, because
+some checks (duplicate titles, missing link targets) are only meaningful across
+the set.
+
+# Citations
+
+[1] [lib/okf/concept.rb](https://github.com/serradura/okf-gem/blob/main/lib/okf/concept.rb) — the pure concept model.

data/.okf/model/graph.md

@@ -0,0 +1,44 @@
+---
+type: Component
+title: OKF::Bundle::Graph
+description: The in-memory knowledge graph — concepts as nodes, cross-links as directed edges, with type and tag indexes.
+resource: lib/okf/bundle/graph.rb
+tags: [model, graph, pure]
+timestamp: 2026-07-11T21:40:00Z
+---
+
+# Overview
+
+`OKF::Bundle::Graph` turns a [bundle](bundle.md) into nodes and edges:
+[concepts](concept.md) become nodes keyed by id, and bundle-relative
+[cross-links](../format/cross-links.md) become directed edges. It is pure — it
+carries no presentation concerns; sizing and colour belong to a renderer like
+the [graph server](../capabilities/graph-server.md).
+
+# Fidelity is a build option
+
+The same graph ships at three weights, so a client downloads only what it needs
+and fetches the rest on demand:
+
+| Build | Node payload |
+|-------|--------------|
+| default (`body: true`) | id, type, title, description, tags, **body** |
+| `body: false` | everything but the body |
+| `minimal: true` | just id and title — the leanest payload to draw |
+
+# Indexes come free at every weight
+
+Regardless of node fidelity, the graph exposes two inverted indexes computed from
+every concept:
+
+- `type_index` — `{ type => [id, …] }`, so even a minimal client can colour nodes
+  by [`type`](concept.md);
+- `tag_index` — `{ tag => [id, …] }`, so it can filter by tag.
+
+Those indexes, plus `unlinked_ids` (degree-0 nodes), are what the
+[read views](../capabilities/read-views.md) — `types`, `tags`, `stats`, `loose`
+— are built from, and what their `--type`/`--area`/`--tag` filters match against.
+
+# Citations
+
+[1] [lib/okf/bundle/graph.rb](https://github.com/serradura/okf-gem/blob/main/lib/okf/bundle/graph.rb) — graph construction and the type/tag indexes.

data/.okf/model/index.md

@@ -0,0 +1,8 @@
+# The model
+
+The pure, in-memory data structures the gem builds a bundle out of — no disk, no
+stdio. Everything else reads or renders these.
+
+* [Concept](concept.md) - one file's worth of knowledge: frontmatter plus body, with a stable id.
+* [Bundle](bundle.md) - a collection of concepts you validate, lint, and graph.
+* [Graph](graph.md) - concepts as nodes, cross-links as edges, plus type and tag indexes.

data/.okf/overview.md

@@ -0,0 +1,66 @@
+---
+type: Overview
+title: okf-gem at a glance
+description: A light Ruby gem that reads, validates, lints, and serves Open Knowledge Format v0.1 bundles.
+tags: [okf, gem, overview, diagram]
+timestamp: 2026-07-12T12:00:00Z
+---
+
+# Overview
+
+**okf-gem** — `okf` on RubyGems — operates on [OKF v0.1](format/okf-format.md)
+bundles: directories of Markdown files with YAML frontmatter that humans and
+agents both read from one source. It does not define new knowledge storage; it
+gives you leverage over knowledge that already lives as Markdown.
+
+```mermaid
+flowchart LR
+  skill["companion<br/>agent skill"] -. authors .-> bundle[("OKF v0.1 bundle<br/>Markdown + YAML")]
+  bundle --> model["pure model<br/>Concept · Bundle · Graph"]
+  subgraph cli ["okf CLI"]
+    validate["validate — legal? §9"]
+    lint["lint — well-curated?"]
+    server["server — explore"]
+  end
+  model --> cli
+  model --> library["library API<br/>embed in Ruby"]
+```
+
+Over such a bundle the gem gives you five capabilities behind one
+[command-line tool](cli.md):
+
+| Capability | What it answers | Verb |
+|------------|-----------------|------|
+| [Conformance validator](capabilities/validator.md) | Is this a legal OKF bundle? (§9) | `validate` |
+| [Curation linter](capabilities/linter.md) | Is it navigable, complete, fresh? | `lint` / `loose` |
+| [Interactive graph server](capabilities/graph-server.md) | Can I explore it visually? | `server` |
+| [Library API](capabilities/library-api.md) | Can my Ruby program use it? | (in-process) |
+| [Companion agent skill](capabilities/agent-skill.md) | Can an agent author it? | `skill` |
+
+Alongside those, a family of [read views](capabilities/read-views.md) —
+`index`, `catalog`, `files`, `tags`, `stats`, `graph` — print the bundle at a
+glance so an agent reads it without a browser.
+
+# The two ideas it inherits from the format
+
+- **Dual audience.** Every file serves a human skimming it *and* an agent
+  extracting from it, so bodies are structural Markdown and
+  [links](format/cross-links.md) are plain Markdown links — both readers already
+  understand them.
+- **The graph is emergent.** Files are nodes, Markdown links are edges. You never
+  declare a graph; the gem [builds one](model/graph.md) from how concepts link.
+
+# Design ethos
+
+The gem is deliberately light so it runs on the Ruby an OS already ships. That
+ethos is not incidental — it is enforced by [hard constraints](design/):
+a [Ruby 2.4 floor](design/ruby-floor.md), exactly
+[two runtime dependencies](design/runtime-dependencies.md), and a
+[core/shell split](design/core-shell-split.md) that keeps all logic pure and
+testable without disk. Everything else — no ActiveSupport, no build step, no
+JavaScript toolchain — follows from those.
+
+# Citations
+
+[1] [README.md](https://github.com/serradura/okf-gem/blob/main/README.md) — the gem's own overview.
+[2] [AGENTS.md](https://github.com/serradura/okf-gem/blob/main/AGENTS.md) — the maintainer guide.

data/CHANGELOG.md

@@ -0,0 +1,54 @@
+# Changelog
+
+## [1.0.0] - 2026-07-12
+
+Initial release.
+
+- `OKF::Concept` / `OKF::Bundle`: pure in-memory model of an OKF v0.1 bundle,
+  buildable straight from data (no disk) with link, citation, and markdown
+  round-trip primitives.
+- `OKF::Bundle::Validator`: the spec §9 conformance gate (hard errors) with the
+  spec's soft guidance reported as warnings — broken cross-links are tolerated,
+  as §5.3 requires.
+- `OKF::Bundle::Linter`: advisory curation-quality report across reachability,
+  backlog, completeness, freshness, provenance, and hygiene, with `--json` as a
+  machine substrate.
+- `OKF::Bundle::Graph`: the knowledge graph (nodes, edges, type/tag indexes) at
+  selectable fidelity.
+- On-disk handles: `OKF::Bundle::Folder`, `OKF::Bundle::Reader`,
+  `OKF::Bundle::Writer` (atomic, validate-before-publish), and
+  `OKF::Concept::File`.
+- `OKF::Server::App`: the interactive graph as a mountable Rack app — five views
+  (graph, catalog, files, tags, stats) with type/area/tag filtering throughout,
+  bodies fetched live from disk — served by a built-in WEBrick runner
+  (`okf server`).
+- `okf` CLI: `validate`, `lint`, `loose`, and `graph`, plus the read views as
+  text — `index`, `catalog`, `files`, `tags`, `types`, `stats` — at full parity
+  with the browser: every list view narrows with `--type`/`--area`/`--tag`
+  (case-insensitive; the bundle root is area `(root)`, accepted as `root`), and
+  `tags --by type|area` regroups the tag index per concept dimension with
+  within-group counts — the tag-curation view. `server` boots the graph page;
+  `skill` installs the companion skill.
+- `okf index`: a read view over the progressive-disclosure layer (spec §6) — one
+  entry per directory that holds concepts or carries an `index.md`, root first,
+  with its authored index body (frontmatter stripped), a type/tag rollup over the
+  concepts that live there, its child directories, and the concept listing. A
+  directory with concepts but no `index.md` has its listing synthesized (§6 permits
+  it) and is flagged. `--area` (repeatable), `--no-body`, and `--json`; advisory,
+  always exit 0. Backed by the pure `OKF::Bundle#directory_index`.
+- JSON output is **compact by default** across every emitting verb (the
+  token-efficient machine substrate, matching the server); `--pretty` indents it
+  for reading and implies `--json`. JSON semantics are identical either way — only
+  whitespace differs — so any parser is unaffected.
+- JSON property projection on the list views: `index`, `catalog`, and `files`
+  take `--fields a,b` (emit only these properties) or `--except a,b` (emit all but
+  these), so an agent never pays tokens for fields it will not read. The flags are
+  mutually exclusive, imply `--json`, match property names case-insensitively, and
+  reject an unknown name (exit 2) listing the valid ones; `okf index --no-body` is
+  shorthand for dropping the `body` field.
+- Bundled companion agent skill (`okf skill <dest>`): SKILL.md carrying the
+  judgment (the CLI surface stays self-describing via `--help`) — including the
+  orient-before-you-read protocol and the CLI/judgment boundary — the OKF v0.1
+  spec, authoring and CLI references (tag-vocabulary curation, the SPEC-section
+  map, the closeout gate), and concept/index/log templates.
+- Runs on Ruby >= 2.4 with two runtime dependencies: rack and webrick.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+# Code of Conduct
+
+"okf" follows [The Ruby Community Conduct Guideline](https://www.ruby-lang.org/en/conduct) in all "collaborative space", which is defined as community communications channels (such as mailing lists, submitted patches, commit comments, etc.):
+
+* Participants will be tolerant of opposing views.
+* Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
+* When interpreting the words and actions of others, participants should always assume good intentions.
+* Behaviour which can be reasonably considered harassment will not be tolerated.
+
+If you have any concerns about behaviour within this project, please contact us at ["rodrigo.serradura@gmail.com"](mailto:"rodrigo.serradura@gmail.com").

data/LICENSE.txt

@@ -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 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 Rodrigo Serradura
+
+   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.