chronologia 0.2.9__tar.gz

chronologia-0.2.9/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 2025 TigreGotico
+
+   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.

chronologia-0.2.9/PKG-INFO

@@ -0,0 +1,341 @@
+Metadata-Version: 2.4
+Name: chronologia
+Version: 0.2.9
+Summary: General-purpose calendrical and chronological core: unbounded datetime-compatible dates, half-open time spans, and a JDN calendar/era/regnal/cycle registry.
+Author: TigreGotico
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/TigreGotico/chronologia
+Project-URL: Repository, https://github.com/TigreGotico/chronologia
+Project-URL: Documentation, https://github.com/TigreGotico/chronologia/tree/master/docs
+Project-URL: Issues, https://github.com/TigreGotico/chronologia/issues
+Keywords: calendar,datetime,julian-day,eras,chronology,astronomical-year
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: ovos-number-parser>=0.19.7a2
+Requires-Dist: ovos-spec-tools>=1.5.0a1
+Provides-Extra: test
+Requires-Dist: pytest; extra == "test"
+Requires-Dist: hypothesis>=6.0; extra == "test"
+Requires-Dist: dateparser>=1.1; extra == "test"
+Requires-Dist: build>=1.0; extra == "test"
+Dynamic: license-file
+
+# chronologia
+
+**A Python library that reads dates written by humans and answers
+questions about them — any date, in any calendar, from the age of the
+dinosaurs to next Tuesday.**
+
+It does two things that usually need two libraries: it *understands* a
+date the way a person wrote it ("the 15th of Ramadan 1446", "next
+winter", "66 million years ago") and it *computes* across every system
+of reckoning humans have used. One call turns a phrase into the exact
+stretch of time it refers to:
+
+```python
+from chronologia import extract_timespan
+from datetime import datetime
+
+span, _ = extract_timespan("the 15th of Ramadan 1446", "en",
+                           datetime(2024, 1, 1))
+print(span.start_datetime.date())   # 2025-03-15
+```
+
+That is the whole point of a *span*: a phrase names a stretch of time,
+not an instant.
+
+When a string contains no date at all, `extract_timespan` returns `None`
+(rather than raising), so guard before unpacking on untrusted input:
+
+```python
+result = extract_timespan("no date here", "en", datetime(2024, 1, 1))
+if result is not None:
+    span, _ = result
+```
+
+Ever wondered…
+
+- what day **"the 15th of Ramadan"** falls on this year?
+- why Russia celebrates the **October** Revolution in **November**?
+- when exactly **"the Jurassic"** was?
+- what happened to the **ten days that vanished** in October 1582?
+- whether **February 30th** ever existed? (It did. Once. In Sweden.)
+
+Computers are surprisingly bad at these questions. Python's built-in
+`datetime` can't even hold a year before 1 AD. This library answers all
+of them — and it never needs the internet, never guesses, and tells you
+honestly when history itself doesn't know the answer.
+
+## Install
+
+```bash
+pip install chronologia
+```
+
+Python 3.10+. The calendrical core is pure standard library; the
+natural-language layer adds two small helpers — **ovos-number-parser**
+(spelled numbers → digits) and **ovos-spec-tools** (loads each language's
+vocabulary files).
+
+**Status.** chronologia is in **alpha**: the public API surface named in
+`chronologia.__all__` is what you build against, and it is covered by an
+extensive test suite, but signatures may still change ahead of a 1.0 that
+freezes them. Pin a version if you need stability across upgrades.
+
+## Nobody means midnight
+
+When someone says **"June 2027"**, they mean the whole month — not one
+secret instant at midnight on the 1st. This library takes that
+seriously: its answers are **spans** — a start and an end. The width of
+a span is honest information. A day is a day wide. A month is a month
+wide. "The Jurassic" is fifty-six million years wide:
+
+```python
+from chronologia import lookup
+
+jurassic = lookup("jurassic")
+print(jurassic.span.start.year)   # -201598050  (about 201.6 million years ago)
+print(jurassic.span.end.year)     # -143098050
+```
+
+Every span also carries a one-word honesty label, its **basis**: was
+this *computed* from an exact rule (`"exact"`), *looked up* in a
+published table (`"tabulated"`), *pieced together* by historians
+(`"reconstructed"`), or *guessed about a future* nobody has decided yet
+(`"predicted"`)? The Jurassic above says `tabulated` — it comes straight
+from the official geological chart, uncertainties included.
+
+Under the hood, one trick powers everything: every day that has ever
+existed gets a plain number — its **Julian Day Number** — so *any* of the
+seventeen built-in calendars can talk to any other by meeting at the
+number in the middle. See [docs/getting-started.md](docs/getting-started.md)
+for the three ideas the whole library is built from.
+
+## What it will NOT do (on purpose)
+
+Some dates cannot be computed — by anyone — and this library refuses to
+pretend otherwise:
+
+- **Moon-sighting months.** The religious Islamic month begins when
+  witnesses *see* the new crescent. A future sighting hasn't happened
+  yet, so the honest answer is a two-day span labelled `predicted` —
+  never fake certainty. (Saudi Arabia's *civil* calendar is published
+  as an official table, so it *is* included — as a table, exactly as
+  far as the table goes.)
+- **The Chinese calendar beyond its tables.** Exact from 1901 to 2099
+  via the Hong Kong Observatory's published tables; beyond that the
+  true calendar needs astronomy, so the library stops rather than
+  drifts.
+- **Calendars nobody controlled.** Before Julius Caesar, Roman priests
+  added days for political reasons — the "calendar" was whatever they
+  decided that year. No software can recover decisions that were never
+  rules. Historians' reconstructions are supported *as*
+  reconstructions, wearing their uncertainty openly.
+
+One rule covers all of it: **a span's width and basis always tell the
+truth about what is knowable.**
+
+## Stories the library can tell
+
+Each of these is a full worked guide in [`docs/`](docs/) — here is just
+the hook and where to read it.
+
+- **The ten days that never happened.** In October 1582 Pope Gregory
+  deleted ten days; Britain lost eleven in 1752, Russia thirteen in 1918
+  (which is why the "October" Revolution fell in November), and Sweden
+  needed a one-off **February 30th** in 1712. Ask for a deleted day and
+  you get a typed `NeverExisted`, not a crash → [docs/timelines.md](docs/timelines.md).
+- **Clocks that lie twice a year.** When clocks "fall back", 1:30 AM
+  happens twice; when they "spring forward", 2:30 AM never happens at
+  all. Resolve a wall-clock time and get the honest answer — both
+  instants, or "that time didn't exist" → [docs/timezones.md](docs/timezones.md).
+- **The sun, the sundial, and the pre-clock day.** Real sunrise, sunset,
+  solar noon and the three twilights (NOAA algorithm, ~1 minute), local
+  *mean* time from before timezones, the unequal hours the Roman world
+  lived by, Islamic prayer times as named conventions, moon phases and
+  the astronomical seasons — plus leap seconds, the reconciliation of
+  atomic and astronomical time → [docs/sun-moon-and-seasons.md](docs/sun-moon-and-seasons.md).
+- **Deep time, honestly.** "66 million years ago" and "66.043 million"
+  are different *claims*, and the span's width says which you made;
+  radiocarbon ages calibrate through the published curve →
+  [docs/deep-time.md](docs/deep-time.md).
+- **Emperors, popes, and consuls.** "Reiwa 7", "the consulship of
+  Lentulus and Marcellus", "Year 5 of Ramesses II" in three competing
+  scholarly chronologies — plus the full Roman Kalends/Nones/Ides
+  grammar in ten living languages → [docs/eras-and-rulers.md](docs/eras-and-rulers.md).
+- **Beyond Earth.** Mars Sol Date, the Darian calendar, rover
+  mission-sols, a span-valued Big Bang epoch and Sagan's Cosmic Calendar
+  → [docs/mars-and-beyond.md](docs/mars-and-beyond.md).
+
+Even a plain word like **"morning"** is a span — and a *convention* a
+culture agrees on, not a fact about the sun. English splits afternoon
+from evening at 18:00; Spanish runs one *tarde* through to 20:00:
+
+```python
+from datetime import date
+from chronologia import daypart_span
+
+tuesday = date(2027, 6, 8)
+print(daypart_span(tuesday, "afternoon").end.isoformat())            # 2027-06-08T18:00:00
+print(daypart_span(tuesday, "tarde", region="es").end.isoformat())  # 2027-06-08T20:00:00
+```
+
+## Command line
+
+Installing the package puts a `chronologia` command on your path (or run it
+as `python -m chronologia`). Each subcommand prints one friendly line:
+
+```bash
+chronologia convert 2024-06-01 --to hebrew        # gregorian 2024-06-01 = hebrew 5784-02-24
+chronologia extract "last summer"                 # -> [..., ...) (year)
+chronologia holidays US 2024                       # one date + name per line
+chronologia easter 2024                            # Easter 2024 (gregorian): 2024-03-31
+chronologia when 1984-06?                          # -> [1984-06-01..., 1984-07-01...) [?]
+```
+
+The same entry point is callable in-process — handy for scripts and tests —
+by handing `main` an argument list (it prints to stdout and returns an exit
+code):
+
+```python
+from chronologia.__main__ import main
+
+main(["easter", "2024"])                # prints: Easter 2024 (gregorian): 2024-03-31
+main(["convert", "2024-06-01", "--to", "coptic"])
+main(["when", "1984-06?"])
+```
+
+BC / negative years need argparse's `--` separator so the leading `-` is not
+read as a flag: `chronologia convert --from julian --to gregorian -- -0043-03-15`.
+
+## Reference
+
+Full guides for everything above live in [`docs/`](docs/), mapped with a
+suggested reading order in [**docs/index.md**](docs/index.md). Prefer to learn
+by running code? The [`examples/`](examples/) directory is eight self-contained,
+self-checking scripts (`python examples/01_extract_basics.py`).
+
+| | |
+|---|---|
+| **Who is this for?** | [**docs/use-cases.md**](docs/use-cases.md) — worked programs for archivists, historians, archaeologists, faith communities, astronomers, engineers, and voice assistants — start here |
+| Reading human dates | [**docs/extraction.md**](docs/extraction.md) — `extract_timespan` turns a phrase into a span; how the per-language vocabulary works and how to add a language |
+| 17 calendars | Gregorian, Julian, Hebrew, Islamic (arithmetic + Saudi Umm al-Qura table), Solar Hijri, Chinese (1901–2099), Coptic, Ethiopian, Armenian, ancient Egyptian, Maya Long Count, French Republican, Bahá'í, ISO week, and more — [docs/calendars.md](docs/calendars.md) |
+| Timelines | 13 jurisdictions' calendar reforms and dateline hops — Rome, Britain, Sweden, Russia, Greece, Japan, plus the days Samoa, the Philippines and Alaska deleted or re-lived at the International Date Line — [docs/timelines.md](docs/timelines.md) |
+| Named periods | the full geological chart (180 entries) plus regional archaeological ages — a British "Late Bronze Age" is not a Mesopotamian one — [docs/deep-time.md](docs/deep-time.md) |
+| Eras & counts | BC/CE, Anno Mundi, Hijri years, Holocene, Byzantine, unix time, Julian Day, Before Present; regnal years (Japanese nengō, Roman consuls, Egyptian chronologies) — [docs/eras-and-rulers.md](docs/eras-and-rulers.md) |
+| Recurrence | [RFC 5545 RRULE](docs/recurrence.md) — "every third Tuesday", Labor Day, Friday the 13th — parsed and expanded as pure JDN arithmetic into day-wide `DateSpan`s |
+| Civil holidays | [public/regional/municipal holidays](docs/civil-holidays.md) as computed rules with observed-shift policies — Portugal at municipal depth (~300 concelhos), US federal, Saudi Arabia |
+| Time, sun & sky | [sun, moon & seasons](docs/sun-moon-and-seasons.md) — sunrise/sunset/twilights, unequal hours, prayer times, moon phases, solstices/equinoxes, local mean time, leap seconds, and the French Revolution's 10-hour clock |
+| Timezones | [timezones](docs/timezones.md) — reading any `zoneinfo` zone as a timeline with honest fall-back/spring-forward handling |
+| Beyond Earth | [Mars and beyond](docs/mars-and-beyond.md) — Mars Sol Date, Coordinated Mars Time, the Darian calendar, and cosmology (a span-valued Big Bang epoch, the Hubble tension, Sagan's Cosmic Calendar) |
+| How does it compare? | [**docs/benchmarks.md**](docs/benchmarks.md) — a standing differential benchmark against `dateparser` and `dateutil` on the repo's own hand-derived corpora |
+
+Every algorithm and every number in the data files is transcribed from
+a cited published source — citations sit in the module docstrings and
+data-file headers. Where sources disagree, both versions ship under
+different names. Where sources are silent, the library says so instead
+of guessing.
+
+## How well does it speak your language?
+
+Forty languages load, but they are not all equally exercised, and pretending
+otherwise would waste your afternoon. Coverage falls into three honest bands:
+
+**Reviewed in depth** — English, Spanish, Portuguese, French, German, Dutch,
+Russian, Arabic, Hebrew. Each has been through repeated adversarial audit
+rounds *and* a dedicated per-language review that probed everyday register,
+not just textbook forms: "quarter to four", "tonight at 8", "om de twee
+weken", "без пяти девять". Expect these to handle what a person would
+actually type.
+
+**Broadly covered** — Italian, Polish, Czech, Slovak, Slovenian, Croatian,
+Bulgarian, Ukrainian, Swedish, Danish, Norwegian (Bokmål and Nynorsk),
+Finnish, Estonian, Hungarian, Greek, Turkish, Azerbaijani, Persian,
+Indonesian, Malay, Catalan, Galician, Romanian, Basque, Frisian. Each has its
+own test corpus and is swept whenever a shared mechanism changes, so the
+common constructions work; the idiomatic long tail is thinner, and that is
+where bug reports are most useful.
+
+**Early** — Aragonese, Asturian, Kabyle, Mirandese, Occitan. The vocabulary
+is in place and the engine is shared, so a lot already works, but these have
+not yet had a native speaker read them end to end. Occitan is the model for
+how that changes: a native speaker reviewed a sibling project's word lists,
+and the forms they supplied turned up a real bug here — "davant-ièr" was
+being read as *yesterday* rather than the day before.
+
+If your language sits in the second or third band and something reads wrong,
+that report is worth more than a patch — attach the phrase, what you expected,
+and what you got. [CONTRIBUTING.md](CONTRIBUTING.md) explains how a language
+gets deepened, and [docs/adding-a-language.md](docs/adding-a-language.md) is
+the full walkthrough for adding one.
+
+## Built by AI, held to account by tests
+
+chronologia was written and orchestrated by AI, directed and reviewed by a
+human maintainer. That is stated plainly here because the method is the reason
+the library exists at all — and because you should be able to judge the work
+without having to trust either the AI or the maintainer.
+
+**Why it could only be built this way.** A library that reads dates in around
+forty languages — with the goal of *every* language over time, the way the
+sibling [orthography2ipa](https://github.com/TigreGotico/orthography2ipa)
+project is already 1000+ languages strong — needs command of grammar,
+number-words, calendar arithmetic and holiday law in each one. No single
+maintainer speaks that many languages, and commissioning a native-speaker
+linguist for each was never realistic for an open-source project — that is
+exactly the barrier that has kept libraries like this narrow, and stuck at a
+handful of major languages. What *is* realistic is to hold AI to a discipline
+strict enough that breadth never buys itself with correctness, so that adding
+the next language is a bounded, verifiable unit of work rather than an act of
+faith:
+
+- **Cite or refuse.** Every algorithm is transcribed from a named, downloaded
+  source — a linguistics paper, a calendrical reference, a statute or gazette —
+  and every gold test value is derived by hand or from an independent source,
+  never from the code under test. Where sources disagree, both readings ship
+  under different names; where no citable source exists, the feature is
+  *refused* and the gap documented. The library says "not known" rather than
+  guess.
+- **Natural-language, test-driven.** For everything a human types, the test
+  came first: thousands of real phrases with hand-derived expected spans, per
+  language, plus adversarial cases written to break the parser. A wrong answer
+  is the top-priority bug before any new feature — and a semantic-parity block
+  checks every language against English span-for-span, so a language nobody on
+  the team speaks is still held to exactly the same bar as the ones they do.
+
+Neither claim asks for your trust: the citations sit in the source and the
+data-file headers, and the test suite — well over a hundred thousand checks —
+either passes on every commit or it doesn't. The full account, including who
+did what and what the process got wrong along the way, is in
+[**docs/transparency.md**](docs/transparency.md).
+
+## Related projects
+
+chronologia is part of the OpenVoiceOS family of language-processing libraries.
+Where this one *reads and reckons* dates, its neighbours handle the pieces
+around them:
+
+- **[ovos-date-parser](https://github.com/OpenVoiceOS/ovos-date-parser)** —
+  the voice-facing layer. It builds on chronologia and adds the glue an
+  assistant needs: *saying* a date back out loud, session handling, and the
+  legacy per-language helpers. If you need to speak a date rather than read
+  one, start there.
+- **[ovos-number-parser](https://github.com/OpenVoiceOS/ovos-number-parser)** —
+  the same idea for numbers: spelled-out numbers, ordinals and fractions to
+  digits and back, across many languages. chronologia uses it to read spelled
+  numbers inside a date phrase.
+- **[ovos-spec-tools](https://github.com/OpenVoiceOS/ovos-spec-tools)** — the
+  reference implementation of the OVOS formal specifications (template
+  expander, locale loader, dialog renderer, language matcher, linter).
+  chronologia loads its per-language vocabulary files through it.
+
+## License
+
+Apache-2.0 © TigreGotico