AIAP welcomes critical review, replication, falsification, accessibility analysis, security testing, psychometric evaluation, implementation evidence, and corrections.
A proposed change should identify:
- the exact claim, rule, artifact, field, formula, or location affected;
- the evidence or failure mode motivating the change;
- whether the change alters architecture, implementation, validation, or presentation;
- the downstream artifacts that require synchronization;
- the test or falsification condition showing the change is an improvement; and
- any rights, accessibility, privacy, security, workload, or public-claim consequence.
Do not create a new lane, role, object, gate, or status merely to name a distinction. Under the evidence-plan authority rule, a category earns authority only when it changes the evidence plan or claim status required for the permitted inference.
- Preserve the current version boundary until a release is explicitly authorized.
- Update tests, crosswalks, examples, and documentation together.
- Do not weaken fail-closed gates or rights/accessibility floors.
- Do not include confidential prompt-bank content, personal data, or reusable attack recipes.
- State whether the proposal is empirically supported, theoretically motivated, or exploratory.
Acceptance remains an author/maintainer decision and does not imply endorsement of a contributor's wider framework or claims.