Skip to content

Commit f8bde3c

Browse files
pixelstrade-devpixelstrade-dev
authored
Merge pull request #2 from pixelstrade-dev/claude/caims-consciousness-framework-2EOiI
docs: add deployment guide, community standards, and launch strategy
2 parents d7ac60e + dc142ee commit f8bde3c

File tree

10 files changed

+1151
-2
lines changed

10 files changed

+1151
-2
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
name: Bug Report
3+
about: Report a bug in CAIMS
4+
title: "[BUG] "
5+
labels: bug
6+
assignees: ''
7+
---
8+
9+
## Description
10+
A clear description of the bug.
11+
12+
## Steps to Reproduce
13+
1. Go to '...'
14+
2. Click on '...'
15+
3. See error
16+
17+
## Expected Behavior
18+
What you expected to happen.
19+
20+
## Actual Behavior
21+
What actually happened.
22+
23+
## Environment
24+
- OS: [e.g., Ubuntu 22.04]
25+
- Docker version: [e.g., 24.0.7]
26+
- Browser: [e.g., Chrome 120]
27+
- CAIMS version: [e.g., 1.0.0]
28+
29+
## Logs
30+
```
31+
Paste relevant logs here
32+
```
33+
34+
## Screenshots
35+
If applicable, add screenshots.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for CAIMS
4+
title: "[FEATURE] "
5+
labels: enhancement
6+
assignees: ''
7+
---
8+
9+
## Problem
10+
A clear description of the problem this feature would solve.
11+
12+
## Proposed Solution
13+
Describe the solution you'd like.
14+
15+
## Alternatives Considered
16+
Any alternative solutions you've considered.
17+
18+
## Additional Context
19+
- Does this relate to a specific KPI (CQ, AQ, CFI, EQ, SQ)?
20+
- Does this affect the scoring engine, debate system, or UI?
21+
- Any relevant research papers or references?

‎.github/ISSUE_TEMPLATE/research.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
name: Research Proposal
3+
about: Propose improvements to scoring methodology or theoretical grounding
4+
title: "[RESEARCH] "
5+
labels: research
6+
assignees: ''
7+
---
8+
9+
## Area
10+
Which KPI or methodology does this concern?
11+
12+
## Current Approach
13+
Brief description of the current implementation.
14+
15+
## Proposed Improvement
16+
What change do you propose?
17+
18+
## Scientific Basis
19+
- References to peer-reviewed publications
20+
- Distinguish between: established fact / hypothesis / speculation
21+
22+
## Impact Assessment
23+
- Which scores would be affected?
24+
- Backward compatibility implications?
25+
- Validation approach?

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
## Summary
2+
Brief description of the changes.
3+
4+
## Motivation
5+
Why is this change needed?
6+
7+
## Changes
8+
- [ ] Change 1
9+
- [ ] Change 2
10+
11+
## Type
12+
- [ ] Bug fix
13+
- [ ] New feature
14+
- [ ] Refactoring
15+
- [ ] Documentation
16+
- [ ] Research / methodology update
17+
18+
## Testing
19+
- [ ] Unit tests added/updated
20+
- [ ] Manual testing performed
21+
- [ ] All existing tests pass (`npm test`)
22+
- [ ] Build succeeds (`npm run build`)
23+
24+
## Checklist
25+
- [ ] Code follows project conventions
26+
- [ ] Self-review completed
27+
- [ ] Documentation updated if needed
28+
- [ ] No breaking changes (or documented)

‎CODE_OF_CONDUCT.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to a positive environment:
10+
11+
- Using welcoming and inclusive language
12+
- Being respectful of differing viewpoints and experiences
13+
- Gracefully accepting constructive criticism
14+
- Focusing on what is best for the community
15+
- Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior:
18+
19+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
20+
- Trolling, insulting or derogatory comments, and personal or political attacks
21+
- Public or private harassment
22+
- Publishing others' private information without explicit permission
23+
- Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Enforcement Responsibilities
26+
27+
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.
28+
29+
## Scope
30+
31+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
32+
33+
## Enforcement
34+
35+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to: **conduct@pixels-trade.com**
36+
37+
All complaints will be reviewed and investigated promptly and fairly.
38+
39+
## Attribution
40+
41+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1.

‎CONTRIBUTING.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Propose refinements to the scoring rubrics, weight distributions, or theoretical
3737
1. Clone the repository and navigate to the project root:
3838

3939
```bash
40-
git clone https://github.com/anthropics/CAIMS-Consciousness-Alignment-Intelligence-Measurement-System.git
40+
git clone https://github.com/pixelstrade-dev/CAIMS-Consciousness-Alignment-Intelligence-Measurement-System.git
4141
cd CAIMS-Consciousness-Alignment-Intelligence-Measurement-System
4242
```
4343

‎README.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -231,4 +231,6 @@ See [LICENSE](LICENSE) for the full text.
231231

232232
## Credits
233233

234-
Built by Skander / [Pixels Trade SA](https://pixels-trade.com).
234+
Developed and maintained by [Pixels Trade SA](https://pixels-trade.com).
235+
236+
For questions, partnerships, or support: **contact@pixels-trade.com**

‎SECURITY.md‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
| Version | Supported |
6+
|---------|--------------------|
7+
| 1.x | Yes |
8+
| < 1.0 | No |
9+
10+
## Reporting a Vulnerability
11+
12+
If you discover a security vulnerability in CAIMS, please report it responsibly.
13+
14+
**Do NOT open a public GitHub issue for security vulnerabilities.**
15+
16+
Instead, send an email to: **security@pixels-trade.com**
17+
18+
Include:
19+
- Description of the vulnerability
20+
- Steps to reproduce
21+
- Potential impact
22+
- Suggested fix (if any)
23+
24+
We will acknowledge receipt within 48 hours and provide a detailed response within 5 business days.
25+
26+
## Scope
27+
28+
The following are in scope:
29+
- API endpoints (`/api/*`)
30+
- Authentication and authorization logic
31+
- Input validation and sanitization
32+
- Database query injection
33+
- Rate limiting bypass
34+
- Prompt injection in scoring engine
35+
36+
## Disclosure Policy
37+
38+
We follow coordinated disclosure. We ask that you:
39+
- Allow us reasonable time to fix the issue before public disclosure
40+
- Do not access or modify other users' data
41+
- Do not perform denial-of-service attacks
42+
43+
## Recognition
44+
45+
We maintain a security acknowledgments section for responsible disclosures (with your permission).

0 commit comments

Comments
 (0)