okf-pro 1.0.0

data/.okf/testing/fixture-is-a-client.md

@@ -0,0 +1,35 @@
+---
+type: Learning
+title: The bundle fixture is a client of the code under test
+description: The bundle fixture computes its own snapshot line by calling the code under test, so a change to the counters reaches every fixture carrying a log day — which bounds what a green ported suite proves.
+---
+
+# Why it calls the code
+
+The fixture writes a real bundle to a temp directory: real frontmatter, real
+indexes, a real board. A mock would test the mock — the checks that matter most
+consult the corpus through `okf validate`, `okf lint` and `okf search`, and none
+of them can be exercised against a stub without exercising the stub instead.
+
+The log day goes further and computes its snapshot line with `Snapshot.line`,
+deliberately: the stop gate verifies counters field by field, and a fixture
+carrying a hand-typed line would drift from its own board exactly the way a
+person's does. Tests *about* drift write their wrong line directly.
+
+# What that costs
+
+It makes the fixture a client. A change to the counters, or to what
+[the read-owed rule](/trust/read-owed-rule.md) counts, reaches every fixture with
+a log day — in the same step where a ported suite running green is supposed to be
+independent proof that the port preserved behaviour.
+
+So "the suite is green, therefore nothing changed" is only true for changes that
+do not touch what the fixture calls. Where a work item does touch it, the
+expected drift is stated in advance and the fixtures are updated as part of that
+item — not discovered afterwards and patched until the suite agrees with itself.
+
+# The general shape
+
+A fixture that computes rather than states is more honest and less independent.
+Both halves are real, and the useful discipline is knowing which changes cross
+the line — not choosing one side permanently.

data/.okf/testing/index.md

@@ -0,0 +1,4 @@
+# Testing
+
+* [drills-over-units](drills-over-units.md) - Every bug in this layer was a gate that passed when it could not do its job.
+* [fixture-is-a-client](fixture-is-a-client.md) - The bundle fixture calls the code under test, so "the ported suite is unchanged proof" has a limit.

data/.okf/trust/index.md

@@ -0,0 +1,7 @@
+# Trust
+
+The v0.2 vocabulary this gem's policy is written in, and the one rule four call
+sites have to agree about.
+
+* [read-owed-rule](read-owed-rule.md) - Only a human discharges the owner's read, and four sites must say so together.
+* [scalar-verified](scalar-verified.md) - The grammar failure that fires the guard, gets approved, and then reads as unverified forever.

data/.okf/trust/read-owed-rule.md

@@ -0,0 +1,45 @@
+---
+type: Decision
+title: A briefing is owed a read until a human has verified it
+description: §5.3's trust tiers replaced a truthiness test on `verified`, and the four call sites that read the rule have to move together or a briefing falls through all of them.
+---
+
+# The rule
+
+```ruby
+awaiting_read?  # declared_generated? && trust_tier != :human_reviewed
+owner_read?     # trust_tier == :human_reviewed
+```
+
+`declared_generated?` is raw-key detection, so it separates hand-written (no
+provenance at all) from v0.1-with-a-`timestamp`, which the old
+`frontmatter["generated"]` test conflated with okf's own fallback.
+`trust_tier` reads §5.3: no `verified` is unverified, a `process:` or agent
+actor is machine-confirmed, a `human:<id>` actor is human-reviewed.
+
+# Why all four sites move together
+
+Two of them are exact opposites: `unverified_ids` says *the board still owes
+this a To-read line*, `verified_reference_targets` says *the line can go*. Two
+more read the same rule for different audiences: `Attestation.report`
+corpus-wide, and the snapshot's `unverified briefings` counter.
+
+Testing `verified` for truthiness made a nightly `process:`-verified briefing
+simultaneously **awaiting the owner's read** to one caller and **verified, drop
+the line** to the other. The board line vanished, and the read was never owed to
+anyone again. Moving one site and not the other manufactures exactly that state,
+which is why the rule is stated once, in one comment, over both predicates.
+
+# What changed for an adopting bundle
+
+`Snapshot.counters["unverified briefings"]` changes meaning, and the stop gate
+verifies that counter field by field — so every log line in a bundle written
+against the old rule goes stale on upgrade. That is a migration note, not a bug:
+the counter is now answering a better question.
+
+# The general shape
+
+When a derived value is read by several call sites and each re-derives it from
+raw fields, the sites do not drift *gradually*. They diverge the first time the
+underlying vocabulary gains a case none of them was written for — and the divergence
+is silent, because each site is individually correct about the field it reads.

data/.okf/trust/scalar-verified.md

@@ -0,0 +1,48 @@
+---
+type: Finding
+title: A scalar `verified:` fails in the worst available direction
+description: The guard fires on the word, the owner approves, and then the reader drops the malformed value — so the concept stays unverified and the To-read line is demanded forever.
+---
+
+# The sequence
+
+```yaml
+verified: human:rod        # a scalar; §5.2 wants a mapping or a list of them
+```
+
+1. `Guards.attests?` matches on the word `verified:` and routes the write to the
+   owner for approval. It is deliberately generous — this gate **asks**, so a
+   false positive costs one prompt and a miss costs a forged signature.
+2. The owner approves. From their side, the attestation happened.
+3. `Concept#verified` drops the entry, because it is not a mapping. The tier
+   stays `:unverified`.
+4. The To-read line is demanded forever, and the owner is told repeatedly to
+   read something they already read and signed.
+
+# The fix is one line, in the right place
+
+`okf validate` already says exactly what is wrong — *verified should be a
+mapping or a list of mappings* — as a **warning**, because §9 forbids the
+validator from rejecting a soft problem. `Conformance.check` read
+`result.errors` only, and dropped every warning on the floor.
+
+Surfacing `result.warnings` fixes the whole class. The alternative — a
+check of our own for the trust family's grammar — would be a second parser to
+keep in step with okf's, which is how the two spellings of one rule start
+disagreeing.
+
+They are surfaced as advice, not as errors: §9's separation between conformance
+and curation is the kernel's, and a gate that promoted the validator's warnings
+would be overruling it from outside.
+
+It is the same failure class as [the skipped checks](/contract/silent-skips.md)
+and for the same reason: a report that says "fine" over a question nobody
+answered. And it lands on [the read-owed rule](/trust/read-owed-rule.md), which
+is where being wrong costs the owner a demand they already discharged.
+
+# The general shape
+
+The most dangerous validation failure is not the one that rejects. It is the one
+where a permissive *detector* and a strict *parser* disagree — the detector
+fires, a human confirms, and the parser discards. Everyone downstream then has
+positive evidence that the thing happened, and the stored state says it did not.

data/CHANGELOG.md

@@ -0,0 +1,187 @@
+# Changelog
+
+All notable changes to okf-pro are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this gem uses
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-08-17
+
+First release. okf-pro begins as a working prototype — a checker carried inside
+a template repository that was cloned to start a knowledge bundle — and becomes
+a gem entered through okf's plugin seam. The template is now something `okf pro
+setup` writes, rather than a repository to fork.
+
+The prototype's surface was gates and nothing else: every verb a check, a
+report, or a one-time generator. Nothing answered *what is on the board* and
+nothing wrote a line, so an agent working in a seeded bundle rediscovered state
+by reading raw markdown and reconstructed a line's grammar from the guides on
+every use. This surface answers both.
+
+### Added
+
+- **`okf pro setup [DIR]`** — writes the bundle and the governance around it:
+  the Claude Code hooks behind a fail-closed wrapper, a `pre-commit` hook that
+  audits the *staged* tree, a CI workflow, the agent skill, `CLAUDE.md`, a
+  `README.md`, a `.gitignore`, and a blank-slate `.okf/`. It writes what it can
+  and never refuses wholesale: a file you already have is left alone and the
+  template's version is staged beside it as `<path>.okf-pro-new`. The one thing
+  it refuses outright is a directory that is *already* a bundle at its own root,
+  which writing `.okf/` beside would turn into two roots the three doors
+  disagree about — a bare `index.md` is a docs index, not a bundle, and is not
+  refused.
+  Both generated doors prove the checker's **identity** before trusting its exit
+  status: a stray `okf` on PATH that exits 0 is indistinguishable from a clean
+  gate, so the wrapper and the `pre-commit` hook each require the enforcer's
+  marker.
+- **`okf pro upgrade [DIR]`** — rewrites the four files the gem owns (the hook
+  wrapper, the pre-commit hook, the workflow, the skill) and leaves every seeded
+  file byte-identical. Those four carry the contract and must track the gem;
+  everything else is yours from the moment it is written.
+- **`okf pro hook <check>`** — one gate against one hook event on stdin.
+  Eight checks plus the session banner: the attestation guard, the journal
+  guard, the shell guard, conformance, the in-flight cap, reconciliation search,
+  the composed post-edit pass, and the stop gate.
+- **`okf pro audit [DIR]`** — every invariant at once, for CI: the closed core,
+  conformance, the board's grammar, the board↔work pairing in both directions,
+  and the day's snapshot. It runs the linter with a clock, so nothing is
+  silently skipped, and confesses anything it still could not run rather than
+  reporting clean over it.
+- **`okf pro records [DIR]`** — asks git whether the staged commit rewrites a
+  past journal day: a modification, a deletion, a rename or a **typechange**,
+  that last being how replacing a day with a symlink hides from the first
+  three. Records are append-only; corrections go in today's entry.
+- **`okf pro snapshot [DIR]`** — computes the day's counter line and prints it.
+  It never writes: this is a checker, not a generator.
+- **`okf pro unverified [DIR]`** — the concepts still awaiting the owner's
+  read, with the trust tier each one has reached.
+- **`okf pro state [DIR]`** — what is on the board, in one call: every section
+  counter, the budget face, deadlines nothing is in flight against, the newest
+  logged day, whether today's journal is open, and the open projects. Cheap by
+  contract — it reads `board.md`, `log.md` and two globs and parses no concept.
+  `--full` adds the corpus-derived parts (the pairing invariants, the
+  attestation list, the live unverified count) behind one bundle parse.
+- **`okf pro board [DIR]`** — one row per board line: section, text, the two
+  date shapes the counters read, age in days, and bundle links. `--section NAME`
+  narrows it, and a section the board does not have is exit 2 rather than an
+  empty answer indistinguishable from an empty section.
+- **`okf pro capture "<text>"`** — a dated Inbox line, in the shape the counter
+  reads. Text spanning lines is refused rather than escaped.
+- **`okf pro promote <selector>` / `okf pro demote <selector>`** — a line
+  between Backlog/Inbox and In flight, with the `In flight: k/CAP` header kept
+  truthful in the same write. Promotion past the cap is refused, by Rule 3. A
+  selector is keyed and never positional, refuses on ambiguity, and refuses a
+  name that names nothing: `/` and `/projects` are directories every project
+  sits under, and name none of them.
+- **`okf pro journal open [DIR]`** — today's journal day and its index line.
+  What goes in the day stays yours.
+- **`okf pro close <project> [DIR]`** — the three mechanical closing moves: the
+  marker on the project index, its board lines removed, a dated `log.md` entry.
+  It names the project by its directory name or by the `/projects/<slug>/` link
+  a board line carries, with or without the `index.md`. The fourth move —
+  extracting the durable part to `learnings/` — is judgment, and is reported as
+  owed.
+- **`okf pro friction [DIR]`** — what was done by hand that a verb could do,
+  recorded at two points that were already wired, and grouped by the door as
+  well as the file: an Edit to the board says a verb went unused, a shell
+  redirect at anything says the trust guards were bypassed. `--issue` prints a
+  ready `gh issue create` against this gem's repository, and never runs it —
+  and prints nothing at all when nothing was recorded, rather than a report
+  whose body is an empty list; `--clear` resets a count that is otherwise a
+  lifetime total. The recorder never reports a zero it did not count — a failed
+  write leaves a marker, and an unwritable `.tmp/` is asked about directly. The
+  session banner counts the narrower thing: only rows an `okf pro` verb would
+  answer, because a shell redirect's answer is Edit or Write.
+- **`okf pro skill <DEST>`** — the agent skill on its own, for a repository
+  that wants the rules without the scaffold.
+- **`--json` and `--pretty`** on `state`, `board`, `snapshot`, `unverified` and
+  `friction`. `snapshot --json` carries the rendered line beside the twelve
+  counters; `unverified --json` emits structured rows rather than prose a
+  consumer would have to take apart with a regex.
+- **The conservation guard.** Every write verb computes its new text purely,
+  declares the delta it intends, and is refused with exit 2 — nothing written —
+  if the actual delta differs, in either direction. A line dropped alongside an
+  append is a refusal; so is a claimed change that never happened. `close`
+  touches three files and decides about all of them before it writes any, so a
+  refusal from a later move leaves the earlier ones unwritten.
+- **Preconditions the guard cannot supply.** A conservation check proves a line
+  was not dropped and says nothing about whether the right line was chosen, so
+  the choices are guarded separately: a project name is one directory segment
+  and never a relative path, `close` marks a first line only when it is a
+  markdown heading (an index carrying YAML frontmatter opens with `---`, and
+  appending a marker there destroys the fence while still reading as closed),
+  and a writer refuses a leading dash rather than committing a mistyped flag as
+  a board line — `--` escapes content that really starts with one.
+- **The SessionStart banner is that state block**, carrying the same counters
+  `okf pro state` prints, the last logged Snapshot line whole and labelled by
+  the day it was logged under rather than as live, and a closing line saying to
+  refresh with `okf pro state` instead of re-reading the files. Nothing in it is
+  said twice: state delivered without costing a turn is still state a reader has
+  to get through.
+- **A seeded `README.md`, written for the owner rather than the agent.**
+  `CLAUDE.md` and the skill both address the agent; this is the only file in the
+  generated tree that addresses the person, so it carries what the skill never
+  will — a week showing the system in use, the four habits it structures, the
+  tunable numbers and where they live, how to turn each gate off, what survives
+  removal, and what the layer does not promise. It is agent-first by
+  construction: the reader talks to their agent and the verbs appear in one late
+  section, because an owner can go a week without typing one. Seeded, not
+  gem-owned, so `upgrade` never touches it.
+- **The skill routes to the CLI before it routes to a guide.** `SKILL.md` opens
+  its "What to load" section with a table of what to run instead of what to
+  read, and carries the canonical line shapes inline — the board bullet, the two
+  date grammars, the conflict line, the closure marker. The prototype named
+  `audit` and `unverified` only in `guides/okf-rules.md`, which the index routes
+  to *after* something has broken, and they went unused for exactly that reason.
+
+### Changed from the prototype
+
+- **The trust policy is OKF v0.2's.** "Awaiting the owner's read" is derived
+  from §5.3's trust tiers rather than from a truthiness test on `verified:`.
+  A `human:<id>` verification discharges the read; a `process:` or agent one
+  makes the concept *machine-confirmed* and leaves the read owed.
+
+  **Migration:** `Snapshot`'s `unverified briefings` counter changes meaning, and
+  the stop gate verifies that counter field by field — so every `**Snapshot**`
+  line written under the old rule will be reported as disagreeing with its board.
+  Recompute the current day's line with `okf pro snapshot .`; past days are
+  records and stay as they are.
+
+  **Migration:** `verified:` must be a mapping or a list of mappings, and its
+  `by` must use the §7 actor convention (`human:rod`, not `rod`) to count as a
+  human review. A scalar `verified:` now surfaces the validator's warning
+  instead of being silently dropped.
+- **`freshness` is removed.** `stale_after` is the format's own field and §5.5
+  owns where its boundary falls — a concept is stale when `today >= stale_after`,
+  inclusive, which is a day later than the prototype's own comparison.
+  `okf lint --only expired` answers the question, once, correctly.
+- **The gate no longer reports clean over checks it did not run.** A default
+  lint skips `expired` and `stale`; the clock is now supplied so `expired` runs,
+  `stale` is excluded in source with its reason, and anything okf reports as
+  skipped in future is surfaced rather than discarded.
+- **Both doors surface `okf validate`'s warnings.** They read only the errors,
+  so every soft finding — including a malformed trust block — was dropped. The
+  hook door reports them on every Edit and Write, and `okf pro audit` counts
+  them as findings, exactly as it already counted a linter warning: a
+  conformant-but-malformed `verified:` is caught at the agent's tool boundary,
+  and must not then be waved through by the two doors an edit made in an editor
+  actually passes.
+- **`status: deprecated` is operative.** A reconciliation hit on a concept that
+  is already deprecated says so, instead of inviting the collision to be
+  re-litigated.
+- **The shell guard no longer reads an ASCII arrow as a redirection.** `>` was
+  matched anywhere in a command while the comment above the pattern claimed it
+  was anchored to a position a redirection can occupy. Nothing implemented
+  that, so `grep -rn "a --> b" .okf/` — a read — was routed to the owner as a
+  suspected write, as was every grep for a `<!-- rule: … -->` marker or a quoted
+  Ruby hash. A guard that fires on reads trains the reflex that approves the one
+  prompt that mattered.
+- **The rules stop asking for redundant conformance runs.** The PostToolUse
+  hook runs `okf validate` and `okf lint` in process on every Edit and Write;
+  `guides/okf-rules.md` says so, and asks for a manual run only when you need
+  the detail behind a refusal.
+- **The Ruby floor is 2.4**, okf's own, down from the prototype's 2.7. This code
+  runs in git hooks and CI steps on machines nobody chose.
+- **The `.bin/okf_pro` binary is gone.** `okf pro` is the only door, which is
+  what lets the wrapper refuse anything that is not it.
+
+[1.0.0]: https://github.com/serradura/okf-gem/releases/tag/okf-pro%2Fv1.0.0

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.

data/NOTICE

@@ -0,0 +1,10 @@
+OKF gem
+Copyright (c) 2026 Rodrigo Serradura
+
+Licensed under the Apache License, Version 2.0 (see LICENSE.txt).
+
+This product bundles the Open Knowledge Format (OKF) v0.1 specification
+(lib/okf/skill/reference/SPEC.md), authored by Google Cloud Platform and
+licensed under the Apache License, Version 2.0, Copyright (c) Google LLC.
+Source: https://github.com/GoogleCloudPlatform/knowledge-catalog
+Full license text: lib/okf/skill/reference/APACHE-2.0.txt