valoricore 0.1.0__tar.gz

valoricore-0.1.0/.dockerignore

@@ -0,0 +1,8 @@
+target/
+node/target/
+.git/
+.venv/
+__pycache__/
+.DS_Store
+*.pyc
+data/

valoricore-0.1.0/.env.example

@@ -0,0 +1,5 @@
+# Valori Environment Configuration
+# Copy this to .env and fill in your values
+
+# Production Koyeb Deployment URL
+VALORI_URL=https://your-deployment.koyeb.app

valoricore-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,31 @@
+---
+name: Bug Report
+about: Report determinism, ingestion, or kernel correctness issues
+title: "[BUG]"
+labels: bug
+---
+
+### Description
+
+Describe the issue and expected behavior.
+
+### Category
+- Determinism divergence
+- Snapshot / WAL behavior
+- Quantization or clamping
+- Cross-architecture mismatch
+
+### Reproduction Steps
+
+### Hardware / Substrate
+
+CPU:
+Architecture:
+OS:
+
+### Input Data Characteristics
+
+Vector dimension:
+Value range:
+
+### Additional Notes

valoricore-0.1.0/.github/ISSUE_TEMPLATE/feature_proposal.md

@@ -0,0 +1,16 @@
+---
+name: Feature Proposal
+about: Suggest kernel-level improvements
+title: "[PROPOSAL]"
+labels: enhancement
+---
+
+### Problem Context
+
+### Proposed Change
+
+### Determinism Impact
+
+### Cross-substrate Considerations
+
+### Why this belongs in kernel (not evaluator)

valoricore-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,27 @@
+## Summary
+
+What does this change do?
+
+## Determinism Impact
+
+- [ ] No determinism impact
+- [ ] Improves determinism
+- [ ] Changes arithmetic behavior
+
+Explain why.
+
+## Cross-Architecture Behavior
+
+Tested on:
+- [ ] x86
+- [ ] ARM / Apple Silicon
+- [ ] Embedded / Jetson
+
+## Tests
+
+Include reproduction / validation cases.
+
+## Notes
+
+If this relates to forensic or evaluator tracks,
+confirm that logic is kernel-appropriate.

valoricore-0.1.0/.github/workflows/multi-arch-determinism.yml

@@ -0,0 +1,191 @@
+name: Multi-Architecture Determinism Validation
+
+on:
+  push:
+    branches: [ main, develop ]
+    paths:
+      - 'src/**'
+      - 'node/**'
+      - 'embedded/**'
+      - 'ffi/**'
+      - 'Cargo.toml'
+      - 'Cargo.lock'
+      - '.github/workflows/**'
+      # Ignore documentation changes
+      - '!**.md'
+      - '!docs/**'
+  pull_request:
+    branches: [ main ]
+    paths:
+      - 'src/**'
+      - 'node/**'
+      - 'embedded/**'
+      - 'ffi/**'
+      - 'Cargo.toml'
+      - 'Cargo.lock'
+  workflow_dispatch:  # Allow manual triggering
+
+jobs:
+  # Test on x86_64 Linux
+  test-x86:
+    name: "Determinism Test (x86_64 Linux)"
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+        
+      - name: Cache cargo
+        uses: actions/cache@v3
+        with:
+          path: |
+            ~/.cargo/bin/
+            ~/.cargo/registry/index/
+            ~/.cargo/registry/cache/
+            ~/.cargo/git/db/
+            target/
+          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
+          
+      - name: Run determinism test
+        run: |
+          cargo test -p valori-node --test multi_arch_determinism --release determinism_x86 -- --nocapture --test-threads=1 > x86_output.txt 2>&1 || true
+          
+      - name: Extract hash
+        run: |
+          grep "HASH:" x86_output.txt | head -1 | cut -d':' -f2 > x86_hash.txt
+          cat x86_hash.txt
+          
+      - name: Upload hash artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: x86-hash
+          path: x86_hash.txt
+
+  # Test on ARM64 macOS
+  test-arm:
+    name: "Determinism Test (ARM64 macOS)"
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+        
+      - name: Cache cargo
+        uses: actions/cache@v3
+        with:
+          path: |
+            ~/.cargo/bin/
+            ~/.cargo/registry/index/
+            ~/.cargo/registry/cache/
+            ~/.cargo/git/db/
+            target/
+          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
+          
+      - name: Run determinism test
+        run: |
+          cargo test -p valori-node --test multi_arch_determinism --release determinism_arm -- --nocapture --test-threads=1 > arm_output.txt 2>&1 || true
+          
+      - name: Extract hash
+        run: |
+          grep "HASH:" arm_output.txt | head -1 | cut -d':' -f2 > arm_hash.txt
+          cat arm_hash.txt
+          
+      - name: Upload hash artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: arm-hash
+          path: arm_hash.txt
+
+  # Test on WASM32
+  test-wasm:
+    name: "Determinism Test (WASM32)"
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Install Rust + WASM target
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: wasm32-unknown-unknown
+          
+      - name: Cache cargo
+        uses: actions/cache@v3
+        with:
+          path: |
+            ~/.cargo/bin/
+            ~/.cargo/registry/index/
+            ~/.cargo/registry/cache/
+            ~/.cargo/git/db/
+            target/
+          key: ${{ runner.os }}-wasm-cargo-${{ hashFiles('**/Cargo.lock') }}
+          
+      - name: Build kernel for WASM
+        run: |
+          cargo build --lib --target wasm32-unknown-unknown --release
+          
+      - name: Install wasmtime
+        run: |
+          curl https://wasmtime.dev/install.sh -sSf | bash
+          echo "$HOME/.wasmtime/bin" >> $GITHUB_PATH
+          
+      - name: Run WASM determinism test
+        run: |
+          cargo test -p valori-node --test multi_arch_determinism --release determinism_wasm -- --nocapture --test-threads=1 > wasm_output.txt 2>&1 || true
+          
+      - name: Extract hash
+        run: |
+          grep "HASH:" wasm_output.txt | head -1 | cut -d':' -f2 > wasm_hash.txt
+          cat wasm_hash.txt
+          
+      - name: Upload hash artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: wasm-hash
+          path: wasm_hash.txt
+
+  # Compare all hashes
+  validate:
+    name: "Validate Determinism Across Architectures"
+    needs: [test-x86, test-arm, test-wasm]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Download x86 hash
+        uses: actions/download-artifact@v4
+        with:
+          name: x86-hash
+          
+      - name: Download ARM hash
+        uses: actions/download-artifact@v4
+        with:
+          name: arm-hash
+          
+      - name: Download WASM hash
+        uses: actions/download-artifact@v4
+        with:
+          name: wasm-hash
+          
+      - name: Compare hashes
+        run: |
+          echo "=== Multi-Architecture Determinism Validation ==="
+          echo ""
+          echo "x86_64 hash: $(cat x86_hash.txt)"
+          echo "ARM64  hash: $(cat arm_hash.txt)"
+          echo "WASM32 hash: $(cat wasm_hash.txt)"
+          echo ""
+          
+          X86_HASH=$(cat x86_hash.txt | tr -d '[:space:]')
+          ARM_HASH=$(cat arm_hash.txt | tr -d '[:space:]')
+          WASM_HASH=$(cat wasm_hash.txt | tr -d '[:space:]')
+          
+          if [ "$X86_HASH" = "$ARM_HASH" ] && [ "$ARM_HASH" = "$WASM_HASH" ]; then
+            echo "✅✅✅ SUCCESS! All hashes match!"
+            echo "🎯 Determinism verified across x86, ARM, and WASM"
+            exit 0
+          else
+            echo "❌ FAILURE: Hashes do not match!"
+            echo "Determinism broken - this should never happen"
+            exit 1
+          fi
+

valoricore-0.1.0/.gitignore

@@ -0,0 +1,65 @@
+# Rust
+target/
+target_tmp/
+**/*.rs.bk
+debug/
+release/
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# FFI / Native
+*.dll
+*.dylib
+*.pyd
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# IDEs
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+.agent/
+*.log
+*.log
+demo_db/
+
+# Ignore Data
+data/
+*.fvecs
+*.ivecs
+*.tar.gz
+*.db

valoricore-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Valori Project Code of Conduct
+
+The Valori Kernel is a research–grade deterministic computation project. 
+Our work touches systems reliability, reproducibility, and substrate–level
+computing research. We welcome discussion, critique, and contributions — but
+expect interaction to remain respectful and technically grounded.
+
+## Expected Behavior
+
+Participants are expected to:
+
+- Engage constructively and in good faith
+- Critique ideas, not individuals
+- Focus on technical accuracy and clarity
+- Respect research rigor and empirical evidence
+
+## Unacceptable Behavior
+
+Examples include:
+
+- Personal attacks or harassment
+- Misrepresentation of technical claims
+- Intellectual dishonesty
+- Attempts to appropriate or reframe authorship of work
+
+## Research Integrity
+
+Valori maintains strict boundaries between:
+
+- Open–source kernel research and
+- Commercial / enterprise extensions
+
+Contributors must respect these licensing and scope boundaries.
+
+## Reporting Issues
+
+If you believe behavior or activity violates this policy, contact the
+maintainer privately through the repository issue tracker or project email.
+
+The maintainers reserve the right to remove contributions that threaten the
+integrity, safety, or research accuracy of the project.
+
+Thank you for helping maintain a collaborative research environment.

valoricore-0.1.0/COMMERCIAL_LICENSE.md

@@ -0,0 +1,27 @@
+# Valori Commercial Licensing
+
+Valori is open-source software licensed under the **GNU Affero General Public License v3.0 (AGPLv3)**. 
+
+## What does this mean?
+
+### For Open Source & Personal Use (Free)
+You can use Valori Kernel for free if:
+*   You are building an open-source application (licensed under AGPLv3 compatible terms).
+*   You are using it for personal, non-commercial projects.
+*   You are using it internally within your organization **without** exposing it as a service to external users.
+
+### For Commercial Use (Paid License Required)
+You **must** purchase a Commercial License if:
+*   You want to embed Valori Kernel into a proprietary (closed-source) software product or device.
+*   You want to host Valori as a SaaS (Software-as-a-Service) offering to external customers without releasing your own source code.
+*   You simply prefer not to be bound by the copyleft terms of the AGPLv3.
+
+## Commercial License Benefits
+*   **Proprietary Usage**: Embed Valori in your closed-source product without sharing your code.
+*   **Indemnification**: Legal protection and warranty not provided by the open-source license.
+*   **Support**: Direct access to the core engineering team for priority issue resolution.
+*   **Long-Term Support (LTS)**: Access to stable, supported versions for enterprise deployment.
+
+## Contact
+To acquire a commercial license, please contact:
+**varshith.gudur17@gmail.com**

valoricore-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to the Valori Kernel
+
+Thanks for your interest in contributing.
+
+Valori is a deterministic computation kernel designed to eliminate
+substrate-driven divergence across architectures (x86 / ARM / GPU / embedded).
+The project prioritizes mathematical correctness, reproducibility, and
+cross-platform determinism over performance shortcuts.
+
+## Contribution Philosophy
+
+Contributions should:
+
+- Improve determinism, reproducibility, or verification
+- Strengthen fixed-point arithmetic correctness
+- Improve cross-substrate consistency guarantees
+- Add test coverage or validation proofs
+
+Contributions that optimize performance at the cost of determinism will
+not be accepted.
+
+## PR Requirements
+
+Pull requests must include:
+
+- Description of the change
+- Explanation of determinism impact
+- Reproducible test case
+- Cross-architecture notes (where applicable)
+
+## What is Out of Scope
+
+The following belong in private / enterprise tracks:
+
+- forensic analysis pipelines
+- incident replay engines
+- audit and compliance evaluators
+- production ingestion tooling
+
+These systems depend on the kernel but are not part of the open core.
+
+## Development Workflow
+
+1. Open an Issue describing the proposal
+2. Discuss approach and determinism implications
+3. Submit PR after agreement on direction
+
+Thank you for helping strengthen deterministic computing research.