splita 0.1.0__tar.gz

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

@@ -0,0 +1,30 @@
+---
+name: Bug Report
+about: Report a bug in splita
+title: "[BUG] "
+labels: bug
+assignees: ""
+---
+
+## Describe the bug
+A clear and concise description of the bug.
+
+## To reproduce
+Steps to reproduce the behaviour:
+
+```python
+# Minimal code example that triggers the bug
+```
+
+## Expected behaviour
+What you expected to happen.
+
+## Actual behaviour
+What actually happened. Include the full traceback if applicable.
+
+## Environment
+- splita version:
+- Python version:
+- OS:
+- NumPy version:
+- SciPy version:

splita-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature Request
+about: Suggest a new feature or improvement
+title: "[FEATURE] "
+labels: enhancement
+assignees: ""
+---
+
+## Problem
+What problem does this feature solve? What use case does it address?
+
+## Proposed solution
+Describe the API or behaviour you'd like to see.
+
+```python
+# Example usage of the proposed feature
+```
+
+## Alternatives considered
+Any alternative solutions or workarounds you've considered.
+
+## References
+Links to papers, blog posts, or other implementations if applicable.

splita-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+## What does this PR do?
+
+## Checklist
+- [ ] Tests pass (`pytest tests/`)
+- [ ] Lint passes (`ruff check src/`)
+- [ ] Docstrings added for new public functions
+- [ ] CHANGELOG.md updated (if user-facing change)

splita-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,28 @@
+name: CI
+on: [push, pull_request]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install ruff
+      - run: ruff check src/
+      - run: ruff format --check src/
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[ml]"
+      - run: pip install pytest pytest-cov
+      - run: pytest tests/ -q --tb=short -x -p no:cacheprovider

splita-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,24 @@
+name: Deploy Docs
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install mkdocs-material
+      - run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          mkdocs gh-deploy --force

splita-0.1.0/.gitignore

@@ -0,0 +1,21 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+dist/
+build/
+.eggs/
+*.egg
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+.venv/
+venv/
+*.so
+.DS_Store
+splita_api_spec.docx
+.internal/
+dist/

splita-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.9.10
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

splita-0.1.0/.python-version

@@ -0,0 +1 @@
+3.10

splita-0.1.0/CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-03-15
+
+### Added
+
+- Core experimentation engine (`Experiment`, `BayesianExperiment`, `QuantileExperiment`).
+- Sequential testing methods (`mSPRT`, `EValue`, `EProcess`, `GroupSequential`, `ConfidenceSequence`, `YEAST`).
+- Variance reduction techniques (`CUPED`, `CUPAC`, `DoubleML`, `PostStratification`, `RegressionAdjustment`).
+- Causal inference suite (`DifferenceInDifferences`, `SyntheticControl`, `CausalForest`, `TMLE`, `DoublyRobustEstimator`).
+- Experiment diagnostics (`AATest`, `SRMCheck`, `FlickerDetector`, `NoveltyCurve`, `PHackingDetector`).
+- Multi-armed bandit algorithms (`ThompsonSampler`, `LinUCB`, `LinTS`).
+- Experiment design helpers (`FractionalFactorialDesign`, `PairwiseDesign`, `BudgetSplitDesign`).
+- Governance layer (`ExperimentRegistry`, `GuardrailMonitor`, `ConflictDetector`).
+- Structured exception hierarchy (`errors.py`).
+- Frozen dataclass result types for all public APIs.
+- Comprehensive validation utilities (`_validation.py`).

splita-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,55 @@
+# 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, 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
+
+Examples of behaviour 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 behaviour:
+
+- 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 behaviour and will take appropriate and fair corrective action in
+response to any behaviour 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 behaviour may be
+reported to the project maintainers. 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.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

splita-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contributing to splita
+
+Thank you for your interest in contributing to splita! This guide will help you get started.
+
+## Development setup
+
+```bash
+# Clone the repo
+git clone https://github.com/Naareman/splita.git
+cd splita
+
+# Create a virtual environment
+python -m venv .venv
+source .venv/bin/activate
+
+# Install in editable mode with dev dependencies
+pip install -e ".[dev,ml]"
+
+# Install pre-commit hooks
+pre-commit install
+```
+
+## Running checks
+
+```bash
+# Lint
+ruff check src/ tests/
+
+# Format
+ruff format src/ tests/
+
+# Type check
+mypy src/splita/
+
+# Tests
+pytest
+
+# Tests with coverage
+pytest --cov=splita --cov-report=term-missing
+```
+
+## Pull request guidelines
+
+1. **Fork and branch.** Create a feature branch from `main` (e.g. `feat/my-feature` or `fix/issue-42`).
+2. **Write tests first.** Every public method needs tests covering the happy path, edge cases, and validation errors.
+3. **Follow existing patterns.** Look at similar classes in the codebase for API conventions.
+4. **Keep PRs focused.** One feature or fix per PR. Small PRs are reviewed faster.
+5. **Write a clear description.** Explain what the PR does and why, not just what files changed.
+
+## Code style
+
+- **Python 3.10+** type hints: use `X | Y`, not `Optional[X]` or `Union[X, Y]`.
+- **NumPy docstrings** (numpydoc format) on all public APIs.
+- **snake_case** everywhere, no exceptions.
+- **Frozen dataclasses** for all result types, with `.to_dict()`.
+- **Keyword-only** config args (after positional data args).
+- **Error messages** follow the 3-part structure: Problem, Detail, Hint.
+
+```python
+raise ValueError(
+    "`alpha` must be in (0, 1), got 1.5.\n"
+    "  Detail: alpha=1.5 means a 150% false positive rate, which is not meaningful.\n"
+    "  Hint: typical values are 0.05, 0.01, or 0.10."
+)
+```
+
+## Test conventions
+
+- Mirror the `src/` structure in `tests/` (e.g. `src/splita/core/` -> `tests/core/`).
+- Test file names: `test_<module>.py`.
+- Use `pytest` fixtures for shared setup.
+- Statistical correctness tests: compare against `scipy.stats` or known analytic solutions.
+- Every `ValueError` / `TypeError` validation path must have a test.
+
+## Dependencies
+
+- **Required:** numpy, scipy. Nothing else.
+- **Optional:** scikit-learn (for CUPAC/ML features only).
+- Do not add new dependencies without discussion in an issue first.

splita-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Nareman
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.