docs: add deployment guide, community standards, and launch strategy

claude · claude · commit dc142eef97c0 · 2026-04-04T19:40:12.000Z
- Add docs/DEPLOYMENT.md: complete production deployment guide with prerequisites, step-by-step install, database config, nginx reverse proxy, curl test commands, QA acceptance checklist (20 criteria), load testing, security testing, monitoring, and maintenance procedures - Add docs/OPEN_SOURCE_LAUNCH_STRATEGY.md: community activation plan with launch sequence, content calendar, good-first-issues backlog, social media templates, and success metrics - Add SECURITY.md: vulnerability reporting policy - Add CODE_OF_CONDUCT.md: Contributor Covenant v2.1 - Add .github/ISSUE_TEMPLATE/: bug report, feature request, research - Add .github/PULL_REQUEST_TEMPLATE.md - Fix CONTRIBUTING.md: correct clone URL to pixelstrade-dev org - Update README.md: anonymize credits, add contact email https://claude.ai/code/session_01Y7wiMwFa2D4P8zD9RhCgsv
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,35 @@
+---
+name: Bug Report
+about: Report a bug in CAIMS
+title: "[BUG] "
+labels: bug
+assignees: ''
+---
+
+## Description
+A clear description of the bug.
+
+## Steps to Reproduce
+1. Go to '...'
+2. Click on '...'
+3. See error
+
+## Expected Behavior
+What you expected to happen.
+
+## Actual Behavior
+What actually happened.
+
+## Environment
+- OS: [e.g., Ubuntu 22.04]
+- Docker version: [e.g., 24.0.7]
+- Browser: [e.g., Chrome 120]
+- CAIMS version: [e.g., 1.0.0]
+
+## Logs
+```
+Paste relevant logs here
+```
+
+## Screenshots
+If applicable, add screenshots.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,21 @@
+---
+name: Feature Request
+about: Suggest an idea for CAIMS
+title: "[FEATURE] "
+labels: enhancement
+assignees: ''
+---
+
+## Problem
+A clear description of the problem this feature would solve.
+
+## Proposed Solution
+Describe the solution you'd like.
+
+## Alternatives Considered
+Any alternative solutions you've considered.
+
+## Additional Context
+- Does this relate to a specific KPI (CQ, AQ, CFI, EQ, SQ)?
+- Does this affect the scoring engine, debate system, or UI?
+- Any relevant research papers or references?
diff --git a/.github/ISSUE_TEMPLATE/research.md b/.github/ISSUE_TEMPLATE/research.md
@@ -0,0 +1,25 @@
+---
+name: Research Proposal
+about: Propose improvements to scoring methodology or theoretical grounding
+title: "[RESEARCH] "
+labels: research
+assignees: ''
+---
+
+## Area
+Which KPI or methodology does this concern?
+
+## Current Approach
+Brief description of the current implementation.
+
+## Proposed Improvement
+What change do you propose?
+
+## Scientific Basis
+- References to peer-reviewed publications
+- Distinguish between: established fact / hypothesis / speculation
+
+## Impact Assessment
+- Which scores would be affected?
+- Backward compatibility implications?
+- Validation approach?
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,28 @@
+## Summary
+Brief description of the changes.
+
+## Motivation
+Why is this change needed?
+
+## Changes
+- [ ] Change 1
+- [ ] Change 2
+
+## Type
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Refactoring
+- [ ] Documentation
+- [ ] Research / methodology update
+
+## Testing
+- [ ] Unit tests added/updated
+- [ ] Manual testing performed
+- [ ] All existing tests pass (`npm test`)
+- [ ] Build succeeds (`npm run build`)
+
+## Checklist
+- [ ] Code follows project conventions
+- [ ] Self-review completed
+- [ ] Documentation updated if needed
+- [ ] No breaking changes (or documented)
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,41 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community 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, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of 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 towards other community members
+
+Examples of 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
+
+Community leaders 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 community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to: **conduct@pixels-trade.com**
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+## 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
@@ -37,7 +37,7 @@ Propose refinements to the scoring rubrics, weight distributions, or theoretical
 1. Clone the repository and navigate to the project root:
 
 ```bash
-git clone https://github.com/anthropics/CAIMS-Consciousness-Alignment-Intelligence-Measurement-System.git
+git clone https://github.com/pixelstrade-dev/CAIMS-Consciousness-Alignment-Intelligence-Measurement-System.git
 cd CAIMS-Consciousness-Alignment-Intelligence-Measurement-System
 ```
 
diff --git a/README.md b/README.md
@@ -231,4 +231,6 @@ See [LICENSE](LICENSE) for the full text.
 
 ## Credits
 
-Built by Skander / [Pixels Trade SA](https://pixels-trade.com).
+Developed and maintained by [Pixels Trade SA](https://pixels-trade.com).
+
+For questions, partnerships, or support: **contact@pixels-trade.com**
diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,45 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+|---------|--------------------|
+| 1.x     | Yes                |
+| < 1.0   | No                 |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in CAIMS, please report it responsibly.
+
+**Do NOT open a public GitHub issue for security vulnerabilities.**
+
+Instead, send an email to: **security@pixels-trade.com**
+
+Include:
+- Description of the vulnerability
+- Steps to reproduce
+- Potential impact
+- Suggested fix (if any)
+
+We will acknowledge receipt within 48 hours and provide a detailed response within 5 business days.
+
+## Scope
+
+The following are in scope:
+- API endpoints (`/api/*`)
+- Authentication and authorization logic
+- Input validation and sanitization
+- Database query injection
+- Rate limiting bypass
+- Prompt injection in scoring engine
+
+## Disclosure Policy
+
+We follow coordinated disclosure. We ask that you:
+- Allow us reasonable time to fix the issue before public disclosure
+- Do not access or modify other users' data
+- Do not perform denial-of-service attacks
+
+## Recognition
+
+We maintain a security acknowledgments section for responsible disclosures (with your permission).
diff --git a/docs/DEPLOYMENT.md b/docs/DEPLOYMENT.md
diff --git a/docs/OPEN_SOURCE_LAUNCH_STRATEGY.md b/docs/OPEN_SOURCE_LAUNCH_STRATEGY.md
