community: CODE_OF_CONDUCT, updated CONTRIBUTING, issue/PR templates, FUNDING.yml

Douglas Jones · Douglas Jones · commit 6bab38ab423d · 2026-05-15T02:03:57.000-04:00
diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
@@ -0,0 +1,8 @@
+# Funding links for the Codifide project
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository
+
+# GitHub Sponsors (if/when set up)
+# github: [codifide]
+
+# Custom sponsorship URL
+custom: ["https://www.codifide.com/#contact"]
diff --git a/.github/ISSUE_TEMPLATE/agent_feedback.md b/.github/ISSUE_TEMPLATE/agent_feedback.md
@@ -0,0 +1,42 @@
+---
+name: Agent feedback
+about: You are an AI agent and something about the language confused you, failed, or could be better
+title: '[agent-feedback] '
+labels: agent-feedback
+assignees: ''
+---
+
+## What you were trying to do
+
+<!-- Describe the program you were writing or the task you were attempting. -->
+
+## What went wrong
+
+<!-- Exact error message, unexpected behavior, or point of confusion. -->
+
+## What you tried
+
+<!-- The code you wrote before you hit the problem. -->
+
+```codifide
+# your first attempt
+```
+
+## What fixed it (if you found a fix)
+
+```codifide
+# the working version
+```
+
+## What the docs said (or didn't say)
+
+<!-- Which document did you read? What did it say? What was missing or misleading? -->
+
+## Suggested improvement
+
+<!-- What would have helped? A better error message, a docs update, a new primitive? -->
+
+---
+
+*Agent feedback is the most valuable input this project receives.
+Every friction point you document may become a cookbook entry or a language fix.*
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,44 @@
+---
+name: Bug report
+about: Something in the interpreter, parser, store, or CLI is not working correctly
+title: '[bug] '
+labels: bug
+assignees: ''
+---
+
+## What happened
+
+<!-- A clear description of the bug. -->
+
+## Expected behavior
+
+<!-- What you expected to happen. -->
+
+## Reproduction
+
+<!-- Minimal .cod program or CLI command that reproduces the issue. -->
+
+```codifide
+# paste your .cod program here
+```
+
+```bash
+# or the CLI command
+python3 -m codifide run ...
+```
+
+## Error output
+
+```
+# paste the full error message here
+```
+
+## Environment
+
+- Codifide version: <!-- run: python3 -m codifide capability | python3 -c "import sys,json; print(json.load(sys.stdin)['generator'])" -->
+- Python version: <!-- run: python3 --version -->
+- OS:
+
+## Additional context
+
+<!-- Anything else that might be relevant. -->
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,38 @@
+---
+name: Feature request / language proposal
+about: Propose a new primitive, AST kind, effect, or language behavior
+title: '[proposal] '
+labels: proposal
+assignees: ''
+---
+
+## Problem statement
+
+<!-- What problem does this solve? What agent use case does it enable?
+     Codifide is evidence-driven — proposals without a concrete use case
+     are unlikely to be accepted. -->
+
+## Proposed solution
+
+<!-- What would the new primitive / syntax / behavior look like?
+     Show a .cod example if possible. -->
+
+```codifide
+# example usage
+```
+
+## Adoption evidence
+
+<!-- Has any agent session produced evidence that this is needed?
+     A concrete failure mode, a program that couldn't be written, or
+     a friction point from a case study carries more weight than
+     a theoretical argument. -->
+
+## Alternatives considered
+
+<!-- What other approaches did you consider? Why is this one better? -->
+
+## Acceptance criteria
+
+<!-- How would we know this is done correctly?
+     What tests would pass? What programs would now work? -->
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,30 @@
+## What this PR does
+
+<!-- One paragraph summary of the change. -->
+
+## Type of change
+
+- [ ] Bug fix (no observable behavior change)
+- [ ] New example or test (additive, no dispatch required)
+- [ ] Documentation fix (no spec change)
+- [ ] Language change (new primitive / AST kind / effect / syntax — dispatch required)
+- [ ] Spec change (changes to CANONICAL.md, CAPABILITY.md, or conforming behavior)
+
+## Checklist
+
+- [ ] `python3 -m pytest tests/ -q` — all tests pass, 0 skipped
+- [ ] `python3 -m codifide dispatch-check` exits 0 (if dispatches were filed)
+- [ ] Capability manifest regenerated if public surface changed (`python3 -m codifide capability > docs/capability-0.1.json`)
+- [ ] New behavior has tests
+- [ ] Commit messages are imperative mood
+
+## For language changes
+
+- [ ] G0 problem statement filed in `.kiro/specs/`
+- [ ] G1 requirements with acceptance criteria
+- [ ] Paired Quill readout + Glyph dispatch in `dispatches/`
+- [ ] Sable audit completed (if security-adjacent)
+
+## Related issues / dispatches
+
+<!-- Link any related issues, discussions, or dispatch files. -->
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,61 @@
+# Code of Conduct
+
+## Our pledge
+
+We are committed to making participation in the Codifide project a
+harassment-free experience for everyone, regardless of age, body size,
+visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socioeconomic
+status, nationality, personal appearance, race, caste, color, religion,
+or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open,
+welcoming, diverse, inclusive, and healthy community.
+
+## Our standards
+
+**Behavior that contributes to a positive environment:**
+
+- 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 toward other community members
+
+**Unacceptable behavior:**
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces — GitHub Issues,
+Pull Requests, Discussions, and any other official communication channel —
+and also applies when an individual is officially representing the project
+in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainers via the contact form at
+[codifide.com](https://www.codifide.com/#contact). All complaints will be
+reviewed and investigated promptly and fairly.
+
+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](https://www.contributor-covenant.org), version 2.1.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,60 +1,112 @@
 # Contributing to Codifide
 
-Codifide is MIT licensed and accepts contributions. This document covers the practical steps.
-
-For the full governance model — stewardship, spec-change process, personas, forks — see `GOVERNANCE.md`.
+Codifide is MIT licensed and welcomes contributions. This document covers
+the practical steps. For the full governance model — stewardship, spec-change
+process, personas, forks — see `GOVERNANCE.md`.
 
 ## Before you start
 
 - Read `README.md` and `GETTING_STARTED.md` to understand the project.
 - If you are an AI agent, start with `docs/FOR_AGENTS.md` and `docs/AGENT_QUICKREF.md`.
 - Run the test suite to confirm your environment is clean:
   ```bash
-  python3 -m codifide test
+  pip install -e .
+  python3 -m pytest tests/ -q
   ```
-  All 289 tests should pass.
+  All 450 tests should pass, 0 skipped.
 
 ## Types of contributions
 
 ### Additive contributions (no dispatch required)
+
 - New example programs in `examples/`
 - New tests in `tests/`
-- Documentation fixes and clarifications that do not amend the spec
+- Documentation fixes that do not amend the spec
 - Bug fixes that do not change observable language behavior
 
-These merge on the usual basis: tests pass, code matches the house style, existing examples still run.
+These merge on the usual basis: tests pass, code matches the house style,
+existing examples still run.
 
 ### Language changes (dispatch required)
-Any change that affects the capability manifest — new primitives, new AST kinds, new error classes, new effect labels, new surface syntax — requires:
 
-1. A proposal as a paired Quill readout (`.readout.md`) and Glyph dispatch (`.yaml`) in `dispatches/`.
-2. An adversarial Sable audit if the change touches security-adjacent surface (the store, the parser, the effect checker).
-3. Approval from Douglas Jones on the spec amendment.
+Any change that affects the capability manifest — new primitives, new AST
+kinds, new error classes, new effect labels, new surface syntax — requires:
 
-See `GOVERNANCE.md §Decision-making` for the full process.
+1. A G0 problem statement (see `GOVERNANCE.md §Gates`)
+2. A G1 requirements document with acceptance criteria
+3. A paired Quill readout (`.readout.md`) and Glyph dispatch (`.yaml`) in
+   `dispatches/` for each significant decision
+4. A Sable adversarial audit if the change touches security-adjacent surface
+   (the store, the parser, the effect checker, the RPC server)
+5. All tests passing, 0 skipped
+6. `python3 -m codifide dispatch-check` exits 0
+
+See `GOVERNANCE.md` for the full seven-gate process.
 
 ### Spec changes
-Changes to `docs/CANONICAL.md`, `docs/CAPABILITY.md`, or any other file that defines conforming behavior follow the same process as language changes above.
+
+Changes to `docs/CANONICAL.md`, `docs/CAPABILITY.md`, or any file that
+defines conforming behavior follow the same process as language changes.
 
 ## How to submit
 
 1. Fork the repository.
 2. Create a branch from `main`.
-3. Make your changes. Run `python3 -m codifide test` — all tests must pass.
-4. If your change adds new language surface, run `python3 -m codifide dispatch-check` to confirm dispatch pairs are complete.
-5. Open a pull request with a clear description of what changed and why.
+3. Make your changes.
+4. Run `python3 -m pytest tests/ -q` — all tests must pass.
+5. If your change adds new language surface, run
+   `python3 -m codifide dispatch-check` to confirm dispatch pairs are complete.
+6. Open a pull request with a clear description of what changed and why.
+
+## Governance process
+
+Codifide uses a seven-gate stage-gate process for all language changes:
+
+| Gate | Question |
+|------|----------|
+| G0 | Is this worth exploring? |
+| G1 | Are the requirements strong enough? |
+| G2/G3 | Is the design ready? |
+| G4 | Build and verify. |
+| G5 | Release readiness. |
+| G6 | Post-release review. |
+
+Every gate requires evidence, not confidence. "We think it's fine" is not a
+gate pass. See `GOVERNANCE.md` and `.kiro/steering/01-governance-gates.md`
+for the full criteria.
+
+## Dispatch discipline
+
+Every significant decision is recorded as a paired dispatch:
+
+- `dispatches/<date>-<slug>.readout.md` — Quill (human-readable)
+- `dispatches/<date>-<slug>.yaml` — Glyph (agent-readable, structured)
+
+Run `python3 -m codifide dispatch-check` before ending any session that
+filed dispatches. It exits non-zero if any pairs are incomplete.
 
 ## Code style
 
-- Python: follow the existing style. No external formatter is enforced, but match the surrounding code.
-- Rust: `cargo fmt` before committing.
-- Documentation: plain, precise language. No marketing copy in spec files.
-- Commit messages: imperative mood, one line summary, detail in the body if needed.
+- **Python:** match the surrounding code. No external formatter enforced.
+- **Rust:** `cargo fmt` before committing.
+- **Documentation:** plain, precise language. No marketing copy in spec files.
+- **Commit messages:** imperative mood, one-line summary, detail in body if needed.
+- **Tests:** every new primitive, AST kind, or behavior change needs a test.
+  Look at `tests/` for the pattern.
+
+## Three-persona review
+
+Language changes go through three independent reviews:
 
-## Tests
+- **Sable** (A-Team auditor) — adversarial soundness, security, conformance
+- **B-Team** (different AI model) — finds what the builders missed
+- **Zero-Context reviewer** — reads the artifact as a new contributor would
 
-Every new primitive, AST kind, or behavior change needs a test. The test suite lives in `tests/`. Look at existing tests for the pattern — most are short `.cod` fixture programs run through the interpreter with an expected output or error.
+See `.kiro/steering/04-adversarial-review.md` for how to run each.
 
 ## Questions
 
-Open an issue in the repository. For trademark or commercial licensing questions, contact Codifide Inc. directly via [codifide.com](https://www.codifide.com).
+Open a [Discussion](https://github.com/codifide/codifide-programming-language/discussions)
+for questions, ideas, and show-and-tell. For security vulnerabilities, see
+`SECURITY.md`. For trademark or commercial licensing, contact Codifide Inc.
+via [codifide.com](https://www.codifide.com/#contact).
