From 5c62220f0fae992f148991332dacec777709c81d Mon Sep 17 00:00:00 2001
From: "Douglas Brown .Jr" <60854716+sonoxo@users.noreply.github.com>
Date: Thu, 27 Aug 2026 07:37:43 -0400
Subject: [PATCH] Add contributor verification checklist

---
 docs/CONTRIBUTOR_CHECKLIST.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 docs/CONTRIBUTOR_CHECKLIST.md

diff --git a/docs/CONTRIBUTOR_CHECKLIST.md b/docs/CONTRIBUTOR_CHECKLIST.md
new file mode 100644
index 0000000..842f8d5
--- /dev/null
+++ b/docs/CONTRIBUTOR_CHECKLIST.md
@@ -0,0 +1,28 @@
+# ZYRA Contributor Checklist
+
+Use this before opening a pull request.
+
+## Scope
+
+- Keep the change focused on one clear improvement.
+- Link the change to the relevant ZYRA, XUNIA, VA3LM, Cadence/Flow, ontology, or documentation lane.
+- Preserve existing security and human-approval boundaries.
+
+## Validate
+
+- Run the relevant tests.
+- Run TypeScript/build checks when code changes.
+- Never commit credentials or tokens.
+- Include a short explanation of what changed and how it was verified.
+
+## Pull request
+
+- Use a descriptive title.
+- List changed files or modules.
+- State the verification performed.
+- Add screenshots for visible UI changes.
+- Keep unrelated changes out of the PR.
+
+## First contribution path
+
+Start with documentation, tests, developer examples, or a small isolated feature. See `CONTRIBUTING.md` for the full contributor workflow.