crprotocol 2.0.0__tar.gz

crprotocol-2.0.0/.dockerignore

@@ -0,0 +1,36 @@
+# CRP container ignores — keep image small
+__pycache__/
+*.py[cod]
+*.so
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.hypothesis/
+dist/
+build/
+*.egg-info/
+tests/
+docs/
+examples/
+rfcs/
+specification/
+schemas/
+media/
+crp_sessions/
+_long_gen_results/
+_*.py
+_*.txt
+_*.json
+_*.jsonl
+*.tmp
+*.bak
+*.md
+!README.md
+!LICENSE.md
+.git/
+.github/
+.vscode/
+.idea/
+.pre-commit-config.yaml
+Dockerfile
+.dockerignore

crprotocol-2.0.0/.github/CODEOWNERS

@@ -0,0 +1,32 @@
+# CRP Repository Code Owners
+# See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+#
+# These owners are REQUIRED reviewers for all PRs touching their areas.
+# No PR can be merged without approval from the relevant code owner(s).
+
+# ── Global: Everything requires maintainer approval ──
+*                           @Constantinos-uni
+
+# ── Specification: Core protocol documents ──
+/specification/             @Constantinos-uni
+/schemas/                   @Constantinos-uni
+/rfcs/                      @Constantinos-uni
+
+# ── SDK Implementation ──
+/crp/                       @Constantinos-uni
+
+# ── Licensing & Governance ──
+LICENSE.md                  @Constantinos-uni
+GOVERNANCE.md               @Constantinos-uni
+SECURITY.md                 @Constantinos-uni
+CODE_OF_CONDUCT.md          @Constantinos-uni
+CONTRIBUTING.md             @Constantinos-uni
+
+# ── CI/CD & Infrastructure ──
+/.github/                   @Constantinos-uni
+pyproject.toml              @Constantinos-uni
+mkdocs.yml                  @Constantinos-uni
+
+# ── Documentation site ──
+/site-docs/                 @Constantinos-uni
+/docs/                      @Constantinos-uni

crprotocol-2.0.0/.github/FUNDING.yml

@@ -0,0 +1,6 @@
+# Funding links for CRP™ — Context Relay Protocol
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository
+
+github: Constantinos-uni
+custom:
+  - "https://crprotocol.io"

crprotocol-2.0.0/.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,50 @@
+name: Bug Report
+description: Report an issue with the CRP specification or schemas
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      description: Which part of the specification is affected?
+      options:
+        - Core Protocol (02_CORE_PROTOCOL.md)
+        - Context Envelope (03_CONTEXT_ENVELOPE.md)
+        - Token Generation (04_TOKEN_GENERATION_PROTOCOL.md)
+        - System Integration (05_SYSTEM_WIDE_INTEGRATION.md)
+        - Implementation Plan (06_IMPLEMENTATION_PLAN.md)
+        - Security (07_SECURITY.md)
+        - Monetization (08_MONETIZATION.md)
+        - Deployment (09_DEPLOYMENT.md)
+        - JSON Schemas
+        - Examples
+        - README
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear description of the issue
+      placeholder: Describe the bug or inconsistency...
+    validations:
+      required: true
+  - type: textarea
+    id: location
+    attributes:
+      label: Location
+      description: Specific section, line numbers, or schema files affected
+      placeholder: "e.g., §3.8, line 1400 in 02_CORE_PROTOCOL.md"
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What should the specification say?
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Any additional context, references, or related sections

crprotocol-2.0.0/.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,52 @@
+name: Feature Request
+description: Propose a new feature or capability for CRP
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: What problem does this feature solve?
+      placeholder: "I'm trying to ... but CRP doesn't support ..."
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed Solution
+      description: Describe your proposed addition to the specification
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: What other approaches did you consider?
+  - type: dropdown
+    id: breaking
+    attributes:
+      label: Breaking Change?
+      description: Would this require changes to existing Stable APIs?
+      options:
+        - "No — purely additive"
+        - "Yes — changes existing behavior"
+        - "Unsure"
+    validations:
+      required: true
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope
+      description: Which area of the specification is affected?
+      options:
+        - Core Protocol
+        - Extraction Pipeline
+        - CKF / Knowledge Fabric
+        - API / Schemas
+        - Security
+        - Deployment
+        - Observability
+        - Other
+    validations:
+      required: true

crprotocol-2.0.0/.github/ISSUE_TEMPLATE/spec-clarification.yml

@@ -0,0 +1,36 @@
+name: Spec Clarification
+description: Request clarification on a specification section
+title: "[Clarification]: "
+labels: ["clarification"]
+body:
+  - type: textarea
+    id: section
+    attributes:
+      label: Section Reference
+      description: Which section(s) need clarification?
+      placeholder: "e.g., §6.10.2 TaskIntent schema, §3.8 CKF retrieval modes"
+    validations:
+      required: true
+  - type: textarea
+    id: question
+    attributes:
+      label: Question
+      description: What is unclear or ambiguous?
+    validations:
+      required: true
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Suggested Clarification
+      description: If you have a suggestion for how to clarify, include it here
+  - type: dropdown
+    id: impact
+    attributes:
+      label: Impact Level
+      description: How does this ambiguity affect implementation?
+      options:
+        - Blocking — cannot implement without clarification
+        - Significant — multiple valid interpretations possible
+        - Minor — wording improvement, intent is clear
+    validations:
+      required: true

crprotocol-2.0.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+## Description
+
+<!-- Briefly describe what this PR changes and why -->
+
+## Type of Change
+
+- [ ] Typo / wording fix
+- [ ] Specification clarification (no semantic change)
+- [ ] Non-breaking addition (new optional field, new example)
+- [ ] Breaking change (requires RFC)
+- [ ] Schema change
+- [ ] Example addition/update
+- [ ] Documentation (README, CONTRIBUTING, etc.)
+
+## Specification Sections Affected
+
+<!-- List affected sections, e.g., §3.8, §6.10.2, §22 -->
+
+## RFC 2119 Impact
+
+<!-- If this changes any MUST/SHOULD/MAY requirements, list them here -->
+
+- [ ] No RFC 2119 changes
+- [ ] Changes MUST/MUST NOT requirements
+- [ ] Changes SHOULD/SHOULD NOT requirements
+- [ ] Changes MAY requirements
+
+## Checklist
+
+- [ ] I have read the [Contributing Guide](CONTRIBUTING.md)
+- [ ] JSON Schemas validate correctly (if modified)
+- [ ] Cross-references are correct (§ references point to valid sections)
+- [ ] CHANGELOG.md is updated (for user-facing changes)
+- [ ] No broken links in modified documents

crprotocol-2.0.0/.github/workflows/ci.yml

@@ -0,0 +1,46 @@
+# Copyright © 2025 Constantinos Vidiniotis. All rights reserved.
+# Licensed under Elastic License 2.0 — see LICENSE.md for details.
+
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  lint-and-test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: ruff check crp/ tests/
+
+      - name: Type check with mypy
+        run: mypy crp/ --ignore-missing-imports
+
+      - name: Run tests with coverage
+        run: pytest tests/ -v --tb=short --cov=crp --cov-report=term-missing --cov-fail-under=80
+
+      - name: Dependency audit
+        run: pip-audit --strict --desc on
+        continue-on-error: true  # advisory until all deps are pinned

crprotocol-2.0.0/.github/workflows/link-check-config.json

@@ -0,0 +1,8 @@
+{
+  "ignorePatterns": [
+    {
+      "pattern": "^https?://"
+    }
+  ],
+  "aliveStatusCodes": [200, 206, 301, 302, 403]
+}

crprotocol-2.0.0/.github/workflows/link-check.yml

@@ -0,0 +1,19 @@
+name: Check Links
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  link-check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Check internal links
+        uses: gaurav-nelson/github-action-markdown-link-check@v1
+        with:
+          use-quiet-mode: 'yes'
+          config-file: '.github/workflows/link-check-config.json'

crprotocol-2.0.0/.github/workflows/validate-schemas.yml

@@ -0,0 +1,34 @@
+name: Validate JSON Schemas
+
+on:
+  push:
+    branches: [ main ]
+    paths:
+      - 'schemas/**'
+  pull_request:
+    branches: [ main ]
+    paths:
+      - 'schemas/**'
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Install ajv-cli
+        run: npm install -g ajv-cli ajv-formats
+
+      - name: Validate all schemas
+        run: |
+          echo "Validating JSON Schema files..."
+          for schema in schemas/*.json; do
+            echo "  Validating: $schema"
+            ajv compile -s "$schema" --spec=draft2020 -c ajv-formats || exit 1
+          done
+          echo "All schemas valid!"

crprotocol-2.0.0/.gitignore

@@ -0,0 +1,61 @@
+# OS files
+.DS_Store
+Thumbs.db
+desktop.ini
+
+# Editor files
+*.swp
+*.swo
+*~
+.vscode/
+.idea/
+*.sublime-*
+
+# Node modules (for schema validation)
+node_modules/
+
+# Build outputs
+dist/
+build/
+*.egg-info/
+site/
+
+# Python
+__pycache__/
+*.py[cod]
+*.so
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+*.egg
+pip-wheel-metadata/
+
+# Temporary files
+*.tmp
+*.bak
+
+# Runtime session data
+crp_sessions/
+.hypothesis/
+
+# Dev scratch files (root-level only)
+/_*.py
+/_*.txt
+/_*.json
+/_*.jsonl
+/_full_*
+/_long_gen*
+/_live_*
+/_check_*
+/_dep_*
+/_pytest_count*
+/_test_*
+/_tr.*
+/_batch*
+/0.80)
+/_long_gen_results/
+/type_confidence
+/[0-9][0-9][0-9]*
+
+# Numeric test output directories
+/[0-9]*/

crprotocol-2.0.0/.pre-commit-config.yaml

@@ -0,0 +1,31 @@
+# Copyright © 2025 Constantinos Vidiniotis. All rights reserved.
+# Licensed under Elastic License 2.0 — see LICENSE.md for details.
+#
+# Install: pip install pre-commit && pre-commit install
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-json
+      - id: check-added-large-files
+        args: ['--maxkb=500']
+      - id: check-merge-conflict
+      - id: detect-private-key
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.4.4
+    hooks:
+      - id: ruff
+        args: [--fix]
+
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v1.10.0
+    hooks:
+      - id: mypy
+        additional_dependencies: []
+        args: [--ignore-missing-imports]
+        files: ^crp/