metrifid 0.2.1__tar.gz

metrifid-0.2.1/.github/quality-constraints.txt

@@ -0,0 +1,11 @@
+# CI-only quality toolchain. Public runtime and development dependency metadata remain minimum-only.
+build==1.5.0
+editables==0.6
+hatchling==1.31.0
+hypothesis==6.165.2
+mypy==1.20.2
+numpy==2.3.5
+pytest==9.1.1
+pytest-randomly==4.1.0
+ruff==0.16.2
+twine==7.0.0

metrifid-0.2.1/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+coverage.xml
+htmlcov/
+build/
+dist/
+*.egg-info/
+*.dist-info/
+.venv/

metrifid-0.2.1/.pre-commit-config.yaml

@@ -0,0 +1,23 @@
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff check
+        entry: python -m ruff check
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: ruff-format
+        name: ruff format --check
+        entry: python -m ruff format --check
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: mypy
+        name: mypy --strict src/metrifid
+        entry: python -m mypy --strict src/metrifid
+        language: system
+        types: [python]
+        pass_filenames: false

metrifid-0.2.1/CHANGELOG.md

@@ -0,0 +1,269 @@
+# Changelog
+
+Notable changes to `metrifid`. Starting with `0.2.0`, release identifiers use exactly three
+dot-separated integer components: `MAJOR.MINOR.PATCH`. Historical development entries below
+remain as an audit trail and do not define the current release version.
+
+## 0.2.1
+
+- Keep Apache License 2.0 as the controlling license for the open-source Metrifid repository.
+- Add project attribution through `NOTICE`.
+- Add the unmodified Developer Certificate of Origin 1.1 and require signed-off contributed commits.
+- Clarify that DCO sign-off is contribution provenance, not copyright assignment.
+- Package `LICENSE` and `NOTICE` as PEP 639 legal files and carry `DCO` in the source distribution.
+- Identify the copyright holder in package metadata and remove the deprecated Apache license Trove
+  classifier.
+
+## 0.2.0
+
+- Add `python -m metrifid.demo`, a self-contained first-use demonstration that runs from a wheel
+  installation alone with no checkout, arguments, network access, or packaged assets.
+- Add `docs/sdk.md` documenting the supported programmatic execution surface — `certify_models`,
+  `compare_configuration_file`, and `audit_configuration_file` — with signatures, return types, the
+  completed-decision versus refusal distinction, output ownership, the native runtime requirement,
+  and an explicit statement that native execution is neither thread-safe nor reentrant.
+- Add four runnable SDK example scripts under `examples/sdk/` that use only public APIs and run
+  from any directory against an installed wheel.
+- Add a complete, runnable comparison example under `examples/compare/` with all ten configuration
+  fields, both models, and a workload preparation script that never overwrites an existing artifact.
+- Make the README first-use path wheel-only, and use inline code instead of relative Markdown links
+  so the PyPI description has no broken links before owner-bound URLs exist.
+- State in `docs/model_closure.md` and `docs/capabilities_and_use_cases.md` that closure content is
+  bounded by the documented byte limit, that file-count, directory-count, and traversal-depth limits
+  are not separately guaranteed in this pre-alpha release, and that this package targets local
+  trusted-input workflows rather than hosted untrusted uploads.
+- Replace hand-maintained test-count claims with a statement that release evidence is generated by
+  CI, and remove stale `0.2.0a13` version text.
+- Ship `SECURITY.md`, `CODE_OF_CONDUCT.md`, `.pre-commit-config.yaml`, and
+  `.github/quality-constraints.txt` in the source distribution so it contains everything its own
+  contributor and security documentation references.
+- Build release artifacts through isolated PEP 517, install and test the direct sdist in a separate
+  clean environment, rebuild a wheel from the extracted sdist, and check distribution equivalence
+  semantically in CI.
+
+## 0.2.0a14
+
+- Add one bounded strict JSON admission module and apply it to comparison configurations, alias
+  files, and timestep-audit configurations. Duplicate member names, raw float tokens, `NaN`,
+  `Infinity`, malformed UTF-8, and oversized, over-deep, over-wide, or over-long documents are now
+  refused at every file-based trust boundary, and audit configurations no longer use permissive
+  JSON parsing.
+- Read configuration and alias files through a single no-follow descriptor confirmed regular by
+  `fstat`, with the byte ceiling applied before parsing.
+- Add `metrifid.certify.load_and_validate_certification_receipt` for receipt files and untrusted
+  bytes. It rejects duplicate names and noncanonical numeric tokens before the semantic validator
+  runs. `validate_receipt` is unchanged for callers holding a parsed mapping.
+- Make certification receipt parsing and validation importable without MuJoCo or NumPy by moving
+  the runtime-identity schema to `certify/_runtime_schema.py` and the field-report schema to
+  `certify/_field_schema.py`, and by deferring native imports in `certify/_artifact.py` and
+  `certify/_bytes.py` to their producer functions.
+- Report the real operation on distribution-identity failures, so a `certify` refusal says
+  `certify` and an `audit-timestep` refusal says `audit-timestep`.
+- Restore normal Python submodule attribute behavior, so `import metrifid.errors` then
+  `metrifid.errors` works.
+- Install MuJoCo in the CI quality environment so strict MyPy passes on a first push.
+
+## 0.2.0a13
+
+- Add a human-friendly getting-started guide and a faithful capabilities/use-cases reference.
+- Make source-checkout installation the primary pre-publication path in README and examples.
+- Remove stale release numbers and avoid promising a vulnerability-reporting channel before it is enabled.
+- Preserve the open-ended CPython and NumPy compatibility policy introduced in 0.2.0a12.
+- Make release quality checks reproducible with CI-only constraints that do not narrow public
+  runtime or development dependencies.
+- Correct three cross-version/platform test assumptions and the Audit retained-evidence expectation.
+- Keep runtime admission capability-based and architecture-neutral.
+
+## [0.2.0a12]
+
+### Changed
+
+- Python metadata is `>=3.11` with no upper bound, and the classifiers list 3.11 through 3.14.
+- One shared native-runtime gate now admits Certify, Compare, Audit Timestep, and compiled model
+  identity. The separate, narrower Certify envelope is removed.
+- The gate rejects only Python below 3.11. It never inspects the interpreter implementation name,
+  uses no finite Python-minor allowlist or upper bound, and never rejects an architecture; the
+  machine string remains receipt evidence only.
+- Platform admission is capability-based: a POSIX operating system reporting `Linux` or `Darwin`
+  plus the exact `dir_fd`, `follow_symlinks`, `fd`, callable, and open-flag facilities the confined
+  filesystem work requires. Native Windows remains unsupported; WSL is the documented route.
+- The MuJoCo runtime dependency is `mujoco==3.10.0.*`, so binding-only `3.10.0.postN` packages that
+  target the same native engine are accepted. Prerelease, development, `3.10.1`, and `3.11`-or-later
+  package versions still refuse, and the native engine must remain 3.10.0 / 3010000 exactly.
+- NumPy is `>=1.26` with no runtime upper bound and no runtime version gate.
+- The development extra keeps its package names, drops NumPy, and uses minimum-only specifiers.
+- The build-system requirement is `hatchling>=1.27` with no upper bound.
+- CI builds one wheel and one sdist once and installs those exact wheel bytes noneditably in every
+  compatibility lane. MJB digests are never compared across lanes.
+- `tools/mjb_characterization.py` is included in the sdist and runs in every blocking lane. It stays
+  outside the public import package.
+
+### Unchanged
+
+- Public APIs, schemas, statuses, reason codes, exit codes, numerical methods, output names, receipt
+  bytes, output ownership, source-closure behavior, and the complete-MJB identity rule.
+- The workload artifact writers, canonical JSON and exact-number helpers, and receipt parsing and
+  validation remain outside the native gate and require no MuJoCo admission.
+
+## [0.2.0a11]
+
+### Fixed
+
+- Certify and Compare perform their final public-path and exact-byte verification after the retained source contexts close, so replacing the public output pathname during final source cleanup causes refusal instead of returning paths to unrelated bytes.
+- Timestep Audit verifies the aggregate pair before making the public path and registered output tree its final success boundary, closing the same path-replacement window for aggregate results.
+- Private temporary names are relinquished permanently after finalization or cleanup. Reusing an old random temporary name later can no longer cause Metrifid cleanup to remove the caller's new directory entry.
+- Comparison and Audit tests now assert the no-clobber preservation contract instead of the obsolete replace-and-delete behavior.
+
+### Unchanged
+
+- Public APIs, schemas, statuses, reason codes, exit codes, numerical methods, output names, receipt bytes for successful unaffected runs, and the complete-MJB identity rule.
+
+## [0.2.0a10]
+
+### Fixed
+
+- Public output ownership is recorded only after a descriptor-relative no-clobber hard link exists
+  and still identifies the retained sealed bytes. A conflicting hardlink can no longer be mistaken
+  for product-owned output and deleted during failure cleanup.
+- Generic paired-result and workload-writer cleanup removes only retained private temporaries.
+  Already-linked public evidence is preserved on every later failure, while timestep-audit cleanup
+  still removes exact private workspace artifacts and never deletes registered public evidence.
+
+### Unchanged
+
+- Successful Compare, Certify, workload-writer, and timestep-audit bytes; public APIs; schemas;
+  statuses; reason codes; exits; numerical methods; and output names.
+
+## [0.2.0a8]
+
+### Fixed
+
+- A timestep audit freezes one model-closure snapshot and one bounded state/actions byte set for
+  the entire campaign. Every candidate consumes those inputs, the aggregate derives identities
+  from them, and final live-input divergence removes all audit output and refuses publication.
+- Model traversal, paired-result publication, audit cleanup, and workload writers are confined to
+  retained directory descriptors. NPZ size limits are enforced during the read, Certify retains and
+  reverifies both source snapshots, and Certify/Compare refuse output at or below either model root.
+- Source-closure documentation now matches execution: every admitted regular file under the model
+  root affects source identity, while separate dependency discovery identifies files MuJoCo reaches.
+  An unused regular file does not affect compiled-MJB bytes unless MuJoCo resolves it.
+
+### Unchanged
+
+- Public APIs, schemas, statuses, exit codes, output names, receipt meanings, numerical methods,
+  exact-time behavior, and the package architecture.
+
+## [0.2.0a7]
+
+### Changed
+
+- The project adopts its public name. The distribution, import package, console
+  command, repository slug, schema prefix and runtime key prefix are all `metrifid`, and the
+  display name is `Metrifid`. This is a pre-public namespace reset, so no alias for the former
+  internal name is shipped in any form.
+- The model-closure documentation states the part it previously left out: a substitution that is
+  visible in file metadata refuses before the member is read at all. The admitted-replacement,
+  final-divergence and byte-identical cases are unchanged and the content-addressed claim is not
+  broadened.
+
+### Unchanged
+
+- Every command, decision, status, exit code, refusal, metric, tolerance, time-grid rule,
+  source-closure algorithm, receipt hashing rule, canonical encoding, output filename, supported
+  platform and public Python export. Only the namespace and the version moved.
+
+## [0.2.0a6]
+
+### Changed
+
+- The source-closure contract is documented as what it computes: content addressing. A member is
+  named by its relative path, its exact byte count and the SHA-256 of the exact bytes read. Those
+  bytes are the ones hashed, copied into the private immutable snapshot and compiled, and the
+  source is re-measured against that snapshot before publication. The documentation no longer
+  implies that a byte-identical replacement of a member's underlying file object is detected; no
+  published identity depends on distinguishing it.
+
+### Unchanged
+
+- Every command, status, exit code, schema identifier, canonical encoding, output filename,
+  supported platform and public Python export. Symlink, path-escape, non-regular-member,
+  unreadable-member and byte-budget refusals remain fail-closed, and source content that differs
+  from the snapshot at final verification still refuses with `MODEL_CLOSURE_MUTATED`.
+
+## [0.2.0a5]
+
+### Added
+
+- `certify` is validated on Linux x86_64 as well as Darwin x86_64, both with CPython 3.12 and
+  MuJoCo Python and native `3.10.0` exactly. The supported set is explicit; every other
+  environment still refuses rather than guessing, and the refusal now names the complete
+  supported set.
+- Continuous integration runs the bundled `examples/certify/run_example.py` against the installed
+  wheel, so the documented example is exercised on every change.
+
+### Changed
+
+- Continuous integration installs the built wheel with its bounded `[dev]` extra instead of
+  installing validation tools separately, and verifies that both the import and the console
+  script resolve from the installed environment.
+- Documentation states plainly that a complete-MJB certificate is bound to the runtime identity
+  recorded in the receipt. Support statements name the two measured platforms.
+
+### Unchanged
+
+- Every command, status, exit code, schema identifier, canonical encoding, output filename,
+  atomic publication rule, closure and snapshot behavior, installed-distribution identity check,
+  top-level Python export and runtime dependency. `compare` and `audit-timestep` keep the
+  environment envelope they already had.
+
+## [0.2.0a4]
+
+### Changed
+
+- The repository is shaped for outside contributors: development-history artifacts and the tests
+  that asserted file inventories, source line counts and documentation prose are gone. Every
+  behavior, security, receipt, closure, path-confinement, workload, comparison, audit and
+  certification test is retained.
+- Two long modules were split along their real seams with no import path changed:
+  `_model_admission` is a facade over `_model_compile` and `_model_descriptors`;
+  `timestep_audit` is a facade over `_audit_config`, `_audit_execution` and `_audit_reporting`.
+- Documentation is organized around the three decisions a user makes, with an API reference, a
+  model-closure guide, a workload guide and a public case study. A runnable example ships in
+  `examples/certify/`.
+
+### Fixed
+
+- Descriptive field evidence is bounded. A changed field larger than 64 MiB per side keeps its
+  path, types, dtypes, shapes and digests but reports no element count and no witnesses, and the
+  report's `truncated` flag records it. Changed fields are described in sorted path order and no
+  two fields' copied arrays are ever held at the same time.
+- Receipt revalidation completes its descriptive type checks: a present field side must name a
+  nonempty type and a null-or-nonempty dtype, an absent side must be null throughout, and a
+  witness value may only be one of the canonical forms the reporter emits.
+
+## [0.2.0a3]
+
+### Added
+
+- `metrifid certify`: compile two MuJoCo source closures and state, over every byte of the
+  serialized compiled model, whether they are identical. Exit `0` certifies; exit `40` does not.
+  It runs no workload and never steps the simulation. On a difference the receipt reports the
+  first differing byte offset, the differing byte count, and a bounded descriptive report naming
+  the changed public fields with sorted index and value witnesses.
+- Receipt revalidation for an unsigned certification receipt: exact member sets, frozen claim and
+  limitation text, the nested runtime identity and its own hash, both role identities, each
+  artifact's binding to the recorded runtime, and the byte comparison against the two artifacts.
+
+### Fixed
+
+- Test isolation no longer depends on suite order: helpers that swap modules record and restore
+  every `sys.modules` entry and parent-package attribute they change.
+
+## Earlier development
+
+`0.1.x` through `0.2.0a2` established the foundations the shipped decisions rest on: canonical
+JSON with exact rationals and IEEE-754 bit-exact doubles, self-hashed receipts, measured model
+closures with bounded no-follow reads and mutation detection, snapshot compilation, semantic
+joint and actuator alignment, strict workload artifacts with an exact time grid, the `compare`
+decision and its four statuses, the `audit-timestep` decision, and the installed-distribution
+identity check. None of it was published.

metrifid-0.2.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,106 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a
+harassment-free experience for everyone, regardless of age, body size, visible or invisible
+disability, ethnicity, sex characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race, caste, color, religion,
+or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive,
+and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Demonstrating empathy and kindness toward other people.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Giving and gracefully accepting constructive feedback.
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the
+  experience.
+- Focusing on what is best not just for us as individuals, but for the overall community.
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing others' private information, such as a physical or electronic address, without
+  explicit permission.
+- Other conduct which could reasonably be considered inappropriate in a professional setting.
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable
+behavior and will take appropriate and fair corrective action in response to behavior they deem
+inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits,
+code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct,
+and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is
+officially representing the community in public spaces. Examples include using an official account,
+posting through an official social media account, or acting as an appointed representative at an
+online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to repository
+maintainers through private repository channels made available by the hosting platform. All
+complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any
+incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for
+any action they deem in violation of this Code of Conduct.
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or
+unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the
+nature of the violation and an explanation of why the behavior was inappropriate. A public apology
+may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people
+involved, including unsolicited interaction with those enforcing the Code of Conduct, for a
+specified period of time. This includes avoiding interactions in community spaces as well as
+external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate
+behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the
+community for a specified period of time. No public or private interaction with the people involved,
+including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this
+period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including
+sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement
+of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

metrifid-0.2.1/CONTRIBUTING.md

@@ -0,0 +1,105 @@
+# Contributing
+
+Thanks for looking. This is a small, deliberately narrow tool, and the bar for changes is
+"a user can tell the difference".
+
+## Contribution license and DCO sign-off
+
+Metrifid is licensed under Apache License 2.0. Contributions intentionally submitted for inclusion
+are accepted under that license. Every commit in a pull request must certify the Developer
+Certificate of Origin 1.1 in [`DCO`](DCO).
+
+Use `git commit -s` to add this line to each commit message:
+
+```text
+Signed-off-by: Your Name <you@example.com>
+```
+
+The sign-off certifies that you have the right to submit the contribution under Apache-2.0. It is
+not a copyright assignment or a contributor license agreement. Contributors retain copyright in
+their contributions. Do not submit material you do not have the right to contribute. A pull request
+with an unsigned commit will not be merged. The DCO also explains that the public sign-off record is
+retained and may be redistributed with the project.
+
+Read [`docs/licensing_and_contributions.md`](docs/licensing_and_contributions.md) before opening a
+pull request.
+
+## Set up
+
+```bash
+python -m venv .venv && source .venv/bin/activate
+python -m pip install -e ".[dev]"
+```
+
+The editable install above is for editing, linting, typing, and pure/unit work only. Integration,
+security, receipt, command, and release evidence must run against a noneditable wheel, because the
+product is the installed distribution rather than the source tree.
+
+The MuJoCo native engine `3.10.0` exactly is a hard requirement — the compiled-artifact identity is
+only meaningful against a fixed engine build. A binding-only `3.10.0.postN` package targets that
+same engine and is accepted; any other engine version refuses rather than guessing.
+
+Python 3.11 or newer is supported, with no upper bound and no runtime rejection based on the
+interpreter name. Release evidence currently uses CPython because the MuJoCo binary wheels exercised
+by CI target CPython. The package metadata has no artificial upper bound. CI is configured for
+CPython 3.11–3.14 on Linux x86_64, CPython 3.12 and 3.14 on macOS arm64, and CPython 3.12 on
+macOS x86_64. Linux and macOS are admitted when the shared POSIX capability gate passes, with no
+architecture whitelist. Native Windows is unsupported; use WSL.
+
+## Before you open a pull request
+
+Use the editable development environment for static quality gates:
+
+```bash
+python -m ruff check .
+python -m ruff format --check .
+python -m mypy --strict src/metrifid
+```
+
+Run product, integration, security, receipt, command, and release tests from a separate noneditable
+wheel environment:
+
+```bash
+python -m build --no-isolation
+python -m venv .wheel-test-venv
+source .wheel-test-venv/bin/activate
+python -m pip install dist/metrifid-*.whl
+python -m pip install -c .github/quality-constraints.txt   editables hatchling hypothesis mypy pytest pytest-randomly
+python -m pytest -q tests
+```
+
+CI follows the same separation: it builds one wheel and one sdist once, then installs those exact
+wheel bytes noneditably in every compatibility lane. Decision-bearing release evidence never comes
+from the editable source tree.
+
+## What the tests are for
+
+Tests here assert *behavior*: statuses, exit codes, refusal reasons, published bytes, hash
+stability, path confinement, read bounds and receipt validation. Please add tests of that kind.
+
+Please do not add tests that assert source line counts, repository file inventories,
+documentation wording, or frozen distribution hashes. Those pin the shape of the repository
+rather than the behavior of the product, and they were removed for that reason.
+
+## Things that are deliberately frozen
+
+Changing any of these is a breaking change and needs its own discussion first:
+
+- the three command shapes and their exit codes;
+- the completed statuses;
+- the complete-MJB identity method;
+- the published schema identifiers;
+- canonical JSON encoding, exact-number forms and self-hashing;
+- output filenames and atomic publication;
+- the top-level `metrifid` exports.
+
+## Style
+
+Ruff decides formatting and lint; there is no separate style guide to read. Keep functions small
+enough to read in one screen — nothing in `src/metrifid` exceeds 80 lines. Prefer a named helper
+over a comment explaining a long block, and prefer a comment explaining *why* over one restating
+*what*.
+
+## Reporting a security issue
+
+See [`SECURITY.md`](SECURITY.md). Please do not open a public issue for a vulnerability.

metrifid-0.2.1/DCO

@@ -0,0 +1,33 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.