chore: update governance documents

.gitignore

@@ -0,0 +1 @@
+.governance_ref

BRANDING.md

@@ -1,26 +1,24 @@
 # Codeijoe™ Brand Identity & Guidelines
 
-> **Tagline:** "Where AI falls short."
-> **Identity:** The Engineering Proving Ground.
+> **Tagline:** "Validate The Human, Audit The Machine."
+> **Identity:** The Engineering Audit Authority.
 > **Since:** November 5, 2024 (First Commercial Use).
 
 ## 1. The Core Narrative
-Codeijoe exists to validate the **human edge** in software engineering.
-* **AI (LLMs)** are excellent at syntax and boilerplate.
-* **Engineers** are required for context, architectural decisions, and maintaining legacy systems.
-
-**Codeijoe tests for Context & Decision Making.** We do not test for memorized syntax.
+Codeijoe exists to separate **Engineers** (who take liability) from **Prompters** (who generate code).
+* **The Crisis:** "Vibe Coding" has flooded the industry with fragile, AI-generated software.
+* **The Solution:** We provide "Brownfield Missions"—broken, legacy codebases that require Human Context to fix.
 
 ## 2. Terminology Enforcement (Strict)
-To maintain the high-stakes environment, the following terminology replacement is mandatory across all repos:
+To maintain the "High Stakes" environment, use these terms:
 
-| BANNED TERM ❌ | REQUIRED TERM ✅ | REASON |
+| BANNED TERM ❌ | REQUIRED TERM ✅ | CONTEXT |
 | :--- | :--- | :--- |
-| **Mentorship** | **Proving Ground / Verification** | We do not hold hands; we test skills. |
-| **Mentee/Student** | **Challenger** | Passive vs. Active mindset. |
-| **Teacher/Mentor** | **Reviewer/Maintainer** | Objective code review, not subjective teaching. |
-| **Homework/Task** | **Mission / Protocol** | Industrial framing over academic framing. |
+| **Coding Challenge** | **Audit Mission** | It's not a game; it's a forensic audit. |
+| **Solution / Answer** | **Trade-off Analysis** | There is no single right answer, only choices. |
+| **Student** | **Auditor / Challenger** | Active liability vs. Passive learning. |
+| **Teacher** | **The System** | We verify; we don't teach. |
 
 ## 3. Visual & Voice
-* **Tone:** Stoic, Professional, "The Mountain Engineer". No fluff, no excessive emojis.
-* **Logo Usage:** The name "Codeijoe" must always carry the **™** symbol on its first mention in documentation to assert Common Law Trademark rights.
+* **Tone:** Forensic, Industrial, "The Auditor".
+* **Trademark:** The name "Codeijoe" must always carry the **™** symbol on its first mention in formal docs.

CODE_OF_CONDUCT.md

@@ -1,56 +1,47 @@
-# Code of Conduct
+# Codeijoe™ Professional Conduct Protocol
 
-## The "Professional" Clause
-Codeijoe is a simulation of a high-standard engineering environment.
-* **Toxicity is banned:** Harassment, elitism, or discrimination results in an instant ban.
-* **Laziness is discouraged:** Asking questions that can be answered by reading the README is considered noise.
+> **Status:** Active Enforcement
+> **Applicability:** All Repositories, Pull Requests, and Issues.
 
-We are here to build, not to argue.
+## 1. The Core Philosophy
+Codeijoe is not a social club; it is a **Professional Audit Simulation**.
+We value **Integrity** over Comfort, and **Truth** over Politeness.
 
----
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+While we strictly enforce a harassment-free environment, we do not enforce "toxic positivity". Engineering reviews are critical, direct, and factual.
 
-Examples of unacceptable behavior by participants include:
+## 2. Standards of Conduct
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+### ✅ Required Behavior (The Professional)
+* **Accountability:** Own your code. If you make a mistake, admit it and fix it.
+* **Direct Communication:** Be concise. Don't fluff your sentences.
+* **Reasoning:** Explain *why* you made a decision, not just *what* you did.
+* **Respect for Time:** Read the documentation (`README.md`, `CONTRIBUTING.md`) before asking questions.
 
-## Our Responsibilities
+### ❌ Prohibited Behavior (The Amateur)
+* **AI Spamming:** Submitting unreviewed, auto-generated code just to "pass". This results in an immediate **Permanent Ban**.
+* **Begging for Hints:** Opening Issues asking "How do I solve this?". This is an audit, not a tutorial.
+* **Solution Leaking:** Posting full answers in public discussions. This ruins the proving ground for others.
+* **Harassment:** Any form of sexism, racism, or personal attacks. We have zero tolerance for hate speech.
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+## 3. The "No Spoon-feeding" Clause
+In the industry, your Senior Engineer is busy.
+* **It is NOT a violation** of this Code of Conduct for a Maintainer to close your Issue with "Read the Manual" or "Debug it yourself."
+* This is not hostility; this is the **Standard of Independence** we are testing for.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+## 4. Enforcement Strategy
 
-## Scope
+### The "One Strike" Policy for Integrity
+* **Cheating / AI Spam / Tempering with Tests:** Immediate Ban. No appeal.
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+### The "Three Strike" Policy for Behavior
+* **Unprofessional Conduct (Trolling/Spamming):**
+    1.  **Warning:** Comment deleted & formal warning.
+    2.  **Suspension:** 30-day block from the organization.
+    3.  **Ban:** Permanent expulsion.
 
-## Enforcement
+## 5. Reporting
+If you witness genuine harassment or abuse (not just strict code review), report it directly to the Ops Commander at **iw@ijoe.eu.org**.
+* *Note: Complaints about "The test is too hard" or " The bot is mean" will be ignored.*
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html][version]
-
-[homepage]: https://www.contributor-covenant.org
-[version]: https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+---
+*Adapted for the Codeijoe Audit Authority. This document supersedes the standard Contributor Covenant.*

CONTRIBUTING.md

@@ -1,25 +1,27 @@
-# Rules of Engagement
+# Rules of Engagement: The Audit Protocol
 
-**Welcome to the Proving Ground.**
-You are here to test your skills, not to be taught.
+**Welcome to the Authority.**
+You are here to validate your Engineering Judgment, not just your syntax.
 
-## The Workflow
-1. **Fork** the Challenge Repository.
-2. **Solve** the problem locally.
-3. **Test** locally. If `npm test` fails locally, **DO NOT** open a PR.
-4. **Submit PR** only when you are confident.
+## 1. The "Human-Only" Workflow
+1. **Fork** the Mission Repository.
+2. **Audit** the codebase. Find the trap (Logic Error, Security Hole, or Performance Bomb).
+3. **Fix** the issue locally.
+4. **Submit PR** to the `main` branch.
 
-## The "Zero-Touch" Policy
-We utilize aggressive automation.
-* If your PR fails the CI/CD Pipeline (Linter/Tests), it will be **automatically ignored** by humans.
-* Do not tag Maintainers asking "Why did my test fail?". Read the logs. Debugging is part of the challenge.
+## 2. The Voight-Kampff Rule (CRITICAL)
+Codeijoe uses an automated **Reasoning Check**.
+* We do not care if your code works. We care if you know **WHY** it works.
+* **Mandatory:** In your Pull Request description, you MUST fill out the **"Trade-off Analysis"** section.
+* **Warning:** If you provide a generic AI summary (e.g., "I fixed the bug"), our Gatekeeper Bot will **Auto-Reject** your submission as "AI Slop". Write like an Engineer.
 
-## Legal & IP Rights
-By submitting a Pull Request to Codeijoe:
-1. You certify that the code is your original work.
-2. You grant Codeijoe a perpetual, world-wide, royalty-free license to use, display, and distribute your contribution under the **Apache License 2.0**.
-3. You retain moral rights to claim this work in your personal portfolio.
+## 3. The "Zero-Touch" Policy
+We utilize aggressive automation.
+* **Fail Fast:** If your PR fails the CI/CD Pipeline (Tests/Linter), it is ignored.
+* **No Spoon-feeding:** Do not open Issues asking "Why did this fail?". Read the logs. Debugging is the test.
 
-## Prohibited Behavior
-* **Spoilers:** Do not post full solutions in Issues/Discussions.
-* **Begging:** Do not ask for easy passes or manual fixes.
+## 4. Legal & IP Rights
+By submitting a Pull Request:
+1.  You certify that the logic is your own.
+2.  You grant Codeijoe a license to use your submission for data analysis.
+3.  You retain moral rights to use this work in your portfolio.