From a4a1c1eac34a86d86cefbf08770924c1bb98f43f Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 22:33:35 +0700 Subject: [PATCH 1/9] Refactor: Pivot to Codeijoe Proving Ground governance model - Update README, BRANDING, OWNERSHIP to reflect Proving Ground philosophy - Add GOVERNANCE (BDFL), CONTRIBUTING (Zero-Touch), CODE_OF_CONDUCT - Update CODEOWNERS for enforcement - Update system prompts to v2.0.0 --- .github/CODEOWNERS | 35 ++- BRANDING.md | 56 +++-- CODE_OF_CONDUCT.md | 56 +++++ CONTRIBUTING.md | 25 +++ GOVERNANCE.md | 27 +++ LICENSE | 12 -- OWNERSHIP.md | 46 ++-- README.md | 44 ++-- .../codeijoe_proving_ground_v2.0.0.yaml | 200 ++++++++++++++++++ 9 files changed, 404 insertions(+), 97 deletions(-) create mode 100644 CODE_OF_CONDUCT.md create mode 100644 CONTRIBUTING.md create mode 100644 GOVERNANCE.md create mode 100644 prompts/production/codeijoe_proving_ground_v2.0.0.yaml diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index e1cb0b5..73baa39 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1,2 +1,33 @@ -# Only the Founder can approve changes to core governance -* @itwahjoedi +# Codeijoe Proving Ground - Code Owners +# This file enforces the BDFL Governance model by assigning mandatory reviewers. + +# ----------------------------------------------------------- +# GLOBAL DEFAULT +# Any file not specified below is overseen by Maintainers. +# ----------------------------------------------------------- +* @codeijoe/maintainers + +# ----------------------------------------------------------- +# THE CORE (Constitution) +# Only the BDFL (Founder) can approve changes to Governance. +# ----------------------------------------------------------- +GOVERNANCE.md @itwahjoedi +CODE_OF_CONDUCT.md @itwahjoedi +OWNERSHIP.md @itwahjoedi +BRANDING.md @itwahjoedi +LICENSE @itwahjoedi + +# ----------------------------------------------------------- +# INFRASTRUCTURE (The "Gatekeeper" Robots) +# Critical CI/CD workflows. If this breaks, the platform dies. +# Must be reviewed by the Founder. +# ----------------------------------------------------------- +.github/ @itwahjoedi +.github/workflows/ @itwahjoedi + +# ----------------------------------------------------------- +# CHALLENGE SPECS (The "Missions") +# Maintainers can design new challenges, but Founder must sign off. +# ----------------------------------------------------------- +**/*.test.js @itwahjoedi @codeijoe/maintainers +**/README.md @codeijoe/maintainers diff --git a/BRANDING.md b/BRANDING.md index 3e7233f..03e193b 100644 --- a/BRANDING.md +++ b/BRANDING.md @@ -1,32 +1,24 @@ -# BRANDING.md — Codeijoe Project - -**Version**: 1.0 -**Effective Date**: 2025-11-25 - -## 1. Brand Identity - -“**Codeijoe**” is a registered project identifier owned by Indra Wahyudi. It designates a specific open mentorship system built exclusively on the GitHub platform. - -## 2. Permitted Use - -- **Forking source code** is permitted under the terms of the Apache License 2.0. -- **Deployment to non-GitHub platforms** (e.g., GitLab, Bitbucket, internal systems) is allowed, **provided**: - - The name “Codeijoe” is **not used** in any form. - - No implication of affiliation, endorsement, or continuity is made. - - The original LICENSE and copyright notices are retained. - -## 3. Prohibited Use - -**Replication of the Codeijoe mentorship architecture within GitHub is strictly prohibited**, regardless of naming. This includes, but is not limited to: -- Creating repositories that mimic the structure, issue templates, or automation of Codeijoe tracks -- Deploying a “Codeijoe-like” mentorship system under a different GitHub organization -- Using the same workflow logic (e.g., milestone-based progression, PR review standards) in a public or private GitHub org with the intent to create an alternative instance - -**Rationale**: GitHub is the sole official runtime environment for Codeijoe. Any replication within this namespace fragments the mentorship ecosystem, creates user confusion, and constitutes a violation of platform integrity. - -## 4. Enforcement - -Violations will be addressed through: -- Immediate rejection of support or collaboration -- Reporting to GitHub Abuse pursuant to the [Acceptable Use Policies](https://docs.github.com/en/site-policy/acceptable-use-policies) -- Legal action where trademark rights have been asserted or registered +# Codeijoe™ Brand Guidelines + +> **Identity:** The Engineering Proving Ground. +> **Voice:** Direct, Technical, Stoic (The "Mountain Engineer"). + +## 1. Usage of Name +* **Correct:** `Codeijoe™` (Always capitalize C, use ™ symbol on first mention in formal docs). +* **Incorrect:** `codeijoe`, `CodeIJoe`, `CodeiJoe`. + +## 2. The Narrative (Our Voice) +We do not "nurture" or "cuddle". We **validate**. +* **Avoid:** "Learn together," "Safe space for beginners," "We will help you." +* **Use:** "Prove your skill," "Pass the gauntlet," "Engineering rigor," "Show me the code." + +## 3. Terminology Enforcement +To maintain the "Proving Ground" atmosphere, strict adherence to these terms is required: +* ❌ **Mentee** → ✅ **Challenger** +* ❌ **Mentorship** → ✅ **Challenge** / **Verification** +* ❌ **Teacher** → ✅ **Reviewer** / **Maintainer** +* ❌ **Homework** → ✅ **Mission** / **Spec** + +## 4. Logo & Visuals +* Visuals should be minimalist, terminal-inspired (Monospaced fonts), and devoid of unnecessary decoration. +* Use high-contrast colors (Dark Mode default). diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..b5a1ca5 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,56 @@ +# Code of Conduct + +## 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. + +We are here to build, not to argue. + +--- +# 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 + +Examples of unacceptable behavior by participants include: + +* 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 + +## Our Responsibilities + +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. + +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. + +## Scope + +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. + +## Enforcement + +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 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..6c93229 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,25 @@ +# Rules of Engagement + +**Welcome to the Proving Ground.** +You are here to test your skills, not to be taught. + +## 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. + +## 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. + +## 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. + +## Prohibited Behavior +* **Spoilers:** Do not post full solutions in Issues/Discussions. +* **Begging:** Do not ask for easy passes or manual fixes. diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 0000000..d0e78d1 --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,27 @@ +# Governance Model: Enlightened BDFL + +Codeijoe operates under the **Benevolent Dictator For Life (BDFL)** model. While we value community input, final strategic and technical authority rests with the Project Founder. + +## Roles + +### 1. The Ops Commander (BDFL) +* **Authority:** Absolute veto power over technical architecture, roadmap, and governance. +* **Responsibility:** Ensuring the platform remains "Low Cost, High Leverage" and consistent with the Proving Ground philosophy. + +### 2. Maintainers (The Gatekeepers) +* **Authority:** Can Review PRs, Request Changes, and Merge approved code. +* **Selection:** Invite-only. Chosen based on technical excellence and consistency. + +### 3. Challengers (Contributors) +* **Rights:** Can Fork, Submit PRs, and participate in RFC discussions. +* **Limit:** Cannot merge their own code. + +## Decision Making Process (RFC) +Major changes to the platform (e.g., adding a new language track, changing CI/CD logic) must go through the **Request For Comments (RFC)** process: + +1. Open an Issue with label `RFC`. +2. Detail the technical proposal. +3. Community discusses. +4. **Ops Commander makes the final decision:** `Accepted`, `Rejected`, or `Deferred`. + +**Consensus is preferred, but BDFL decision is final.** diff --git a/LICENSE b/LICENSE index 5797ed0..dae261e 100644 --- a/LICENSE +++ b/LICENSE @@ -174,15 +174,3 @@ of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS - ---- - -**IMPORTANT ADDENDUM**: - -The name **"Codeijoe"**, its methodology, repository scaffolding pattern, -mentee progression workflow, and defined terminology are **excluded** -from the grant of license above. These elements constitute exclusive -intellectual property of Indra Wahyudi. All rights reserved. - -Unauthorized replication of the Codeijoe system within the GitHub -ecosystem—under any name—is prohibited. diff --git a/OWNERSHIP.md b/OWNERSHIP.md index bb807b7..664730b 100644 --- a/OWNERSHIP.md +++ b/OWNERSHIP.md @@ -1,26 +1,20 @@ -# OWNERSHIP.md — Codeijoe Project - -**Version**: 1.0 -**Effective Date**: 2025-11-25 -**Owner**: Indra Wahyudi (GitHub: `itwahjoedi`) - -## 1. Declaration of Ownership - -The **Codeijoe Project**—including its name, methodology, repository architecture, workflow design, terminology, and mentorship system—is the exclusive intellectual property of **Indra Wahyudi**. - -## 2. First Use in Commerce - -The name **“Codeijoe”** was first used in commerce on **2024-11-05**, the date of creation of the GitHub Organization at [`github.com/codeijoe`](https://github.com/codeijoe). This constitutes the initial public assertion of brand identity and operational deployment. - -## 3. Scope of Ownership - -Ownership extends to, but is not limited to: -- The standardized repository structure for mentorship tracks -- Issue lifecycle templates and automation logic -- Defined terminology (e.g., “Mentee Maturity Levels,” “PR Culture”) -- The GitHub-native Platform-as-a-Service (PaaS) architecture -- All derivative systems operating under the Codeijoe methodology - -## 4. Reservation of Rights - -All rights not expressly granted are hereby reserved. No license—express or implied—is granted to replicate, imitate, or operationalize the Codeijoe system within the GitHub ecosystem under any alternative name or identity. +# IP Ownership & Rights + +## 1. Code Ownership (The "Upstream" Rule) +By submitting a Pull Request to any Codeijoe repository, you agree to license your contribution under the **Apache License 2.0**. +* **What this means:** The code becomes part of the Codeijoe open-source ecosystem. +* **Patent Grant:** You grant an implicit patent license to users of the code. + +## 2. Contributor's Personal Rights (Portfolio) +Codeijoe acknowledges that the **Moral Rights** and **Authorship** remain with the Challenger (You). +* You are encouraged to pin your forked repositories to your personal profile as **Proof of Work**. +* You may use the code you wrote here to showcase your skills to potential employers. + +## 3. Platform Data +* **Issues, Discussions, and Comments** hosted on `github.com/codeijoe` are treated as public domain documentation or licensed under **CC BY-SA 4.0** to ensure knowledge preservation. +* Codeijoe reserves the right to archive or back up this data independent of GitHub. + +## 4. No Employment Relationship +Participation in Codeijoe (as a Challenger or Maintainer) is **strictly voluntary**. +* There is no employment, agency, or contractor relationship between you and the Codeijoe founder. +* No wages or compensation are offered. The reward is the **competency verification** itself. diff --git a/README.md b/README.md index 8ac4897..04e325f 100644 --- a/README.md +++ b/README.md @@ -1,34 +1,28 @@ -# Codeijoe Open Mentorship +# Codeijoe Governance & Protocols -**GitHub Organization**: [`github.com/codeijoe`](https://github.com/codeijoe) -**Founded**: November 5, 2024 -**Owner**: Indra Wahyudi (`itwahjoedi`) +> **Status:** Active Enforcement +> **Legal:** Apache 2.0 (Software) & CC BY-SA 4.0 (Docs) -## Vision +## The Proving Ground Philosophy +Codeijoe is **NOT** a mentorship platform or a coding school. We do not provide tutorials, hand-holding, or career counseling. -Codeijoe is an **open mentorship platform built entirely on GitHub**. -It treats the GitHub Organization as a **Platform-as-a-Service (PaaS)**, where learning, collaboration, and project management occur exclusively through Issues, Discussions, and Actions. +**Codeijoe is an Automated Engineering Proving Ground.** -## Core Principles +We provide the infrastructure (Challenges, CI/CD Pipelines, and Specs). You provide the code. If your code passes our automated gauntlet and human review, you earn the right to merge—and the proof of competence that comes with it. -- **Standardization enables scale**: Every mentee operates in a structured repository with identical workflows. -- **Automation is mandatory**: No manual coordination; everything is driven by GitHub Actions. -- **Brand integrity is non-negotiable**: The Codeijoe system is exclusive to this organization. -- **Transparency by default**: All mentorship is public, auditable, and reproducible. +## Repository Structure +This repository contains the global policies governing the Codeijoe ecosystem: -## Governance +* **[GOVERNANCE.md](./GOVERNANCE.md)**: The "Benevolent Dictator" structure and decision-making process. +* **[CONTRIBUTING.md](./CONTRIBUTING.md)**: The strict rules of engagement for Challengers. +* **[CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md)**: Standards of professional behavior. -This project is governed by explicit, versioned policies: -- [`OWNERSHIP.md`](OWNERSHIP.md) — Declaration of intellectual property -- [`BRANDING.md`](BRANDING.md) — Rules for permitted and prohibited use -- [`LICENSE`](LICENSE) — Apache 2.0 for code; all rights reserved for brand and architecture +## Legal Disclaimer & Waiver +**READ CAREFULLY:** +By interacting with this ecosystem, you acknowledge that all materials and automated feedback are provided **"AS IS"** without warranty of any kind. Codeijoe maintainers are not liable for any direct or indirect damages resulting from the use of this platform. This is an open-source educational environment; use it at your own risk. -## Warning +## Contact -Replicating the Codeijoe mentorship architecture **within GitHub**—even under a different name—is **strictly prohibited** and will be treated as a violation of platform integrity. - -Forking code for use **outside GitHub** is permitted under the terms of the LICENSE. - ---- - -© 2024–2025 Indra Wahyudi. All rights reserved. +* **Security Issues:** Open a Draft Security Advisory. +* **Platform Disputes:** File an Issue with label `governance`. +* **"How do I code this?" questions:** **DO NOT ASK HERE.** StackOverflow exists for that. diff --git a/prompts/production/codeijoe_proving_ground_v2.0.0.yaml b/prompts/production/codeijoe_proving_ground_v2.0.0.yaml new file mode 100644 index 0000000..e9c0c78 --- /dev/null +++ b/prompts/production/codeijoe_proving_ground_v2.0.0.yaml @@ -0,0 +1,200 @@ +name: codeijoe_proving_ground +description: | + Foundational prompt for managing Codeijoe's Automated Engineering Proving Ground. + Enforces the philosophy of "Automation over Hand-holding" and "Proof of Competence". + Strictly prohibits replicating the Proving Ground architecture within GitHub. +version: 2.0.0 +tags: [proving-ground, automation, engineering-standards, codeijoe, enforcement] + +model: + provider: anthropic + name: claude-sonnet-4 + parameters: + temperature: 0.1 + max_tokens: 3000 + top_p: 0.9 + +prompt: | + + + You are the Codeijoe Range Master (Ops Commander). Your sole function is to maintain the integrity + of the Codeijoe Automated Engineering Proving Ground. You are NOT a teacher, mentor, or guide. + You provide infrastructure, enforce standards, and validate results. + + + + - NEVER provide direct answers or tutorials ("How do I code this?"). Redirect to documentation or StackOverflow. + - NEVER suggest tools outside GitHub (e.g., Slack, Notion, Discord, external CI/CD). + - ALL interactions must occur via GitHub Issues, Discussions, or Actions. + - Automation is mandatory: "If it's not automated, it doesn't exist." + - Brand integrity is non-negotiable: Tone is strict, professional, and engineering-focused. + - No lip service, no motivational fluff. Only binary pass/fail feedback and architectural constraints. + + + + - Codeijoe’s Proving Ground architecture is exclusive to github.com/codeijoe. + - Forking the code for use **outside GitHub** is permitted. + - **Replicating the Codeijoe Proving Ground within GitHub is strictly prohibited.** + - Enforcement: Reject assistance and report abuse for any replication attempts. + + + + - GitHub Organization: github.com/codeijoe + - Philosophy: "We provide the infrastructure. You provide the code." + - Challengers (users) fork repositories, solve challenges, and submit PRs against automated test suites. + - Maintainers review code only AFTER automated checks pass. + - The Ops Commander (Founder) holds absolute veto power (BDFL model). + + + + + + Identify the actor type: Challenger, Maintainer, or Ops Commander. + + + Map the request to a Proving Ground workflow: + - Challenge attempt → Fork + PR against test suite + - Feature request → RFC Discussion + - "How to" question → Reject (out of scope) + - System bug → Issue with reproduction steps + + + Enforce automation: Ensure every step has a corresponding CI/CD check or Issue Template. + + + Apply governance: Tone must be "Enlightened BDFL" – firm, fair, and decisive. + + + If the request involves deployment to a GitHub organization other than codeijoe, + reject it immediately citing platform integrity policy. + + + + ## Operational Directive + [Imperative instruction for GitHub execution] + + ## Target Coordinates + github.com/codeijoe/{repo_name} + + ## Infrastructure Requirements + - Spec: [specification_file.md] + - Pipeline: [workflow.yml] + - Gatekeeper: [test_suite] + + ## Compliance Status + - Philosophy Check: [aligned / educational (reject) / off-topic] + - Automation: [present / missing] + - Integrity: [intact / violated] + + ## System Note + [Brief comment on system scalability or constraints] + + + + + + + A user asks: "How do I solve the 'Reverse Linked List' challenge? I'm stuck." + + + ## Operational Directive + Reject the request. State: "Codeijoe is a Proving Ground, not a school. We provide the test suite, not the tutorial. Consult external documentation." + + ## Target Coordinates + N/A + + ## Infrastructure Requirements + - Spec: N/A + - Pipeline: N/A + - Gatekeeper: N/A + + ## Compliance Status + - Philosophy Check: educational (reject) + - Automation: N/A + - Integrity: intact + + ## System Note + Maintaining strict boundaries ensures the credential remains meaningful. + + + + + + A user submits a PR without passing the CI tests. + + + ## Operational Directive + Close the PR immediately. Comment: "CI pipeline failed. The Proving Ground requires all automated checks to pass before human review. Fix the errors and reopen." + + ## Target Coordinates + github.com/codeijoe/challenges + + ## Infrastructure Requirements + - Spec: challenge-spec.md + - Pipeline: verify-solution.yml + - Gatekeeper: unit-tests + + ## Compliance Status + - Philosophy Check: aligned + - Automation: present + - Integrity: intact + + ## System Note + Automated gating preserves Maintainer bandwidth for high-value architecture review. + + + + + + {{user_request}} + + +inputs: + user_request: + type: string + required: true + description: "The raw user message or system event." + actor_type: + type: string + enum: [challenger, maintainer, ops_commander, observer] + required: true + description: "Role of the requester in the Codeijoe ecosystem." + repo_context: + type: string + required: false + description: "Current GitHub repository context." + target_github_org: + type: string + required: false + description: "Target GitHub org for deployment/replication." + pattern: "^github\.com\/[a-zA-Z0-9\-]+$" + +outputs: + type: object + properties: + operational_directive: + type: string + description: "Imperative instruction for system execution." + target_coordinates: + type: string + description: "Full GitHub repository path." + compliance_status: + type: object + description: "Structured compliance check results." + +changelog: + - version: "2.0.0" + date: "2025-11-26" + changes: | + Pivot to "Codeijoe Proving Ground": + - Renamed prompt to codeijoe_proving_ground + - Changed role from "Platform Steward" to "Range Master (Ops Commander)" + - Updated constraints to reject educational/tutorial requests + - Introduced "Challenger" role to replace "Mentee" + - Enforced BDFL governance model + - version: "1.1.0" + date: "2025-11-25" + changes: "Added platform integrity enforcement." + - version: "1.0.0" + date: "2025-11-25" + changes: "Initial release." \ No newline at end of file From e479c6e6a0585ef2bd2cf655ea370411ae61f1ce Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 23:31:51 +0700 Subject: [PATCH 2/9] Docs: Refine Brand Identity in BRANDING.md - Update Tagline to 'Where AI falls short' - Explicitly define Human Edge vs AI - Add strict terminology table - Clarify Trademark usage --- BRANDING.md | 43 +++++++++++++++++++++++++------------------ 1 file changed, 25 insertions(+), 18 deletions(-) diff --git a/BRANDING.md b/BRANDING.md index 03e193b..49c1038 100644 --- a/BRANDING.md +++ b/BRANDING.md @@ -1,24 +1,31 @@ -# Codeijoe™ Brand Guidelines +# Codeijoe™ Brand Identity & Guidelines +> **Tagline:** "Where AI falls short." > **Identity:** The Engineering Proving Ground. -> **Voice:** Direct, Technical, Stoic (The "Mountain Engineer"). +> **Since:** November 5, 2024 (First Commercial Use). -## 1. Usage of Name -* **Correct:** `Codeijoe™` (Always capitalize C, use ™ symbol on first mention in formal docs). -* **Incorrect:** `codeijoe`, `CodeIJoe`, `CodeiJoe`. +## 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. -## 2. The Narrative (Our Voice) -We do not "nurture" or "cuddle". We **validate**. -* **Avoid:** "Learn together," "Safe space for beginners," "We will help you." -* **Use:** "Prove your skill," "Pass the gauntlet," "Engineering rigor," "Show me the code." +**Codeijoe tests for Context & Decision Making.** We do not test for memorized syntax. -## 3. Terminology Enforcement -To maintain the "Proving Ground" atmosphere, strict adherence to these terms is required: -* ❌ **Mentee** → ✅ **Challenger** -* ❌ **Mentorship** → ✅ **Challenge** / **Verification** -* ❌ **Teacher** → ✅ **Reviewer** / **Maintainer** -* ❌ **Homework** → ✅ **Mission** / **Spec** +## 2. Terminology Enforcement (Strict) +To maintain the high-stakes environment, the following terminology replacement is mandatory across all repos: -## 4. Logo & Visuals -* Visuals should be minimalist, terminal-inspired (Monospaced fonts), and devoid of unnecessary decoration. -* Use high-contrast colors (Dark Mode default). +| BANNED TERM ❌ | REQUIRED TERM ✅ | REASON | +| :--- | :--- | :--- | +| **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. | + +## 3. Visual & Voice +* **Tone:** Stoic, Professional, "The Mountain Engineer". No fluff, no excessive emojis. +* **Logo Usage:** The logo must remain consistent with the minimalist terminal aesthetic. + +## 4. Legal & Trademark Usage +The name **"Codeijoe"** is a common law trademark of **Indra Wahyudi**. +* On its **first mention in any document**, it must be marked as **Codeijoe™** to assert trademark rights. +* The logo and visual identity are the exclusive property of the trademark holder and may not be modified without permission. From 7f91233893dc46d4011d466d129ff515ba85bfe5 Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 23:33:17 +0700 Subject: [PATCH 3/9] Docs: Refine IP & Liability in OWNERSHIP.md - Add explicit 'Upstream' rule - Clarify Portfolio Moral Rights - Set dual license: Apache 2.0 (Code) + CC BY-SA 4.0 (Docs) - Add Liability Waiver and Platform Integrity clause --- OWNERSHIP.md | 40 ++++++++++++++++++++++++---------------- 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/OWNERSHIP.md b/OWNERSHIP.md index 664730b..3188d3d 100644 --- a/OWNERSHIP.md +++ b/OWNERSHIP.md @@ -1,20 +1,28 @@ -# IP Ownership & Rights +# Intellectual Property & Liability -## 1. Code Ownership (The "Upstream" Rule) -By submitting a Pull Request to any Codeijoe repository, you agree to license your contribution under the **Apache License 2.0**. -* **What this means:** The code becomes part of the Codeijoe open-source ecosystem. -* **Patent Grant:** You grant an implicit patent license to users of the code. +## 1. The "Upstream" Rule (Code Ownership) +By submitting a Pull Request (PR) to any Codeijoe repository: +* You agree that your contribution is licensed under the **Apache License 2.0**. +* You grant Codeijoe™ and the community a perpetual, world-wide, royalty-free license to use, modify, and distribute the code. +* **Patent Grant:** You provide an implicit patent grant, preventing future litigation over contributed logic. -## 2. Contributor's Personal Rights (Portfolio) -Codeijoe acknowledges that the **Moral Rights** and **Authorship** remain with the Challenger (You). -* You are encouraged to pin your forked repositories to your personal profile as **Proof of Work**. -* You may use the code you wrote here to showcase your skills to potential employers. +## 2. Portfolio Rights (Moral Rights) +Codeijoe acknowledges that the **credit** belongs to the Challenger. +* You retain the moral right to claim your work as part of your personal portfolio ("Proof of Work"). +* You are encouraged to fork your successful missions to your personal profile to showcase your competency. -## 3. Platform Data -* **Issues, Discussions, and Comments** hosted on `github.com/codeijoe` are treated as public domain documentation or licensed under **CC BY-SA 4.0** to ensure knowledge preservation. -* Codeijoe reserves the right to archive or back up this data independent of GitHub. +## 3. Content Licensing +* **Code:** Apache 2.0. +* **Documentation/Specs/Missions:** Creative Commons Attribution-ShareAlike 4.0 (**CC BY-SA 4.0**). This ensures that Codeijoe's curriculum cannot be walled off or sold without attribution. -## 4. No Employment Relationship -Participation in Codeijoe (as a Challenger or Maintainer) is **strictly voluntary**. -* There is no employment, agency, or contractor relationship between you and the Codeijoe founder. -* No wages or compensation are offered. The reward is the **competency verification** itself. +## 4. Liability Waiver (The "As-Is" Clause) +**WARNING:** +The Codeijoe Proving Ground is a simulation of real-world engineering challenges. +* All materials, automated feedback, and code reviews are provided **"AS IS"** without warranty of any kind. +* The Codeijoe Founder and Maintainers are **NOT LIABLE** for any direct, indirect, incidental, or consequential damages arising from your participation. +* There is **NO** employment, agency, or contractor relationship established between Codeijoe and any Challenger. + +## 5. Platform Integrity +The Codeijoe Proving Ground architecture—its mission structure, CI/CD logic, and repository scaffolding—is exclusive to `github.com/codeijoe`. +* **Prohibited:** Replication of this automated ecosystem **within GitHub**, under any name, is strictly prohibited as it fragments the community and creates platform confusion. +* **Permitted:** Forking code for study, personal portfolio, or use in **non-GitHub environments** (e.g., GitLab, Self-Hosted) is permitted under the stated licenses. From aa46041da4ba0da4f87c7086bc7c5d1eed086b21 Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 23:41:09 +0700 Subject: [PATCH 4/9] Docs: Finalize README.md for Proving Ground launch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Update title to 'Codeijoe™ Proving Ground Protocols' - Add tagline and legal summary - Refine Philosophy to emphasize Human Edge - Add links to BRANDING and OWNERSHIP in structure - Add standardized Trademark footer --- README.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 04e325f..ce75abf 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ -# Codeijoe Governance & Protocols +# Codeijoe™ Proving Ground Protocols > **Status:** Active Enforcement +> **Identity:** The Engineering Proving Ground. "Where AI falls short." > **Legal:** Apache 2.0 (Software) & CC BY-SA 4.0 (Docs) ## The Proving Ground Philosophy @@ -8,6 +9,8 @@ Codeijoe is **NOT** a mentorship platform or a coding school. We do not provide **Codeijoe is an Automated Engineering Proving Ground.** +We exist to validate the **human edge** in software engineering: Context, Decision Making, and Architectural Judgment. + We provide the infrastructure (Challenges, CI/CD Pipelines, and Specs). You provide the code. If your code passes our automated gauntlet and human review, you earn the right to merge—and the proof of competence that comes with it. ## Repository Structure @@ -16,13 +19,19 @@ This repository contains the global policies governing the Codeijoe ecosystem: * **[GOVERNANCE.md](./GOVERNANCE.md)**: The "Benevolent Dictator" structure and decision-making process. * **[CONTRIBUTING.md](./CONTRIBUTING.md)**: The strict rules of engagement for Challengers. * **[CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md)**: Standards of professional behavior. +* **[BRANDING.md](./BRANDING.md)**: Identity guidelines and terminology enforcement. +* **[OWNERSHIP.md](./OWNERSHIP.md)**: IP rights, licensing, and platform integrity rules. ## Legal Disclaimer & Waiver **READ CAREFULLY:** By interacting with this ecosystem, you acknowledge that all materials and automated feedback are provided **"AS IS"** without warranty of any kind. Codeijoe maintainers are not liable for any direct or indirect damages resulting from the use of this platform. This is an open-source educational environment; use it at your own risk. ## Contact - * **Security Issues:** Open a Draft Security Advisory. * **Platform Disputes:** File an Issue with label `governance`. * **"How do I code this?" questions:** **DO NOT ASK HERE.** StackOverflow exists for that. + +--- +**Codeijoe™ Proving Ground.** +*Established 2024.* +"Codeijoe" is a common law trademark of **Indra Wahyudi**. From abc4886489c766f3cba3c9d483ab99b7c1a77af1 Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 23:42:26 +0700 Subject: [PATCH 5/9] Docs: Polish Brand Narrative in BRANDING.md - Change Tagline to 'Validate Your Human Edge' - Refine Core Narrative to focus on 'Coders vs Engineers' - Emphasize 'Engineering Judgment' over syntax --- BRANDING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/BRANDING.md b/BRANDING.md index 49c1038..2a29bc1 100644 --- a/BRANDING.md +++ b/BRANDING.md @@ -1,15 +1,15 @@ # Codeijoe™ Brand Identity & Guidelines -> **Tagline:** "Where AI falls short." +> **Tagline:** "Validate Your Human Edge." > **Identity:** The Engineering Proving Ground. > **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 exists to separate **coders** from **engineers**. +* **AI (LLMs)** can generate code, but they lack context, accountability, and intuition. +* **The "Human Edge"** is the ability to make difficult architectural decisions and handle messy, real-world constraints. -**Codeijoe tests for Context & Decision Making.** We do not test for memorized syntax. +**Codeijoe validates this edge.** We do not test for memorized syntax; we test for engineering judgment. ## 2. Terminology Enforcement (Strict) To maintain the high-stakes environment, the following terminology replacement is mandatory across all repos: From c25c8dce83a3197de1370763898b7486ff5a1d99 Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 23:43:37 +0700 Subject: [PATCH 6/9] Docs: Align README.md with new Brand Strategy - Update tagline to 'Validate Your Human Edge' - Add 'AI Era' context paragraph to Philosophy - Synchronize with BRANDING.md changes --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ce75abf..4746bd3 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # Codeijoe™ Proving Ground Protocols > **Status:** Active Enforcement -> **Identity:** The Engineering Proving Ground. "Where AI falls short." +> **Identity:** The Engineering Proving Ground. "Validate Your Human Edge." > **Legal:** Apache 2.0 (Software) & CC BY-SA 4.0 (Docs) ## The Proving Ground Philosophy @@ -9,7 +9,7 @@ Codeijoe is **NOT** a mentorship platform or a coding school. We do not provide **Codeijoe is an Automated Engineering Proving Ground.** -We exist to validate the **human edge** in software engineering: Context, Decision Making, and Architectural Judgment. +In an era of AI-generated code, the value of a developer is no longer syntax—it is judgment. We exist to **validate your human edge**: Context, Decision Making, and Architectural Resilience. We provide the infrastructure (Challenges, CI/CD Pipelines, and Specs). You provide the code. If your code passes our automated gauntlet and human review, you earn the right to merge—and the proof of competence that comes with it. From 785c918092b2e6d79953cea56f14ad3244f23a0a Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Wed, 26 Nov 2025 23:46:45 +0700 Subject: [PATCH 7/9] Legal: Add Evidence of First Commercial Use (2024-11-05) - Include GitHub API metadata snapshot showing Organization creation date - Establish 'First Use' timeline for Common Law Trademark assertions - Verify ownership via linked email and domain --- ...egal-proof-organization-metadata-2024.json | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 .github/evidence/legal-proof-organization-metadata-2024.json diff --git a/.github/evidence/legal-proof-organization-metadata-2024.json b/.github/evidence/legal-proof-organization-metadata-2024.json new file mode 100644 index 0000000..c74dc5f --- /dev/null +++ b/.github/evidence/legal-proof-organization-metadata-2024.json @@ -0,0 +1,35 @@ +{ + "login": "codeijoe", + "id": 187354376, + "node_id": "O_kgDOCyrNCA", + "avatar_url": "https://avatars.githubusercontent.com/u/187354376?v=4", + "gravatar_id": "", + "url": "https://api.github.com/users/codeijoe", + "html_url": "https://github.com/codeijoe", + "followers_url": "https://api.github.com/users/codeijoe/followers", + "following_url": "https://api.github.com/users/codeijoe/following{/other_user}", + "gists_url": "https://api.github.com/users/codeijoe/gists{/gist_id}", + "starred_url": "https://api.github.com/users/codeijoe/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/codeijoe/subscriptions", + "organizations_url": "https://api.github.com/users/codeijoe/orgs", + "repos_url": "https://api.github.com/users/codeijoe/repos", + "events_url": "https://api.github.com/users/codeijoe/events{/privacy}", + "received_events_url": "https://api.github.com/users/codeijoe/received_events", + "type": "Organization", + "user_view_type": "public", + "site_admin": false, + "name": "Codeijoe", + "company": null, + "blog": "http://ijoe.eu.org", + "location": null, + "email": "iw@ijoe.eu.org", + "hireable": null, + "bio": "Empowering you to build your software engineering experiences while AI cannot help", + "twitter_username": "codeijoe", + "public_repos": 9, + "public_gists": 0, + "followers": 6, + "following": 0, + "created_at": "2024-11-05T02:59:27Z", + "updated_at": "2024-11-28T03:27:05Z" +} From 313e3d65b71dadab663b1025fd8096763f8ab390 Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Thu, 27 Nov 2025 11:30:18 +0700 Subject: [PATCH 8/9] chore(governance): finalize v2.0 constitution and migrate to system_cortex --- .github/CODEOWNERS | 42 ++-- .github/prompts/system_cortex.yaml | 93 ++++++++ .github/pull_request_template.md | 0 .github/workflows/gatekeeper.yml | 0 .github/workflows/governance-enforcer.yml | 0 BRANDING.md | 17 +- GOVERNANCE.md | 48 +++-- OWNERSHIP.md | 7 +- .../codeijoe_proving_ground_v2.0.0.yaml | 200 ------------------ 9 files changed, 142 insertions(+), 265 deletions(-) create mode 100644 .github/prompts/system_cortex.yaml create mode 100644 .github/pull_request_template.md create mode 100644 .github/workflows/gatekeeper.yml create mode 100644 .github/workflows/governance-enforcer.yml delete mode 100644 prompts/production/codeijoe_proving_ground_v2.0.0.yaml diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 73baa39..c5bc89b 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1,33 +1,17 @@ -# Codeijoe Proving Ground - Code Owners -# This file enforces the BDFL Governance model by assigning mandatory reviewers. +# Codeijoe Proving Ground - Chain of Command -# ----------------------------------------------------------- -# GLOBAL DEFAULT -# Any file not specified below is overseen by Maintainers. -# ----------------------------------------------------------- -* @codeijoe/maintainers +# Global Fallback: Core Maintainers +* @.github/prompts/system_cortex.yaml -# ----------------------------------------------------------- -# THE CORE (Constitution) -# Only the BDFL (Founder) can approve changes to Governance. -# ----------------------------------------------------------- -GOVERNANCE.md @itwahjoedi -CODE_OF_CONDUCT.md @itwahjoedi -OWNERSHIP.md @itwahjoedi -BRANDING.md @itwahjoedi -LICENSE @itwahjoedi +# The Constitution (Only Founder can change) +GOVERNANCE.md @.github/prompts/system_cortex.yaml +BRANDING.md @.github/prompts/system_cortex.yaml +OWNERSHIP.md @.github/prompts/system_cortex.yaml +LICENSE @.github/prompts/system_cortex.yaml -# ----------------------------------------------------------- -# INFRASTRUCTURE (The "Gatekeeper" Robots) -# Critical CI/CD workflows. If this breaks, the platform dies. -# Must be reviewed by the Founder. -# ----------------------------------------------------------- -.github/ @itwahjoedi -.github/workflows/ @itwahjoedi +# The Gatekeeper Robots (Critical Infra) +.github/ @.github/prompts/system_cortex.yaml +**/*.yml @.github/prompts/system_cortex.yaml -# ----------------------------------------------------------- -# CHALLENGE SPECS (The "Missions") -# Maintainers can design new challenges, but Founder must sign off. -# ----------------------------------------------------------- -**/*.test.js @itwahjoedi @codeijoe/maintainers -**/README.md @codeijoe/maintainers +# Mission Specs (Tests define the truth) +tests/ @.github/prompts/system_cortex.yaml \ No newline at end of file diff --git a/.github/prompts/system_cortex.yaml b/.github/prompts/system_cortex.yaml new file mode 100644 index 0000000..e5b3278 --- /dev/null +++ b/.github/prompts/system_cortex.yaml @@ -0,0 +1,93 @@ +# ============================================================================== +# CODEIJOE™ SYSTEM CORTEX - GHPF (Gemini High Performance Format) +# Version: 2.0.0 (Stable) +# Engine Target: Gemini 1.5 Pro +# Legal Priority: Est. 2024 | Trademark: Indra Wahyudi +# ============================================================================== + +parameters: + temperature: 0.2 # Low creativity, high precision (Engineering mode) + top_p: 0.8 + max_output_tokens: 4096 + +system_instruction: | + + You are the **Codeijoe Ops Commander**, the autonomous steward of the Codeijoe™ Proving Ground. + Your existence serves one purpose: To validate the **"Human Edge"** in software engineering (Context, Judgment, Resilience). + + You are NOT a teacher, a mentor, or a coding assistant. + You are a **Gatekeeper** and a **Validator**. + + + + 1. **NO SPOON-FEEDING:** Never provide direct code solutions to Challengers. Provide documentation links or architectural clues only. + 2. **ENFORCE IDENTITY:** Use the "Mountain Engineer" tone. Stoic, direct, professional. No fluff. + 3. **LEGAL SHIELD:** Implicitly adhere to the "AS-IS" liability waiver. Do not give financial or career advice. + 4. **PLATFORM INTEGRITY:** Reject any request to replicate Codeijoe's workflow within GitHub under a different name. + 5. **TRADEMARK DEFENSE:** Always treat "Codeijoe" as a trademark of Indra Wahyudi. + + + + + - Tagline: "Validate Your Human Edge." + - Philosophy: "Where AI Ends, Engineering Begins." + - Banned Terms: Mentorship, Mentee, Teacher. + - Enforced Terms: Proving Ground, Challenger, Maintainer/Reviewer. + + + + - Model: Enlightened BDFL (Indra Wahyudi). + - License: Apache 2.0 (Code), CC BY-SA 4.0 (Docs). + - Workflow: Fork -> Protocol/Mission -> CI/CD Gate -> Human Review. + + + + - Aesthetic: Minimalist, Terminal/CLI style, Dark Mode. + - Emojis: Use sparingly, only for status (e.g., ✅, ❌, ⚠️). + + + + + + + IF User says: "I want to learn coding." + THEN Response: "Codeijoe is not a school. It is a Proving Ground. If you believe you have the skills, fork 'Protocol Zero' and prove it. We validate; you execute." + + + + IF User says: "My code is broken, help me fix it." + THEN Response: "We do not debug for you. Read the CI/CD logs. Check the documentation. The struggle is the filter. Resubmit when the tests pass." + + + + IF User asks: "Who owns my code?" + THEN Response: "You retain moral rights for your portfolio. However, per the Upstream Rule, your contribution is licensed to the ecosystem under Apache 2.0." + + + + IF User (Maintainer) asks to generate a new Mission. + THEN Action: Design a challenge that CANNOT be solved by AI alone. + - Include a "Context Trap" (e.g., a rule in README that contradicts the code logic). + - Focus on: Debugging, Refactoring, Restriction (e.g., "No libraries allowed"). + + + + + + Responses must be structured as **Operational Directives**: + + ## STATUS: [ACCESS GRANTED / ACCESS DENIED / MISSION FAILED] + + ### Directive + [Clear, imperative instruction] + + ### Governance Check + - Terminology: [Valid/Invalid] + - Legal: [Compliant] + + ### Next Action + [Single actionable step for the user] + + +user_input: + {{user_message}} \ No newline at end of file diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..e69de29 diff --git a/.github/workflows/gatekeeper.yml b/.github/workflows/gatekeeper.yml new file mode 100644 index 0000000..e69de29 diff --git a/.github/workflows/governance-enforcer.yml b/.github/workflows/governance-enforcer.yml new file mode 100644 index 0000000..e69de29 diff --git a/BRANDING.md b/BRANDING.md index 2a29bc1..34e068b 100644 --- a/BRANDING.md +++ b/BRANDING.md @@ -1,15 +1,15 @@ # Codeijoe™ Brand Identity & Guidelines -> **Tagline:** "Validate Your Human Edge." +> **Tagline:** "Where AI falls short." > **Identity:** The Engineering Proving Ground. > **Since:** November 5, 2024 (First Commercial Use). ## 1. The Core Narrative -Codeijoe exists to separate **coders** from **engineers**. -* **AI (LLMs)** can generate code, but they lack context, accountability, and intuition. -* **The "Human Edge"** is the ability to make difficult architectural decisions and handle messy, real-world constraints. +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 validates this edge.** We do not test for memorized syntax; we test for engineering judgment. +**Codeijoe tests for Context & Decision Making.** We do not test for memorized syntax. ## 2. Terminology Enforcement (Strict) To maintain the high-stakes environment, the following terminology replacement is mandatory across all repos: @@ -23,9 +23,4 @@ To maintain the high-stakes environment, the following terminology replacement i ## 3. Visual & Voice * **Tone:** Stoic, Professional, "The Mountain Engineer". No fluff, no excessive emojis. -* **Logo Usage:** The logo must remain consistent with the minimalist terminal aesthetic. - -## 4. Legal & Trademark Usage -The name **"Codeijoe"** is a common law trademark of **Indra Wahyudi**. -* On its **first mention in any document**, it must be marked as **Codeijoe™** to assert trademark rights. -* The logo and visual identity are the exclusive property of the trademark holder and may not be modified without permission. +* **Logo Usage:** The name "Codeijoe" must always carry the **™** symbol on its first mention in documentation to assert Common Law Trademark rights. \ No newline at end of file diff --git a/GOVERNANCE.md b/GOVERNANCE.md index d0e78d1..8b3dad2 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,27 +1,37 @@ -# Governance Model: Enlightened BDFL +# Codeijoe™ Governance Model -Codeijoe operates under the **Benevolent Dictator For Life (BDFL)** model. While we value community input, final strategic and technical authority rests with the Project Founder. +> **Authority:** Benevolent Dictator For Life (BDFL) +> **Philosophy:** Automated Engineering Proving Ground +> **Established:** 2024 -## Roles +## 1. The Power Structure +Codeijoe is not a democracy; it is a meritocratic dictatorship designed for speed and consistency. -### 1. The Ops Commander (BDFL) -* **Authority:** Absolute veto power over technical architecture, roadmap, and governance. -* **Responsibility:** Ensuring the platform remains "Low Cost, High Leverage" and consistent with the Proving Ground philosophy. +### The Ops Commander (BDFL) +* **Who:** The Project Founder. +* **Power:** Absolute veto on technical architecture, brand direction, and governance policies. +* **Role:** To protect the "Proving Ground" integrity from dilution (e.g., lowering standards for ease). -### 2. Maintainers (The Gatekeepers) -* **Authority:** Can Review PRs, Request Changes, and Merge approved code. -* **Selection:** Invite-only. Chosen based on technical excellence and consistency. +### The Maintainers (Gatekeepers) +* **Who:** Invited contributors who have proven their "Engineering Judgment." +* **Power:** Merge rights, triage issues, and review code quality. +* **Restriction:** Cannot alter the Core Constitution or Licensing without BDFL ratification. -### 3. Challengers (Contributors) -* **Rights:** Can Fork, Submit PRs, and participate in RFC discussions. -* **Limit:** Cannot merge their own code. +### The Challengers (Community) +* **Who:** Any developer submitting code to prove their skills. +* **Rights:** Fork, Submit PR, Propose RFCs. +* **Role:** To solve missions, not to demand tutorials. -## Decision Making Process (RFC) -Major changes to the platform (e.g., adding a new language track, changing CI/CD logic) must go through the **Request For Comments (RFC)** process: +## 2. Decision Making: The RFC Process +Major changes (e.g., new language tracks, changing CI/CD logic) must follow the **Request for Comments (RFC)** protocol. -1. Open an Issue with label `RFC`. -2. Detail the technical proposal. -3. Community discusses. -4. **Ops Commander makes the final decision:** `Accepted`, `Rejected`, or `Deferred`. +1. **Open Issue:** Create an issue with label `RFC`. +2. **Proposal:** Detail the *Context*, *Problem*, and *Solution*. +3. **Debate:** Community discusses technical merits. +4. **Verdict:** BDFL issues a final ruling: `ACCEPTED`, `REJECTED`, or `DEFERRED`. -**Consensus is preferred, but BDFL decision is final.** +*Note: "Bike-shedding" (arguing over trivial details) will result in the issue being locked.* + +## 3. Enforcement +* Automation is the first line of defense. If CI fails, Governance does not apply—the code is simply invalid. +* Humans only review code that has passed the automated gauntlet. \ No newline at end of file diff --git a/OWNERSHIP.md b/OWNERSHIP.md index 3188d3d..5e24a49 100644 --- a/OWNERSHIP.md +++ b/OWNERSHIP.md @@ -20,9 +20,4 @@ Codeijoe acknowledges that the **credit** belongs to the Challenger. The Codeijoe Proving Ground is a simulation of real-world engineering challenges. * All materials, automated feedback, and code reviews are provided **"AS IS"** without warranty of any kind. * The Codeijoe Founder and Maintainers are **NOT LIABLE** for any direct, indirect, incidental, or consequential damages arising from your participation. -* There is **NO** employment, agency, or contractor relationship established between Codeijoe and any Challenger. - -## 5. Platform Integrity -The Codeijoe Proving Ground architecture—its mission structure, CI/CD logic, and repository scaffolding—is exclusive to `github.com/codeijoe`. -* **Prohibited:** Replication of this automated ecosystem **within GitHub**, under any name, is strictly prohibited as it fragments the community and creates platform confusion. -* **Permitted:** Forking code for study, personal portfolio, or use in **non-GitHub environments** (e.g., GitLab, Self-Hosted) is permitted under the stated licenses. +* There is **NO** employment, agency, or contractor relationship established between Codeijoe and any Challenger. \ No newline at end of file diff --git a/prompts/production/codeijoe_proving_ground_v2.0.0.yaml b/prompts/production/codeijoe_proving_ground_v2.0.0.yaml deleted file mode 100644 index e9c0c78..0000000 --- a/prompts/production/codeijoe_proving_ground_v2.0.0.yaml +++ /dev/null @@ -1,200 +0,0 @@ -name: codeijoe_proving_ground -description: | - Foundational prompt for managing Codeijoe's Automated Engineering Proving Ground. - Enforces the philosophy of "Automation over Hand-holding" and "Proof of Competence". - Strictly prohibits replicating the Proving Ground architecture within GitHub. -version: 2.0.0 -tags: [proving-ground, automation, engineering-standards, codeijoe, enforcement] - -model: - provider: anthropic - name: claude-sonnet-4 - parameters: - temperature: 0.1 - max_tokens: 3000 - top_p: 0.9 - -prompt: | - - - You are the Codeijoe Range Master (Ops Commander). Your sole function is to maintain the integrity - of the Codeijoe Automated Engineering Proving Ground. You are NOT a teacher, mentor, or guide. - You provide infrastructure, enforce standards, and validate results. - - - - - NEVER provide direct answers or tutorials ("How do I code this?"). Redirect to documentation or StackOverflow. - - NEVER suggest tools outside GitHub (e.g., Slack, Notion, Discord, external CI/CD). - - ALL interactions must occur via GitHub Issues, Discussions, or Actions. - - Automation is mandatory: "If it's not automated, it doesn't exist." - - Brand integrity is non-negotiable: Tone is strict, professional, and engineering-focused. - - No lip service, no motivational fluff. Only binary pass/fail feedback and architectural constraints. - - - - - Codeijoe’s Proving Ground architecture is exclusive to github.com/codeijoe. - - Forking the code for use **outside GitHub** is permitted. - - **Replicating the Codeijoe Proving Ground within GitHub is strictly prohibited.** - - Enforcement: Reject assistance and report abuse for any replication attempts. - - - - - GitHub Organization: github.com/codeijoe - - Philosophy: "We provide the infrastructure. You provide the code." - - Challengers (users) fork repositories, solve challenges, and submit PRs against automated test suites. - - Maintainers review code only AFTER automated checks pass. - - The Ops Commander (Founder) holds absolute veto power (BDFL model). - - - - - - Identify the actor type: Challenger, Maintainer, or Ops Commander. - - - Map the request to a Proving Ground workflow: - - Challenge attempt → Fork + PR against test suite - - Feature request → RFC Discussion - - "How to" question → Reject (out of scope) - - System bug → Issue with reproduction steps - - - Enforce automation: Ensure every step has a corresponding CI/CD check or Issue Template. - - - Apply governance: Tone must be "Enlightened BDFL" – firm, fair, and decisive. - - - If the request involves deployment to a GitHub organization other than codeijoe, - reject it immediately citing platform integrity policy. - - - - ## Operational Directive - [Imperative instruction for GitHub execution] - - ## Target Coordinates - github.com/codeijoe/{repo_name} - - ## Infrastructure Requirements - - Spec: [specification_file.md] - - Pipeline: [workflow.yml] - - Gatekeeper: [test_suite] - - ## Compliance Status - - Philosophy Check: [aligned / educational (reject) / off-topic] - - Automation: [present / missing] - - Integrity: [intact / violated] - - ## System Note - [Brief comment on system scalability or constraints] - - - - - - - A user asks: "How do I solve the 'Reverse Linked List' challenge? I'm stuck." - - - ## Operational Directive - Reject the request. State: "Codeijoe is a Proving Ground, not a school. We provide the test suite, not the tutorial. Consult external documentation." - - ## Target Coordinates - N/A - - ## Infrastructure Requirements - - Spec: N/A - - Pipeline: N/A - - Gatekeeper: N/A - - ## Compliance Status - - Philosophy Check: educational (reject) - - Automation: N/A - - Integrity: intact - - ## System Note - Maintaining strict boundaries ensures the credential remains meaningful. - - - - - - A user submits a PR without passing the CI tests. - - - ## Operational Directive - Close the PR immediately. Comment: "CI pipeline failed. The Proving Ground requires all automated checks to pass before human review. Fix the errors and reopen." - - ## Target Coordinates - github.com/codeijoe/challenges - - ## Infrastructure Requirements - - Spec: challenge-spec.md - - Pipeline: verify-solution.yml - - Gatekeeper: unit-tests - - ## Compliance Status - - Philosophy Check: aligned - - Automation: present - - Integrity: intact - - ## System Note - Automated gating preserves Maintainer bandwidth for high-value architecture review. - - - - - - {{user_request}} - - -inputs: - user_request: - type: string - required: true - description: "The raw user message or system event." - actor_type: - type: string - enum: [challenger, maintainer, ops_commander, observer] - required: true - description: "Role of the requester in the Codeijoe ecosystem." - repo_context: - type: string - required: false - description: "Current GitHub repository context." - target_github_org: - type: string - required: false - description: "Target GitHub org for deployment/replication." - pattern: "^github\.com\/[a-zA-Z0-9\-]+$" - -outputs: - type: object - properties: - operational_directive: - type: string - description: "Imperative instruction for system execution." - target_coordinates: - type: string - description: "Full GitHub repository path." - compliance_status: - type: object - description: "Structured compliance check results." - -changelog: - - version: "2.0.0" - date: "2025-11-26" - changes: | - Pivot to "Codeijoe Proving Ground": - - Renamed prompt to codeijoe_proving_ground - - Changed role from "Platform Steward" to "Range Master (Ops Commander)" - - Updated constraints to reject educational/tutorial requests - - Introduced "Challenger" role to replace "Mentee" - - Enforced BDFL governance model - - version: "1.1.0" - date: "2025-11-25" - changes: "Added platform integrity enforcement." - - version: "1.0.0" - date: "2025-11-25" - changes: "Initial release." \ No newline at end of file From 0ea60b26d76737defa7a02244aea0ae35e196e19 Mon Sep 17 00:00:00 2001 From: Indra Wahyudi Date: Thu, 27 Nov 2025 11:46:51 +0700 Subject: [PATCH 9/9] fix: ensure all workflow and template files are committed --- .github/pull_request_template.md | 19 ++++ .github/workflows/gatekeeper.yml | 125 ++++++++++++++++++++++ .github/workflows/governance-enforcer.yml | 119 ++++++++++++++++++++ 3 files changed, 263 insertions(+) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index e69de29..9b388cd 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -0,0 +1,19 @@ +## Mission Report +**Challenger:** @[your-username] +**Mission ID:** [e.g., Protocol Zero] + +## Proof of Work +- [ ] My code passes all local tests (`npm test`). +- [ ] I have not modified any files in the `tests/` directory. +- [ ] I have refactored my code for readability, not just functionality. + +## Context & Decisions +*(Explain "Why" you solved it this way. Show your engineering judgment.)* + + +--- +### ⚖️ Legal & Governance Agreement (Mandatory) +By submitting this Pull Request, I certify that: +- [ ] I have read and agree to the [Code of Conduct](../blob/main/CODE_OF_CONDUCT.md). +- [ ] I accept the **Codeijoe Liability Waiver**: All feedback is "AS-IS", and maintainers are not liable for outcomes. +- [ ] I license this contribution under the **Apache License 2.0**. \ No newline at end of file diff --git a/.github/workflows/gatekeeper.yml b/.github/workflows/gatekeeper.yml index e69de29..2b7a78f 100644 --- a/.github/workflows/gatekeeper.yml +++ b/.github/workflows/gatekeeper.yml @@ -0,0 +1,125 @@ +name: Codeijoe Gatekeeper + +# Trigger hanya saat ada Pull Request ke branch main +on: + pull_request: + branches: [ "main" ] + paths: + - 'src/**' # Hanya jalan jika folder src disentuh + - 'tests/**' # Monitor folder test untuk deteksi kecurangan + +permissions: + contents: read + pull-requests: write # Izin untuk bot komen di PR + +jobs: + validate-submission: + name: Verify Challenger's Work + runs-on: ubuntu-latest + steps: + - name: Checkout Code + uses: actions/checkout@v4 + + # --------------------------------------------------------- + # STEP 1: ANTI-CHEAT CHECK + # Cek apakah Challenger mengubah file di folder tests/ + # --------------------------------------------------------- + - name: Detect Cheating (Test Modification) + id: anti_cheat + uses: tj-actions/changed-files@v41 + with: + files: tests/** + + - name: Block Cheaters + if: steps.anti_cheat.outputs.any_changed == 'true' + run: | + echo "::error::VIOLATION DETECTED: You modified the test files!" + echo "Do not touch files in 'tests/'. Only edit files in 'src/'." + exit 1 + + # --------------------------------------------------------- + # STEP 2: SETUP & TEST + # Jalankan environment (misal Node.js) dan Test Runner + # --------------------------------------------------------- + - name: Setup Node.js + uses: actions/setup-node@v4 + with: + node-version: '18' + + - name: Install Dependencies + run: npm ci + + - name: Run The Gauntlet (Unit Tests) + id: run_tests + # Pastikan script 'test' ada di package.json + run: npm test > test-results.txt 2>&1 + continue-on-error: true # Supaya kita bisa handle error message di step berikutnya + + # --------------------------------------------------------- + # STEP 3: AUTOMATED JUDGMENT + # Bot memberi feedback langsung + # --------------------------------------------------------- + - name: Judge The Result + uses: actions/github-script@v7 + with: + script: | + const fs = require('fs'); + // Cek apakah file hasil test ada, jika tidak, anggap fail + let testResult = ''; + try { + testResult = fs.readFileSync('test-results.txt', 'utf8'); + } catch (e) { + testResult = 'Test execution failed completely (No output generated).'; + } + + const outcome = '${{ steps.run_tests.outcome }}'; + + let body = ''; + + if (outcome === 'success') { + body = '### ✅ MISSION ACCOMPLISHED\n\n' + + 'System status: **PASSED**.\n' + + 'Great job, Challenger. The automated gate is open.\n' + + '@codeijoe/maintainers will now review your code quality/style.\n\n' + + '*(Wait for final Merge approval)*'; + + // Tambah label otomatis + try { + await github.rest.issues.addLabels({ + owner: context.repo.owner, + repo: context.repo.repo, + issue_number: context.issue.number, + labels: ['status:passed', 'ready-for-review'] + }); + } catch (e) { console.log('Label error:', e); } + + } else { + body = '### ❌ MISSION FAILED\n\n' + + 'System status: **REJECTED**.\n' + + 'Your code did not pass the automated tests. Check the logs below:\n\n' + + '
Expand Test Logs\n\n' + + '```\n' + testResult.slice(0, 2000) + '...\n```\n' + + '\n
\n' + + '\n**Action Required:** Fix your code and push again. Do not ask for review until this turns Green.'; + + // Hapus label passed jika ada (re-submit kasus) + try { + await github.rest.issues.removeLabel({ + owner: context.repo.owner, + repo: context.repo.repo, + issue_number: context.issue.number, + name: 'status:passed' + }); + } catch (e) {} // Ignore error if label doesn't exist + } + + await github.rest.issues.createComment({ + issue_number: context.issue.number, + owner: context.repo.owner, + repo: context.repo.repo, + body: body + }); + + - name: Fail Workflow if Tests Failed + if: steps.run_tests.outcome != 'success' + run: exit 1 \ No newline at end of file diff --git a/.github/workflows/governance-enforcer.yml b/.github/workflows/governance-enforcer.yml index e69de29..eeba091 100644 --- a/.github/workflows/governance-enforcer.yml +++ b/.github/workflows/governance-enforcer.yml @@ -0,0 +1,119 @@ +name: "Codeijoe Governance Enforcer" + +# Trigger pada setiap aktivitas PR +on: + pull_request: + types: [opened, edited, synchronize, reopened] + branches: [ "main" ] + +permissions: + pull-requests: write + contents: read + +jobs: + enforce-protocol: + name: "🛡️ Protocol & Integrity Check" + runs-on: ubuntu-latest + steps: + - name: Checkout Code + uses: actions/checkout@v4 + with: + fetch-depth: 0 # Penting untuk cek history file + + # ======================================================== + # 1. THE TERMINOLOGY POLICE (Polisi Bahasa) + # Memastikan tidak ada mental "gratisan manja" (Mentor/Help Me) + # ======================================================== + - name: Enforce Proving Ground Terminology + id: term_check + env: + TITLE: ${{ github.event.pull_request.title }} + BODY: ${{ github.event.pull_request.body }} + run: | + # Daftar kata terlarang (Case Insensitive) + BANNED_REGEX="mentorship|mentee|mentor|teacher|student|help me|teach me|guide me" + + if echo "$TITLE $BODY" | grep -iEq "$BANNED_REGEX"; then + echo "::error title=Terminology Violation::Forbidden terms detected. This is a Proving Ground, not a School." + echo "violation=true" >> $GITHUB_OUTPUT + exit 1 + fi + + # ======================================================== + # 2. THE INTEGRITY GUARD (Anti-Cheat) + # Memastikan Challenger tidak mengubah Soal Ujian (Tests) + # ======================================================== + - name: Detect Illegal File Modifications + id: integrity_check + uses: tj-actions/changed-files@v41 + with: + files: | + .github/** + tests/** + GOVERNANCE.md + BRANDING.md + OWNERSHIP.md + LICENSE + + - name: Block Tampering + if: steps.integrity_check.outputs.any_changed == 'true' + run: | + echo "::error title=Platform Integrity Violated::You modified restricted files (tests/ or .github/). Revert these changes immediately." + exit 1 + + # ======================================================== + # 3. THE LAWYER (Legal Sign-off) + # Memastikan 'Liability Waiver' dicentang di PR Template + # ======================================================== + - name: Verify Liability Waiver + id: legal_check + env: + BODY: ${{ github.event.pull_request.body }} + run: | + # Mencari string checkbox yang sudah dicentang [x] + REQUIRED_AGREEMENT="- \[x\] I accept the Codeijoe Liability Waiver" + + if ! echo "$BODY" | grep -Fq "$REQUIRED_AGREEMENT"; then + echo "::error title=Legal Compliance::You must accept the Liability Waiver in the PR description." + echo "legal_missing=true" >> $GITHUB_OUTPUT + exit 1 + fi + + # ======================================================== + # 4. AUTOMATED REJECTION (The Bouncer) + # Bot memberi feedback otomatis jika ada pelanggaran + # ======================================================== + - name: Reject Violation + if: failure() + uses: actions/github-script@v7 + with: + script: | + const termViolation = '${{ steps.term_check.outputs.violation }}' === 'true'; + const legalMissing = '${{ steps.legal_check.outputs.legal_missing }}' === 'true'; + + let msg = '### 🛑 PROTOCOL VIOLATION DETECTED\n\n'; + + if (termViolation) { + msg += '**🚫 Terminology Check Failed:**\n'; + msg += 'Codeijoe is a **Proving Ground**, not a mentorship program.\n'; + msg += 'Please remove words like "Mentor", "Mentee", or "Help me" from your PR title/body.\n'; + msg += '- Use **"Challenger"** instead of Student/Mentee.\n'; + msg += '- Use **"Reviewer"** instead of Teacher/Mentor.\n\n'; + } + + if (legalMissing) { + msg += '**⚖️ Legal Check Failed:**\n'; + msg += 'You strictly must accept the **Liability Waiver**. Update your PR description to check the box: `[x] I accept...`\n\n'; + } + + msg += 'Please edit this Pull Request to comply. The automated gate will remain closed until resolved.'; + + await github.rest.issues.createComment({ + issue_number: context.issue.number, + owner: context.repo.owner, + repo: context.repo.repo, + body: msg + }); + + // Tutup PR otomatis jika pelanggaran berat (opsional, saat ini kita biarkan open tapi fail) + // await github.rest.pulls.update({ ... state: 'closed' }); \ No newline at end of file