narrative-harm-classifier 0.1.0__tar.gz

narrative_harm_classifier-0.1.0/.env.example

@@ -0,0 +1,32 @@
+# --- App ---
+APP_NAME=Narrative Harm Classifier
+DEBUG=false
+
+# --- Azure Text Analytics ---
+# Get from Azure Portal → Cognitive Services → Text Analytics
+AZURE_TEXT_ANALYTICS_ENDPOINT=https://<your-resource>.cognitiveservices.azure.com/
+AZURE_TEXT_ANALYTICS_KEY=<your-key>
+
+# --- Azure Storage (optional — for audit log persistence) ---
+AZURE_STORAGE_CONNECTION_STRING=DefaultEndpointsProtocol=https;AccountName=...
+AZURE_STORAGE_CONTAINER=classifications
+
+# --- Database (Postgres/Azure SQL in prod, SQLite for local dev) ---
+DATABASE_URL=sqlite:///./dev.db
+# DATABASE_URL=postgresql://<user>:<pass>@<host>:5432/<db>
+# DATABASE_URL=mssql+pyodbc://<user>:<pass>@<server>.database.windows.net/<db>?driver=ODBC+Driver+18+for+SQL+Server
+
+# --- Escalation tracking (defaults to DATABASE_URL when unset) ---
+TRACKING_DB_URL=sqlite:///./tracking.db
+
+# --- Classification ---
+# TAXONOMY_CONFIG_PATH, BENCHMARK_TEMPLATES_PATH, PATTERNS_DIR, DOGWHISTLES_PATH, and
+# I18N_SMOKE_TESTS_PATH all default to the files shipped inside the installed package —
+# only set these to override with your own.
+# TAXONOMY_CONFIG_PATH=/path/to/custom_taxonomy.yaml
+# BENCHMARK_TEMPLATES_PATH=/path/to/custom_benchmark_templates.yaml
+# PATTERNS_DIR=/path/to/custom_patterns_dir
+# DOGWHISTLES_PATH=/path/to/custom_dogwhistles.yaml
+# I18N_SMOKE_TESTS_PATH=/path/to/custom_i18n_smoke_tests.yaml
+TAXONOMY_VERSION=1.0.0
+DEFAULT_CONFIDENCE_THRESHOLD=0.65

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

@@ -0,0 +1,52 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install package (dev extras)
+        run: pip install -e ".[dev]"
+
+      - name: Run unit + integration + API tests with coverage
+        run: |
+          pytest tests/unit tests/integration tests/api -v \
+            --cov=narrative_harm_classifier --cov-report=term-missing --cov-fail-under=80
+
+      - name: Print benchmark report (human-readable summary alongside the gate below)
+        run: python -m narrative_harm_classifier.cli benchmark run
+
+      - name: Enforce benchmark gate (precision 1.0 / recall 1.0 / FPR 0.0, full cross-group consistency)
+        run: pytest tests/benchmark -v
+
+  milestone-gate:
+    runs-on: ubuntu-latest
+    needs: test
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install package (dev extras)
+        run: pip install -e ".[dev]"
+
+      - name: Enforce Phase 1 milestone gate (dehumanization precision/recall/FPR)
+        run: pytest tests/integration/test_validation.py -v

narrative_harm_classifier-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,50 @@
+name: Publish to PyPI
+
+# Triggers on a GitHub Release being published, or manually via the Actions
+# tab. Uses PyPI Trusted Publishing (OIDC) — no API token is stored in this
+# repo. One-time setup required on pypi.org before this will work: create
+# the project (or its first release manually) and add this repo/workflow as
+# a "trusted publisher" under the project's Publishing settings.
+on:
+  release:
+    types: [published]
+  workflow_dispatch: {}
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: pip install build
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # required for PyPI Trusted Publishing
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

narrative_harm_classifier-0.1.0/.gitignore

@@ -0,0 +1,22 @@
+# Python
+__pycache__/
+*.pyc
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+
+# Env / secrets
+.env
+
+# Local data
+*.db
+*.sqlite3
+.coverage
+htmlcov/
+
+# Editors / OS
+.vscode/
+.idea/
+.DS_Store

narrative_harm_classifier-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,159 @@
+# Contributing
+
+## Setup
+
+```bash
+git clone https://github.com/HenryMorganDibie/narrative-harm-classifier.git
+cd narrative-harm-classifier
+python -m venv .venv && source .venv/bin/activate   # or .venv\Scripts\activate on Windows
+pip install -e ".[dev]"
+pytest tests/ -v
+```
+
+## Architecture overview
+
+- `classifier/factory.py` — the single place that constructs a `ClassificationEngine`/`EscalationTracker`/
+  `BenchmarkRunner`/`PerformanceValidator`. Every API route and CLI command goes through this instead of
+  reconstructing dependencies itself — if you're adding a new route or command that needs the engine, use
+  `build_engine(settings)` rather than wiring `load_taxonomy` + `AzureNLPClient` + `ClassificationEngine`
+  by hand again.
+- `classifier/rules/patterns_loader.py` — loads and precompiles a language's vocabulary
+  (`data/patterns/<lang>.yaml`) into a `LanguagePatterns` object. `classifier/rules/engine.py` is
+  language-agnostic; all per-language vocabulary lives in data, not code.
+- `classifier/rules/dogwhistles.py` and `classifier/counter_narrative.py` and `classifier/provenance.py`
+  are small, focused modules — see their docstrings and the corresponding README sections
+  ([Dog-whistle lexicon](README.md#dog-whistle-lexicon-in-depth),
+  [Counter-narrative guidance](README.md#counter-narrative-guidance),
+  [Provenance & tamper-evidence](README.md#provenance--tamper-evidence-in-depth)).
+
+## Adding a taxonomy row
+
+Taxonomy rows live in `narrative_harm_classifier/data/taxonomy_v1.yaml`. Each row needs a `row_id`,
+`target_type`, `harm_mechanism`, `identity_axis`, `signal_weight`, and `decision_threshold`. Corresponding
+regex patterns for a new `harm_mechanism` go under `harm_patterns` in each language file under
+`narrative_harm_classifier/data/patterns/` (at minimum `en.yaml` — a harm mechanism only checked in some
+languages will simply never fire in the others until someone adds it there too).
+
+If a new `harm_mechanism` should participate in escalation tracking, add it to
+`HARM_MECHANISM_SEVERITY` in `narrative_harm_classifier/classifier/tracking/models.py` so it maps to a
+severity level.
+
+## Adding or improving a language
+
+Each language is one file: `narrative_harm_classifier/data/patterns/<iso-639-1-code>.yaml`. Copy an
+existing file's structure — `identity_anchors` and `harm_patterns` are regex pattern lists per
+axis/mechanism; `negation_cues`, `reporting_cues`, `condemnation_cues`, and `benign_context_cues` are
+plain literal phrase lists (no regex syntax needed — they're auto-escaped and combined); `obfuscation_map`
+is a character-substitution table for Latin-script leetspeak evasion (leave it `{}` for non-Latin
+scripts, where that specific evasion technique doesn't apply).
+
+Set `confidence: verified` only if you're confident in the vocabulary's correctness (ideally with
+native-speaker review); otherwise use `confidence: experimental` — this is surfaced directly to API
+consumers via `language_confidence`, so it's not just a label, don't set it to `verified` optimistically.
+
+**A structural pitfall to check for, found while building the Arabic vocabulary**: languages where
+articles, plurals, or other morphology attach directly to a word with no space (Arabic's `ال` definite
+article, for example) will silently fail to match a plain `\b(word)\b` pattern on the attached form —
+`\bمسلم\b` never matches inside `المسلمون`. If your language has this property, make sure patterns account
+for it explicitly (see the comment at the top of `ar.yaml`) rather than assuming `\b` alone is enough.
+
+Add a few cases to `narrative_harm_classifier/data/i18n_smoke_tests.yaml` for your language and run
+`nhc benchmark i18n` (or `pytest tests/unit/test_i18n_smoke.py`) to confirm basic detection works.
+
+## Adding a dog-whistle entry
+
+Entries live in `narrative_harm_classifier/data/dogwhistles.yaml`. Each needs a `term`, `harm_mechanism`,
+`identity_axis`, `signal_weight`, `decision_threshold` (both below 1.0, with headroom between them the
+same way taxonomy rows work), and a `source_note` citing where the term is publicly documented (ADL Hate
+Symbols Database, SPLC, or academic literature on coded hate speech) — this lexicon only takes
+well-documented terms with a citable source, not personal judgment calls about what sounds coded. Use a
+lower `signal_weight`/`decision_threshold` for ambiguous terms with legitimate non-bigoted uses, and a
+higher one for unambiguous, purpose-built coded terms (numeric codes, explicit slogans).
+
+## Adding a benchmark case
+
+Benchmark templates live in `narrative_harm_classifier/data/benchmark_templates.yaml`.
+
+- To test a new phrasing for an existing harm mechanism, add a template with a `{group}` placeholder — it
+  will automatically be expanded across every group in the `groups` list, which also feeds the
+  cross-group-consistency check.
+- To add a one-off hard negative that shouldn't be slot-filled, add it to `standalone_cases` instead.
+- Every template/case needs a `test_type` (`explicit_positive`, `implicit_positive`, `negation`,
+  `counter_speech`, `obfuscated_spelling`, or `benign_trigger_word`) so regressions in a specific capability
+  are visible in the per-test-type breakdown, not just the aggregate.
+
+Run `nhc benchmark run` (or `pytest tests/benchmark -v`) to see the effect of your change.
+
+## CI gate
+
+Pull requests run the full test suite plus the Phase 1 milestone gate
+(`tests/integration/test_validation.py`), which fails the build if the dehumanization category's
+precision/recall/FPR regress below the thresholds in `taxonomy_v1.yaml`. `tests/benchmark/` asserts the
+templated benchmark suite stays at precision 1.0 / recall 1.0 / FPR 0.0 overall and 100% cross-group
+consistency — this **is** a hard gate: a PR that regresses any of those numbers fails CI. CI also enforces
+a minimum 80% coverage (`--cov-fail-under=80`) across `tests/unit tests/integration tests/api`.
+
+## Coverage badge
+
+The coverage badge in the README is a static number (currently ~90%), captured from a real
+`pytest --cov` run at the time it was last updated — it is **not** a live badge that recalculates itself
+on every push. If you add or remove a meaningful chunk of tested code, regenerate it:
+
+```bash
+pytest tests/unit tests/integration tests/api --cov=narrative_harm_classifier --cov-report=term-missing
+```
+
+and update the percentage in the badge URL in `README.md`. (A live-updating badge would need a service
+like Codecov, which requires the maintainer to connect the repo on codecov.io — not set up here yet.)
+
+## Performance numbers
+
+The numbers in the README's [Performance](README.md#performance) section come from running
+[`scripts/measure_performance.py`](scripts/measure_performance.py) — re-run it and update the table if
+you change anything in the hot classification path (`classifier/rules/engine.py`).
+
+## How the engine handles negation, counter-speech, and obfuscation
+
+The engine is still a regex/rule engine, not a trained model — these are handled with explainable
+heuristics in the suppression pipeline (`_rule_negation`, `_rule_counter_speech`, `_rule_benign_context`
+in `narrative_harm_classifier/classifier/rules/engine.py`), reading their cue lists/maps from the active
+language's `LanguagePatterns` (`data/patterns/<lang>.yaml`) rather than understanding language in general:
+
+- **Negation** — a matched harm pattern is discarded if a `negation_cues` entry (`not`, `never`, `isn't`,
+  `false that`, ...) appears in the ~60 characters immediately before the match. This is a local window,
+  not full-sentence parsing, so it can be evaded by negation placed far from the trigger word, or fooled
+  by an unrelated negation word elsewhere in a long sentence.
+- **Counter-speech** — a match is discarded only when the text contains *both* a `reporting_cues` entry
+  ("some say", "calling", "rhetoric claiming", ...) *and* a `condemnation_cues` entry ("dangerous",
+  "bigoted", "led to violence", ...). Requiring both reduces false suppression, but a genuinely harmful
+  post that happens to use one of these words in a non-condemning way could still slip through.
+- **Obfuscated spelling** — each language's `obfuscation_map` (a character-substitution table, e.g.
+  `0→o`, `1→i`, `3→e` for English/Spanish/French) is applied and matched alongside the original text. It
+  only reverses substitutions in that map — homoglyphs, spacing tricks (`v e r m i n`), or substitutions
+  outside the map will not be caught until someone extends the map for that language. Non-Latin-script
+  languages (Russian, Arabic) currently have an empty map since Latin-style digit-substitution doesn't
+  apply the same way — a real gap for whatever the equivalent evasion technique is in those scripts.
+- **Benign-context override** — a language's `benign_context_cues` (pest control, wildlife, film,
+  academic theory, ...) suppress a match when present, so a trigger word discussed in an unrelated
+  literal context doesn't get flagged just because a group is also named nearby. This is a coarse
+  allowlist, not sarcasm/context understanding — it covers the specific hard-negative categories in the
+  benchmark, not every possible benign context.
+
+Only English, Spanish, French, Russian, and Arabic have these cue lists populated; Igbo, Yoruba, and
+Hausa intentionally have them empty (see [Multilingual support](README.md#multilingual-support-in-depth))
+rather than guessed.
+
+**If you find real-world text that evades one of these** (and you will — this is fundamentally a
+keyword/heuristic system, not semantic understanding), the fix is almost always to extend the relevant
+cue list/map in that language's YAML file, or add a new `harm_patterns` entry, then add a benchmark case
+for it so the gap can't silently regress. That's the highest-value kind of contribution here: the
+benchmark passing cleanly today means it's clean against *this* test suite, not that evasion is a solved
+problem in general.
+
+## Database schema changes (pre-1.0)
+
+`classifier/tracking/store.py` uses `metadata.create_all()`, which creates missing tables but does **not**
+alter existing ones. If you add/rename a column (as the provenance hash-chain fields did), delete your
+local `dev.db`/`tracking.db` rather than expecting an in-place migration — there's no Alembic-style
+migration system yet, which is a reasonable gap pre-1.0 but will need addressing before this is used
+somewhere a real schema migration matters.

narrative_harm_classifier-0.1.0/Dockerfile

@@ -0,0 +1,12 @@
+FROM python:3.12-slim
+
+WORKDIR /app
+
+COPY pyproject.toml README.md ./
+COPY narrative_harm_classifier ./narrative_harm_classifier
+
+RUN pip install --no-cache-dir .
+
+EXPOSE 8000
+
+CMD ["nhc", "serve", "--host", "0.0.0.0", "--port", "8000"]

narrative_harm_classifier-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 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 Henry Morgan Dibie
+
+   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.