Signal, decomposed.
Into evidence.
VOLYAR Scanner is a live, production sports betting line-movement scanner — it detects meaningful market movement and classifies it into structured signals for a human operator. It is the operational core VOLYAR X is built around.
- LiveProduction scanner, active today
- 5 stagesContext → Evidence → Safety → Explanation → Engine
- Advisory onlyNo autonomous execution
The pipeline, exposed.
A fixed, documented sequence that assembles one inspectable, advisory decision record — implemented in code, but not yet wired into the live scan loop.
1. Context
Assembles the evidence and correlated inputs a decision will be based on.
2. Evidence
Assesses confidence, quality, risk, and uncertainty from that context.
3. Safety
Applies gate checks and determines readiness and any blockers.
4. Explanation
Builds a human-readable account of the reasoning and evidence involved.
5. Engine
Mechanically assembles the prior stages' outputs into one final, inspectable decision record.
Architecture, specified.
Every layer below is documented as implemented or planned — nothing here is aspirational marketing copy.
Scanner Core
ImplementedProvider abstraction & normalization — incoming data converts to canonical internal types before it reaches signal logic; no provider-specific handling exists past that boundary.
Intelligence & Analytics
ImplementedIsolated, read-only audit layer — market memory, historical baselines, and execution/CLV intelligence. Reads runtime data, never writes to it.
TESKA Foundation
ImplementedIsolated, unwired modules — governance & safety evaluation, reasoning & deliberation, decision provenance, and post-decision review.
Replay & Validation
ImplementedA deterministic offline harness that replays the real scanner decision code against historical or synthetic data, producing an inspectable record.
VOLYAR OS
PlannedThe documented future direction the platform is intended to grow into — a domain-general decision operating system. Does not exist as software today.
Built for a human in the loop.
Every interface is documented as advisory — a person reviews and decides, nothing executes on its own.
Desktop UI
The primary PySide6 desktop application operators use to run and monitor the live scanner.
Remote Panel
A remote operator interface for monitoring and control away from the primary desktop.
Replay & Validation
Deterministic offline replay of real scanner decision code, producing an inspectable record for review.
Implemented. Not yet live.
A strict separation, as documented in the project's own status records — nothing below is blended between the two columns.
Implemented
- VOLYAR Scanner — live, in active production use
- Desktop UI and Remote Panel operator interfaces
- Provider-abstraction and normalization layer
- Isolated analytics & intelligence audit layer
- Advisory Decision Core pipeline (not wired into runtime)
- TESKA foundation modules (isolated, unwired)
- Deterministic replay & validation harness
Documented / Planned Direction
- VOLYAR OS — future domain-general decision operating system
- TESKA as a fully wired, coordinating intelligence layer
- Runtime integration of the Decision Core pipeline
- Deeper AI autonomy — explicitly frozen pending Founder approval
Want the full architecture, layer by layer?
Every documented layer, connector, and current-vs-planned boundary lives on the Technology page.