pccxai · hkimw · May 6, 2026
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,15 +1,5 @@
 # Code of Conduct
 
-PCCX AI participants are expected to follow the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+pccxai participants are expected to follow the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
 
-## Scope
-
-This applies to all project spaces -- issues, pull requests, discussions, and any project-affiliated communication.
-
-## Enforcement
-
-Reports may be sent to k1h6w4@gmail.com. Reports are reviewed with discretion. Maintainers may remove or reject content that violates this Code, and may temporarily or permanently ban contributors as needed.
-
-## Attribution
-
-Adapted from the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+Reports may be sent to k1h6w4@gmail.com. Maintainers review reports with discretion and may remove or reject conduct that violates this standard.
diff --git a/ISSUE_TEMPLATE/bug.yml b/ISSUE_TEMPLATE/bug.yml
@@ -0,0 +1,56 @@
+name: Bug
+description: Report a reproducible defect.
+title: "[bug] "
+labels: ["type:bug", "status:triage"]
+body:
+  - type: input
+    id: repository
+    attributes:
+      label: Repository
+      description: Repository and path, if known.
+      placeholder: "pccxai/repo-name, path/to/file"
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version or commit
+      description: Tag, branch, or commit where the defect was observed.
+      placeholder: "main at abc1234"
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed result
+      description: What happened?
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected result
+      description: What should have happened?
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Reproduction
+      description: Minimal commands, inputs, or steps.
+      placeholder: |
+        1. ...
+        2. ...
+        3. ...
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: OS, toolchain versions, target board, and other relevant context.
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence
+      description: Logs, screenshots, failing checks, or links to run output.
diff --git a/ISSUE_TEMPLATE/bug_report.yml b/ISSUE_TEMPLATE/bug_report.yml
diff --git a/ISSUE_TEMPLATE/documentation.yml b/ISSUE_TEMPLATE/documentation.yml
diff --git a/ISSUE_TEMPLATE/evidence.yml b/ISSUE_TEMPLATE/evidence.yml
@@ -0,0 +1,39 @@
+name: Evidence
+description: Submit or request evidence for repository claims, release gates, or review decisions.
+title: "[evidence] "
+labels: ["type:docs", "area:verification", "status:triage"]
+body:
+  - type: input
+    id: repository
+    attributes:
+      label: Repository
+      description: Repository where the claim, gate, or review decision lives.
+      placeholder: "pccxai/repo-name"
+    validations:
+      required: true
+  - type: textarea
+    id: subject
+    attributes:
+      label: Subject
+      description: Claim, release gate, or review decision that needs evidence.
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence state
+      description: Link the logs, reports, commits, checks, or board records. Say "missing" if evidence is not available yet.
+    validations:
+      required: true
+  - type: textarea
+    id: limits
+    attributes:
+      label: Limits
+      description: Known gaps, blocked inputs, unsupported scope, or follow-up work.
+    validations:
+      required: true
+  - type: textarea
+    id: reviewer_notes
+    attributes:
+      label: Reviewer notes
+      description: Optional notes for maintainers.
diff --git a/ISSUE_TEMPLATE/feature.yml b/ISSUE_TEMPLATE/feature.yml
@@ -0,0 +1,44 @@
+name: Feature
+description: Propose a scoped capability or repository change.
+title: "[feature] "
+labels: ["type:feature", "status:triage"]
+body:
+  - type: input
+    id: repository
+    attributes:
+      label: Repository
+      description: Target repository or repositories.
+      placeholder: "pccxai/repo-name"
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What concrete problem does this solve?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: Describe the smallest useful change.
+    validations:
+      required: true
+  - type: textarea
+    id: boundary
+    attributes:
+      label: Boundary
+      description: What is in scope, and what is explicitly out of scope?
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence or references
+      description: Related issues, design notes, traces, logs, or prior work.
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance checks
+      description: How should maintainers verify this is done?
diff --git a/ISSUE_TEMPLATE/feature_request.yml b/ISSUE_TEMPLATE/feature_request.yml
diff --git a/ISSUE_TEMPLATE/good_first_issue.yml b/ISSUE_TEMPLATE/good_first_issue.yml
diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md
@@ -1,34 +1,14 @@
-<!-- Keep the description tight; the diff itself is the source of truth. -->
-
 ## Summary
 
-<!-- What changed and why, in 1-3 sentences. -->
-
-## Type of change
-
-- [ ] Bug fix
-- [ ] New feature
-- [ ] Documentation
-- [ ] Refactor / cleanup
-- [ ] Build / CI / chore
-
-## Verification
-
-<!-- How was this tested? Cite commands, links to CI runs, or screenshots. -->
-
-## Linked issues
-
-<!-- Closes #..., relates to #..., or "(none)". -->
+-
 
-## Engineering checklist
+## Evidence State
 
-- [ ] Scope is small and bounded
-- [ ] Public interface or boundary is clear
-- [ ] Tests/smoke checks were run
-- [ ] No overclaim about production readiness, timing closure, KV260 inference, or stable ABI
-- [ ] No unrelated repo settings, release, tag, or visibility changes
-- [ ] Critical architecture assumptions are stated
+Evidence state:
 
-## Notes for reviewer
+## Review
 
-<!-- Optional. Anything subtle that the diff does not show. -->
+- [ ] Scope is bounded
+- [ ] Labels and linked issues are correct
+- [ ] Public wording is backed by evidence
+- [ ] No unrelated settings, release, tag, or visibility changes