OBrain Sovereign v1.0 - Production Core

The v1.0 release marks the official transition of the OBrain Sovereign ecosystem from research-grade Alpha to an industrial, production-ready B2B arbitrage engine.

🚨 Major Shift: Non-SaaS Model

Starting with v1.0, OBrain has completely decoupled from the SaaS subscription model. The engine is now exclusively delivered as a Sovereign Infrastructure Implementation.

• No Subscriptions: Eliminated recurring monthly plans.
• Private Nodes: Transitioned to local, dedicated hardware processing.
• Total Ownership: Institutional operators now own 100% of the data and compute cycle.

This release unifies the dual-track architecture (Local M4 Engine + Cloudflare Edge) and standardizes the Zero Trust security boundaries.

Key Milestones Achieved

1. Hybrid Topology & Zero Trust Tunneling

The architectural split is now fully crystallized:

• M4 Acceleration Engine: All ML inferences, mathematical divergence (EMA/SMA), and heavy VLM Playwright scraping execute 100% locally with zero cloud compute cost.
• V8 Edge Worker: The Cloudflare Global Network absorbs all POST /v1/ingest requests, serving as the idempotent D1 database orchestrator.
• HMAC-SHA256 Handshake: The tunnel between local and edge is strictly verified via deterministic JSON payload cryptography.

2. Multi-Layer Sourcing (The Waterfall)

The Sourcing pipeline is now resilient against API outages and HTML layout obfuscation:

• Primary: CJ Dropshipping API
• Secondary: AliExpress DOM Scraper
• Tertiary (Alpha): 1688 Factory Explorer via Llama-3.2 Vision.

3. Gap of Anticipation Parametrization

The system actively isolates the Velocity of Demand:

• Formula parameterized: v > 0
• Acceleration Trigger: EMA 7 / SMA 90 > 1.2
• Brazilian Tax Multipliers established (B2C 1.44x vs B2B 1.85x).

4. Continuous Notification

Telegram alerting is now an asynchronous background trigger on the Edge Worker, emitting a CRITICAL_ACCELERATION signal immediately upon finding a product where ROI exceeds 20%.

Upgrading

All package.json modules across the monorepo (docs-portal, backend-worker, frontend) have been locked to 1.0.0. The repository now holds a "fail-closed" security posture where .env and .dev.vars are strictly .gitignored.

Deus ex machina.