CompTextv7 accepts focused changes that preserve deterministic replay-integrity validation boundaries.
- This improves deterministic replay-integrity validation or is strictly maintenance-only.
- No runtime orchestration added.
- No LLM judge added.
- No embeddings/vector search added.
- No fuzzy semantic matching added.
- No cloud dependency added to validation logic.
- No dashboard/SaaS behavior added.
- No hidden platform expansion.
- Artifacts were regenerated if fixture or validator semantics changed.
- The evidence index was updated or confirmed unchanged if committed evidence artifacts changed.
- Tests were added or updated for new artifact or contract behavior.
- Taxonomy labels were reused, or new labels are explicitly justified.
- The change preserves offline reproducibility.
- The change does not require an RFC, or an RFC is linked.
Before requesting review, confirm the change does not introduce:
- agent framework behavior
- runtime orchestration behavior
- tool routing platform behavior
- LLM judging
- embeddings/vector retrieval
- probabilistic semantic evaluation
- cloud-only validation dependencies
- dashboard/SaaS product scope
If fixture semantics, validator logic, or artifact-producing contracts change, regenerate required artifacts and include the resulting deterministic outputs in the PR.
All validation behavior in core must remain deterministic, offline-capable, and reproducible from committed inputs and scripts.
Reuse existing registered failure labels whenever possible. New labels require explicit justification, narrow definitions, and matching tests/docs updates.
Any proposal that expands scope beyond deterministic replay-integrity validation requires an accepted RFC before implementation.
Keep PRs small, focused, and auditable. Separate governance/docs updates from core logic changes. Core logic updates require tests and green CI before merge readiness.
Changes primarily authored by autonomous coding agents or automated workflows (including ChatGPT, Codex, Gemini, and Copilot) require human review before merge. These edits must stay within the approved PR scope and include exact test commands with their results. To preserve audit trails for automated edits, put workflow, dependency, release, security, packaging, or artifact-only changes into separate PRs when they are not required outputs of the same fixture, validator, or artifact-generator change.
If committed evidence artifacts change, the evidence index must be updated or explicitly confirmed unchanged with rationale in the PR.