mintmark 0.1.1__tar.gz

mintmark-0.1.1/.gitignore

@@ -0,0 +1,29 @@
+# Owner-only planning material. Never enters git history.
+# Repository standard section 7.1: owner-only planning documents are
+# gitignored by name.
+PLAN.md
+briefs/
+research/
+corpus/
+
+# Build and run output
+dist/
+build/
+*.egg-info/
+
+# Environments and caches
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+# OS
+.DS_Store
+
+# Minted output directories produced during development. Anchored to the root:
+# an unanchored pattern also swallowed tests/golden/demo-run, which is committed
+# reference output and the only proof that emitted bytes have not moved.
+/demo-run/
+/*-run/

mintmark-0.1.1/CHANGELOG.md

@@ -0,0 +1,137 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[keep a changelog](https://keepachangelog.com/en/1.1.0/), and this project uses
+[semantic versioning](https://semver.org/spec/v2.0.0.html).
+
+The public surface under semantic versioning is: the command-line grammar, the
+exit codes, every `--json` payload, the library's exported functions and their
+returned dataclasses, the pack schema, the manifest schema, and the byte-level
+output for a fixed set of inputs. A change that alters emitted bytes for a fixed
+seed is a major version event even when no signature changed, because it breaks
+the reproducibility of every published manifest.
+
+## 0.1.1 - 2026-08-22
+
+### Added
+
+- Publication to PyPI, over trusted publishing. The release workflow was written
+  and left disabled so its mechanics could be reviewed before they ever ran; this
+  enables it. No long-lived token is stored in this repository and none is passed
+  to a step, because PyPI verifies the workflow identity directly.
+
+  Three gates stand between a tag and a published release, and none of them is a
+  reviewer's attention. The tag must agree with the version in `pyproject.toml`
+  and with the version the package reports. The full gate runs first and
+  publication depends on it. The `pypi` environment requires the owner's approval
+  and admits only `v*` tags, so a push to main cannot reach it.
+
+### Notes
+
+The package is unchanged from 0.1.0. This version exists because publication is a
+repository change that needs a tag to carry it, and moving the 0.1.0 tag would
+have broken the immutability that repository's own tag ruleset enforces.
+
+A version already on PyPI cannot be replaced, and deleting a release does not
+free its number. The workflow refuses on a version mismatch rather than resolving
+one.
+
+## 0.1.0 - 2026-08-22
+
+### Changed, and it moved emitted bytes
+
+- The manifest gained a `license` block and its schema version went to 2. A
+  dataset leaves this project as a directory of files, and before this there was
+  nothing in that directory saying under what terms it could be used. An
+  attribution requirement a consumer cannot find in the artifact is not a
+  requirement. The block carries the code license, the dataset license the pack
+  declared, and a ready credit line; `verify` prints all three, and stripping the
+  block fails verification like any other tampering.
+- `pack.yaml` requires `dataset_license`, from a closed set. The engine writes
+  this into every manifest it produces, and a free-text field would put a typo,
+  or terms nobody vetted, onto a published artifact. Declaring it changes the
+  pack digest, which changes emitted bytes for a fixed seed, which is why every
+  pack in the family took a version bump alongside it.
+
+- The special-category descriptor lexicons moved into a curated YAML file and
+  grew to 90 entries. Expanding a lexicon changes the draw for every subsequent
+  index, so emitted bytes moved for a fixed seed. **Under this project's own rule
+  that is a major version event.** It is harmless only because nothing has been
+  published: there is no manifest this breaks. The reason is recorded in
+  `tests/golden/demo-run/DIGESTS.json` beside the regenerated goldens.
+- `special_rate` now governs what it claimed to govern. A recipe declared it and
+  nothing read it, so template authors fixed the density with literal
+  probabilities and the recipe field was decoration. Templates now write
+  `[?special: ...]` and the rate comes from the recipe.
+
+### Added
+
+- Turkish mirrors of every community document: contributing, conduct,
+  governance, security, and support, each linked from its original and held in
+  step by a test. The audience for this project reads Turkish, and a README
+  mirror alone left a contributor reading the project's own rules in a second
+  language. The conduct mirror records that it is our own rendering rather than
+  the official one, because the Contributor Covenant publishes Turkish at 2.0
+  while this repository adapts 2.1.
+- `docs/kvkk.md` and its Turkish mirror: what this project produces and what it
+  does not claim under law 6698, with a table mapping the taxonomy's
+  special-category labels to the categories the law enumerates, and naming the
+  three that no label covers.
+- `LICENSE-DATASETS.md`, `CITATION.cff`, issue and pull request templates,
+  `CODEOWNERS`, and grouped monthly dependency updates.
+
+- The `derived:flag_unless` rule, which turns a sentinel enum value into a
+  boolean so a row can carry both which anomaly it is and whether it is one,
+  without two independent draws that can disagree.
+- An optional `age_years: [low, high]` parameter on `datetime_window`, which
+  draws from the span that would give a person that age at the start of the
+  recipe window. Without it a birth date is drawn from the recipe window, so
+  every person in a dataset describing one year was also born in that year. The
+  field is a valid date, the label is right, the span aligns and the manifest
+  verifies, so nothing in the suite caught it; it is only wrong to a reader. The
+  parameter is optional and a field that omits it behaves exactly as before, so
+  no existing declaration had to move. Declaring it on a field whose generator
+  cannot read it is rejected by name at pack load, because a parameter nothing
+  reads is worse than one that fails loudly.
+
+- Deterministic generation engine: SplitMix64 over 64-bit modular arithmetic,
+  per-site stream derivation, unbiased bounded and weighted draws, and
+  continuous distributions sampled from committed fixed-point inverse-CDF tables
+  so that no transcendental function runs in the mint path.
+- Six identifier engines, each with a `safe` default that emits provably
+  checksum-invalid values and an opt-in `validator` mode that is watermarked in
+  the manifest.
+- A closed eighteen-label taxonomy pinned by digest, span recording that
+  survives whitespace normalization, and a label sidecar format that binds spans
+  to the exact text they index.
+- Strict, fail-closed pack loading: duplicate keys, anchors, aliases, merge
+  keys, multi-document files, non-mapping roots, tab indentation, and unknown
+  fields are each rejected by name.
+- Canonical JSONL and CSV emission with no float in emitted data, and atomic
+  output so an interrupted mint leaves no directory that looks like a dataset.
+- A provenance manifest with checksums, `verify` that recomputes every claim it
+  makes, and `reproduce` that re-mints from the manifest and compares bytes.
+- A command-line surface of seven verbs with a five-value exit-code contract and
+  stable `--json` payloads, plus a two-function library API.
+- An example fixture pack, shipped in both the wheel and the sdist, used by the
+  quickstart and the test suite.
+- A real-institution denylist built from a verified public registry, scanned in
+  required CI over lexicons, templates, and golden outputs.
+- English and Turkish READMEs, kept in step by a test that compares their
+  structure and checks the quickstart's promised output against what `verify`
+  actually prints.
+
+### Verified rather than assumed
+
+The VKN check-digit algorithm, against two independent open implementations
+cross-checked over 200 000 inputs. The unassigned status of IBAN bank code
+99999, against the TCMB participant list. Turkey's permanent UTC+3 status,
+against the IANA time zone database. The institution denylist, against the same
+TCMB list. Each record, with its source and retrieval date, is in
+`docs/normative-verification.md`.
+
+### Notes
+
+No release has been published. Nothing exists on any package registry, and
+nothing in this file should be read as a claim that an installable artifact is
+available. The name Mintmark is provisional pending trademark screening.

mintmark-0.1.1/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 [yyyy] [name of copyright owner]
+
+   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.

mintmark-0.1.1/NOTICE

@@ -0,0 +1,14 @@
+Mintmark
+Copyright 2026 Mintmark contributors
+
+This product includes software developed by the Mintmark contributors.
+
+Mintmark is licensed under the Apache License, Version 2.0. This NOTICE is
+informational and does not modify that license.
+
+Mintmark is a provisional working name. Trademark screening is not complete and
+the name is not frozen. See TRADEMARKS.md once published.
+
+Third-party code or assets incorporated into Mintmark must be recorded in
+ORIGIN_AND_ATTRIBUTION.md, including any attribution or NOTICE text required
+by their licenses.