Skip to main content

Exactor Accelerator

PyPI Version License Python Version

🚀 Exactor Accelerator v2.0.10: Bringing Jev's Cognitive Power Directly to the Edge

Exactor Accelerator is the first neuro-symbolic hybrid engine that unifies Unsupervised Learning, Exact Boolean Minimization, and Zero-Data Autonomous Cold-Start Distillation into a single Python library.

Engineered to operate in seamless symbiosis with TypeSafe AI (Jev), Exactor captures the high-level semantic reasoning of Jev's decision engine and compiles it locally into an Exact Boolean Hypercube in Rust. The outcome is a high-performance hybrid infrastructure that executes Jev's cognitive intelligence directly at local micro-latency (0.05 ms), eliminating cloud network latency overhead and slashing token consumption.


💡 What You Gain with This Technology

  1. Sub-Millisecond Edge Latency (0.05 ms): Eliminates the inevitable 500–1,200 ms network transit overhead of cloud AI API round-trips. Critical path decisions are executed in hot memory at hardware speed.
  2. $0.00 Marginal Inference Cost: Routine, repetitive transactions run on the local Fast-Path with zero API calls, delivering up to 100% token cost savings while preserving cloud AI budgets for high-entropy anomalies.
  3. 100% Regulatory Explainability & Determinism: Black-box neural networks and subjective free-form text are replaced with exact mathematical formulas (IF ... AND ... OR ... NOT). Decisions are fully auditable, reproducible, and ready for strict GDPR, HIPAA, SOX, and PCI-DSS compliance.
  4. Instant Zero-Data Cold-Start: No need to spend months collecting or annotating historical datasets. Deploy on Day 1: the system queries Jev for initial events, writes decisions to a concurrent SQLite WAL ledger, and autonomously compiles them into production-ready local boolean hypercubes.
  5. Zero False Negatives on Critical Rules: Hard-anchor non-negotiable security, clinical, or financial constraints (anchor_critical_rules=True) to mathematically prevent false negatives in mission-critical environments.

🎯 The Cloud AI Infrastructure Dilemma (And the Jev + Exactor Synergy)

Until today, mission-critical production architectures faced a painful trade-off:

  • Traditional Machine Learning (XGBoost / Scikit-Learn): Fast at inference time, but completely blind on Day 1 without thousands of labeled historical rows. Moreover, its opaque black-box trees fail strict regulatory audits.
  • Advanced Declarative Reasoning (Jev): Delivers brilliant zero-shot reasoning from day one without prior training data, with class-leading semantic comprehension. However, all cloud-based architectures inevitably incur network latency (API calls) and linear token costs when evaluating millions of continuous requests.

The Strategic Synergy (Jev + Exactor): Rather than forcing a compromise, this alliance delivers the best of both worlds. Jev acts as the strategic intelligence that navigates and calibrates ambiguous, changing scenarios; Exactor acts as its rapid local execution compiler. By logging and distilling live interactions with Jev into a high-concurrency ledger (SQLite in WAL mode), Exactor automates local execution of compiled rules in just 0.05 milliseconds, freeing up bandwidth and safeguarding token budgets.


📊 Production Performance Benchmark

Capability Pure Jev (TypeSafe AI) Traditional ML (XGBoost) Jev + Exactor Accelerator
Zero-Data Cold-Start (Day 1) ✅ Yes (Cloud evaluation) ❌ Impossible (Requires labeled data) ✅ Yes (Immediate symbiosis)
Execution Latency Standard network latency (477–1,200 ms) 1 – 10 ms 0.05 – 0.1 ms (Local edge speed)
Cost per 100M Decisions Continuous token spend Infrastructure compute cost $0.00 on Fast-Path (Smart token savings)
Regulatory Explainability Robust typed schemas Post-hoc approximations (SHAP) 100% Exact Boolean Formulas (GDPR/HIPAA/SOX)

🧠 Three Technological Pillars in a Unified Pipeline

Exactor completely eliminates heavy offline retraining cycles by learning in step with your production decisions:

  • Unsupervised Stream Monitoring: Inspects raw data streams in real time, computing multi-dimensional Shannon entropy and Z-scores to trigger early warnings for concept drift before business operations are affected.
  • Autonomous Cold-Start Distillation: Deploy with zero historical records. The engine partners with Jev's decision engine during initial live transactions, records states in an ultra-fast SQLite WAL ledger, and dynamically generates an optimized local model that faithfully replicates its logical behavior.
  • Drop-in Scikit-Learn API: Native compatibility with the Python data science ecosystem. Call standard .fit(X, y) and .predict(X) backed by a Gray-code hypercube minimizer that guarantees mathematical precision with zero floating-point loss.

⚡ High-Impact Niches of Excellence

  • Real-Time Fraud Prevention: Sub-millisecond local decisions complemented by Jev's adaptive cloud intelligence for complex edge cases.
  • Emergency Medical Triage: Immutable, deterministic audit trails certified and ready for HIPAA compliance.
  • Cybersecurity & SOC Automation: Process 50,000+ events per second (TPS) detecting anomalies and burst velocities at line rate.
  • Total Regulatory Compliance: Every decision is explained by an exact mathematical formula (IF ... AND ... OR ... NOT), eliminating legal liability in automated decisions.

Installation

pip install exactor-accelerator

Configuration

Exactor Accelerator connects to the EXACTOR Core engine for cloud-accelerated boolean minimization. Set your token using any of these methods:

export EXACTOR_CORE_TOKEN="your-token-here"
export JEV_API_KEY="your-jev-key"          # Optional: TypeSafe Jev API
export DEEPSEEK_API_KEY="your-key"          # Optional: LLM explainer

Option 2: .env File

cp .env.example .env
# Edit .env with your tokens

Option 3: Programmatic Configuration

import exactor_accelerator

exactor_accelerator.configure(
    exactor_core_token="your-token-here",
    jev_api_key="your-jev-key",           # Optional
    deepseek_api_key="your-key",          # Optional
)

Option 4: Per-Instance Token

from exactor_accelerator import ExactorAccelerator

engine = ExactorAccelerator(
    exactor_token="your-token-here",
    use_cloud_exactor=True,
)

Note: Without an EXACTOR Core token, the library falls back to the built-in Hypercube Gray-code Reducer engine, which provides the same deterministic boolean minimization locally.


Quick Start (Copy & Run: Unsupervised + Supervised + Cold-Start)

import pandas as pd
from exactor_accelerator import (
    ExactorAccelerator,
    ExactorAcceleratorClassifier,
    get_feature_engine,
    get_regime_detector,
)

# 1. Raw unlabeled stream (or load via pd.read_csv("your_data.csv"))
raw_df = pd.DataFrame({
    "amount": [45.0, 120.5, 950.0, 15.0, 2100.0, 32.0, 1500.0, 80.0, 42.0, 310.0, 1800.0, 55.0],
    "velocity_1h": [1, 2, 8, 1, 15, 1, 12, 2, 1, 3, 14, 1],
    "device_trust": [0.95, 0.88, 0.20, 0.99, 0.10, 0.92, 0.15, 0.85, 0.90, 0.70, 0.08, 0.94],
    "ip_reputation": ["CLEAN", "CLEAN", "SUSPICIOUS", "CLEAN", "MALICIOUS", "CLEAN", "MALICIOUS", "CLEAN", "CLEAN", "SUSPICIOUS", "MALICIOUS", "CLEAN"],
    "country_risk": ["LOW", "LOW", "MEDIUM", "LOW", "HIGH", "LOW", "HIGH", "LOW", "LOW", "MEDIUM", "HIGH", "LOW"],
})

# =====================================================================
# MODE A: UNSUPERVISED (Feature Extraction, Anomaly Z-Scores & Drift)
# =====================================================================
feature_engine = get_feature_engine(domain="fraud")
df_enriched = feature_engine.extract_all(raw_df)

regime_detector = get_regime_detector(domain="fraud")
regime_info = regime_detector.analyze_regime(
    features=df_enriched.iloc[-1].to_dict(),
    history_df=df_enriched,
)
print(f"[Unsupervised] Regime: {regime_info['dominant_regime']} | Gate: {regime_info['actionability_gate']}")

# =====================================================================
# MODE B: SUPERVISED (Exact Boolean Hypercube Minimization + Audit)
# =====================================================================
target = pd.Series([0, 0, 1, 0, 1, 0, 1, 0, 0, 0, 1, 0], name="target")

clf = ExactorAcceleratorClassifier(domain="fraud", fast_path=True)
clf.fit(df_enriched, target)

new_tx = feature_engine.extract_all(pd.DataFrame([{
    "amount": 1850.0,
    "velocity_1h": 14,
    "device_trust": 0.12,
    "ip_reputation": "MALICIOUS",
    "country_risk": "HIGH",
}]))
prediction = clf.predict(new_tx)
explanation = clf.explain(new_tx)

print(f"\n[Supervised] Prediction (is_fraud): {prediction[0]}")
print(f"[Supervised] Exact Boolean Rule: {clf.formula_expr_}")
print(f"[Supervised] Why this decision was made:\n{explanation}")

# =====================================================================
# MODE C: AUTONOMOUS COLD-START (Zero Prior Data -> Live Auto-Distillation)
# =====================================================================
cold_engine = ExactorAccelerator(cold_start=True, auto_evolve_every=5)
live_res = cold_engine.evaluate(new_tx.iloc[0].to_dict(), fast_path=True)
print(f"\n[Cold-Start] Decision: {live_res['decision']} | Route: {live_res['route']}")
print(f"[Cold-Start] Why: {live_res['explicacion_natural']}")

Expected Output

[Unsupervised] Regime: STABLE_PATTERN | Gate: PROCEED

[Supervised] Prediction (is_fraud): 1
[Supervised] Exact Boolean Rule: (~amount_low & ~velocity_1h_high & ~velocity_1h_low & ~device_trust_above_target_median & ~device_trust_low & ~ip_reputation_eq_clean & ip_reputation_eq_suspicious)
[Supervised] Why this decision was made:
1. **What was decided?**
The operation was blocked as a preventive security measure because it was flagged as high risk.

2. **Why?**
- **The device couldn't be trusted:** The device used for this operation had a very low trust score (0.12 out of 1), meaning it didn't look like a device you normally use or one we recognize as safe.
- **The internet connection came from a dangerous source:** The IP address was flagged as malicious, with a very high risk score of 0.95.
- **The activity pattern was unusual:** There were 14 operations in just one hour, which is far more than normal, and the operation came from a high-risk country ($1,850).

3. **What does this mean for you?**
Your operation was not processed, but your account and funds remain safe.

[Cold-Start] Decision: SAFE | Route: JEV_ORACLE
[Cold-Start] Why: Autonomous action [APROBAR_TRANSACCION] executed: Legitimate transaction with confidence (92.0%). Direct pass authorized without friction.

Examples by Domain

Documentation

Roadmap

See ROADMAP_V2.md for details.

Contributing

See CONTRIBUTING.md for details.

License

MIT License - see LICENSE for details.


Architecture & System Design

This architecture integrates the EXACTOR boolean minimization engine (SMLE) with the Jev typed decision model (TypeSafe AI). The system operates under a Live & Incremental Memory paradigm: it starts with optional cold-start historical ingestion and evolves organically with every new query in real time, completely eliminating heavy offline retraining cycles.

       [ PHASE A: INITIAL INGESTION ]
   Historical Files (CSV / JSON / Logs)
                 │
                 ▼
   [ Adaptive Binarization in B^k ]
                 │
                 ▼
   [ EXACTOR Core Engine (Rust/Cloud) ] ──▶ Pure Rules (AND, OR, XOR, NOT)
                 │
                 ▼
   [ Dynamic Exactor ➔ Jev Adapter ]   ──▶ Typed Schema (Noul, Choice, Score)
                 │
                 ▼
       [ PHASE B: REAL-TIME OPERATION ]
   Production Query ──▶ [ Fast-Path Boolean / Jev (0.05-500ms) ]
                                     │
                ┌────────────────────┴────────────────────┐
                ▼                                         ▼
   [ Confidence >= Threshold ]                  [ SQLite WAL Ledger ]
                │                               (Collective Memory)
                ▼                                         │
    [ AUTONOMOUS EXECUTION ]                              ▼
                                                [ Sliding Window ]
                                                          │
                                                          ▼
                                            [ DIFFERENTIAL UPDATE ]
                                                (Hot Evolution)

Operational Workflow

Phase A: Cold-Start & Ingestion

  1. Historical Data Load: Users or administrators supply initial records (CSV, JSON, logs, transactions, or tabular features) via the web interface or REST API.
  2. Adaptive Binarization: The preprocessing engine transforms continuous and categorical variables into discrete propositions ($0$ and $1$) projected onto the boolean hypercube $\mathbb{B}^k$ ($k \le 64$).
  3. Logical Discovery (Exactor Core): The Rust/Cloud engine processes the binarized matrix, distilling an initial set of exact, immutable logical rules (AND, OR, XOR, NOT) with 100% auditability and zero black-box opacity.
  4. Jev Schema Calibration: The discovered rules automatically translate into typed question schemas (Choice, Score, Noul) consumed by the Jev API.

Phase B: Continuous Operation & Live Memory (Zero Retraining)

  1. Real-World Capture: Each new production query, log event, or interaction enters the runtime in raw or semi-structured form.
  2. Ultra-Low Latency Evaluation: Fast-path evaluates the boolean formula in 0.05–0.1 ms ($4,770\times$ speedup); complex or borderline states route to Jev calibrated probability distributions (RLCD - Reinforcement Learning for Calibrated Decisions).
  3. Memory Ledger Tracking: Every interaction is automatically logged into a high-concurrency lightweight database (SQLite in WAL mode), building cumulative system memory.
  4. Differential Updates: Periodically or on-demand, the engine processes recent sliding windows to update logic rules in-place (hot evolution), allowing organic learning from real-world drift without downtime.

Component Architecture

Component 1: Ingestion & Binarization Subsystem (exactor_accelerator.ingestion)

  • Function: Converts continuous and categorical features into clean boolean proposition matrices.
  • Inputs: CSV/JSON datasets (at cold-start) or streaming event payloads (in production).
  • Outputs: Discretized miniterm matrix with hypercube dimension mapping and target column.
  • Key Modules: binarizer.py, loader.py, text_extractor.py.

Component 2: Logic Minimization Engine (exactor_accelerator.core)

  • Function: Executes boolean logic minimization using Gray codes and stack-based hypercube reduction.
  • Key Characteristics: Native boolean hypercube ($\mathbb{B}^k$) operation without floating-point drift, producing auditable rules.
  • Native XOR Support: Detects parity and non-linear algebraic symmetry.
  • Key Modules: hypercube.py, exactor_bridge.py.

Component 3: Dynamic Adapter (exactor_accelerator.adapter)

  • Function: Translates Exactor boolean formulas into typed question schemas for TypeSafe Jev (typesafe-sdk).
  • Payload Structure:
{
  "model": "jev-latest",
  "state": { "event": "Real-time production query data" },
  "questions": {
    "logic_criterion": {
      "type": "noul",
      "instructions": "Is the boolean condition derived from historical analysis satisfied?"
    },
    "recommended_action": {
      "type": "choice",
      "instructions": "Which business action should be executed?",
      "criteria": {
        "AUTONOMOUS_EXECUTION": "High confidence",
        "HUMAN_REVIEW": "Uncertainty / edge case",
        "DISCARD": "Condition not met"
      }
    },
    "criticality_calibration": {
      "type": "score",
      "instructions": "Impact level on a continuous ordinal scale."
    }
  }
}
  • Key Modules: jev_schema.py, translator.py.

Component 4: Decision & Live Memory Layer (exactor_accelerator.ledger & exactor_accelerator.engine)

  • Function: Delivers calibrated probabilistic responses to clients and records interactions for incremental learning.
  • Autonomous Execution: Automatically triggers downstream workflows when confidence exceeds the configured threshold.
  • Concurrent Ledger: SQLite optimized with PRAGMA journal_mode = WAL; and PRAGMA synchronous = NORMAL; for non-blocking concurrent writes.
  • Key Modules: sqlite_wal.py, jev_client.py, runtime.py.

Project Structure

exactor-accelerator/
├── exactor_accelerator/
│   ├── ingestion/             # Component 1: Ingestion & Binarization
│   │   ├── binarizer.py       # Adaptive hypercube discretizer
│   │   ├── loader.py          # CSV/JSON parsers & synthetic loaders
│   │   └── text_extractor.py  # Unstructured text feature extraction
│   ├── core/                  # Component 2: Exactor Logic Engine
│   │   ├── hypercube.py       # Hypercube, Gray code & stack reduction
│   │   └── exactor_bridge.py  # Dispatcher to exactor.tech Cloud / local
│   ├── adapter/               # Component 3: Exactor -> Jev Adapter
│   │   ├── jev_schema.py      # Noul, Choice, and Score primitives
│   │   └── translator.py      # TypeSafe payload generator
│   ├── ledger/                # Component 4A: Live Memory (SQLite WAL)
│   │   └── sqlite_wal.py      # Write-Ahead Logging persistence
│   ├── engine/                # Component 4B: Runtime & Jev Client
│   │   ├── jev_client.py      # TypeSafe API client & RLCD simulator
│   │   └── runtime.py         # HybridRuntime master orchestrator
│   ├── api/                   # FastAPI REST Service
│   │   └── server.py          # OpenAPI endpoints & static UI hosting
│   ├── web/                   # Control Dashboard (Glassmorphic)
│   │   ├── index.html         # Live telemetry & 4-phase dashboard
│   │   ├── styles.css         # Cyber-logic aesthetic
│   │   └── app.js             # Client logic & WAL stream feed
│   └── data/                  # Embedded sample datasets
├── tests/                     # Automated test suite
│   ├── test_binarizer.py
│   ├── test_exactor_hypercube.py
│   ├── test_jev_adapter.py
│   └── test_live_memory.py
├── run_demo.py                # End-to-end interactive CLI demonstration
├── run_server.py              # Web dashboard & REST API server launcher
└── pyproject.toml             # Standard PEP 621 package specification

Usage Instructions

1. Run Automated Test Suite

python -m pytest tests/ -v

2. Run Interactive CLI Demonstration

Demonstrates the complete end-to-end lifecycle in one command:

python run_demo.py

3. Launch Web Server & Control Dashboard

python run_server.py

REST API Endpoints

Method Endpoint Description
GET /api/system/status Engine status, active rule version, and ledger record count
POST /api/ingest/file Phase A: Upload CSV/JSON dataset and trigger logical discovery
POST /api/ingest/sample Phase A: Instantly load sample datasets (fraud / sre / triage)
GET /api/exactor/rules Canonical boolean formulas distilled by Exactor
GET /api/jev/schema Calibrated typed question schema (Noul, Choice, Score)
POST /api/query Phase B: Real-time query evaluation with fast-path and WAL logging
GET /api/ledger Stream audited interaction records from SQLite WAL
POST /api/ledger/feedback Inject human feedback / ground truth for a past query
POST /api/differential/update Trigger differential rule update over a sliding window

Metadata

Release files for exactor-accelerator 2.0.10

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for exactor-accelerator 2.0.10
File Size Uploaded
exactor_accelerator-2.0.10.tar.gz 243.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for exactor-accelerator 2.0.10
File Interpreter ABI Platform
exactor_accelerator-2.0.10-py3-none-any.whl Python 3 none any Details

Total release size: 427.1 kB

Release files / exactor_accelerator-2.0.10.tar.gz

Download URL exactor_accelerator-2.0.10.tar.gz
Size 243.4 kB
Tags Source
SHA-256 checksum
How to use checksums
c9107544e8aaa8b67989d347077238ed6dd96034003bd7b9c18f078cfc4eb4b4
BLAKE2b-256 checksum
How to use checksums
5da12144f54a0075d5a32986b0627b20c9b785c82d9f3798bb0972f02ad8c779
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.0

Release files / exactor_accelerator-2.0.10-py3-none-any.whl

Download URL exactor_accelerator-2.0.10-py3-none-any.whl
Size 183.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
54d1b22f8d8578221ae586e79e79b6a891fb7cb706ba1959b8a0d7cf311c53c5
BLAKE2b-256 checksum
How to use checksums
fda01bc0fadab78fcddeee369f3b1265e6fd3521629104bbc43e11afe107b677
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.0

Release history Release notifications | RSS feed

2.0.11

2 release files

This release

2.0.10 This release

2 release files

2.0.9

2 release files

2.0.8

2 release files

2.0.7

2 release files

2.0.6

2 release files

2.0.5

2 release files

2.0.4

2 release files

2.0.3

2 release files

2.0.1

2 release files

2.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page