docs(governance): independent implementation and auditable provenance - #379
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 442589b87a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - [ ] Product-facing terminology and synthetic code/test identifiers are ARSAS-owned or neutral. | ||
| - [ ] Any external comparison is authorized black-box evidence with its original provenance retained; no source, assets, UI or documentation were copied. | ||
| - [ ] New/generated fixtures have an identified author or generator; third-party assets have verified licenses and notices. | ||
| - [ ] Existing field evidence, DataSet order, release/tag/engine SHA and failed-case history remain unchanged unless a separate evidence-backed change explicitly supersedes them. |
There was a problem hiding this comment.
When later evidence supersedes an acceptance conclusion, this checkbox's single exception also permits changing the associated release, tag, or engine SHA. That contradicts the new policy's requirements to retain historical identity exactly (lines 29 and 41) and could let reviewers approve corruption of the audit trail; separate supersedable conclusions from identifiers and historical evidence that must remain immutable.
Useful? React with 👍 / 👎.
| - [ ] Existing field evidence, DataSet order, release/tag/engine SHA and failed-case history remain unchanged unless a separate evidence-backed change explicitly supersedes them. | ||
| - [ ] Rename or JSON-schema changes update all consumers and preserve numerical/semantic assertions. | ||
|
|
||
| See [independent implementation and provenance policy](../docs/INDEPENDENT_IMPLEMENTATION_AND_PROVENANCE.md). |
There was a problem hiding this comment.
When this template is copied into a pull-request description, the body no longer has .github/ as its file context, so ../docs/... does not resolve to the repository's docs directory. Use a repository-root or absolute URL so contributors can reach the policy required by this review gate.
AGENTS.md reference: AGENTS.md:L227-L227
Useful? React with 👍 / 👎.
Introduce project-wide engineering policy for independent implementation, source and asset origin, neutral synthetic fixtures, truthful black-box comparison provenance, correct third-party notices, release immutability, and atomic contract renames. Link the policy in CONTRIBUTING and add an actionable PR review checklist. This does not certify originality of unexamined historical code; it establishes testable contributor/reviewer obligations. Documentation and contribution process only; no runtime, engine, physical results or published release changes.