Project Prioritization Board

Maturity Legend

Labels reflect available evidence only.

Live / running Active build Design / planned Blocked Needs confirmation Platform layer

Hierarchy And Data Flow

Solid lines are evidence-backed; dashed lines need owner confirmation.

Infrastructure / Data Backbone

QuantDB / DCC Unified data hub. Schemas: raw, data, signals, portfolio, app, dcc, agentx.

Unified Data API REST/MCP distribution layer used by product apps and agents.

GPU Quant Sub-Agent Planned compute layer for heavy backtests and ML research; blocked on GPU capacity.

Signal / Strategy Services

Signal Centre Admin/decision surface at signalcentre.quantclaw.org; documented as #1 DCC consumer.

VIPSignals Client, admin, engine, and paper-trade monitor; produces and distributes signal recommendations.

Strategy Builder Vibe-to-Python flow: prompt -> strategy spec/code -> validation/backtest -> publish candidate.

User-Facing Products / Workflows

TerminalX Trading terminal and market/data workbench consuming QuantDB/DCC data.

AgentX PI agent platform. Uses QuantDB-backed factor snapshots and eToro as execution/portfolio source of truth.

SmartPortfolio Portfolio creation/review using QuantDB factor rankings and portfolio schemas.

Portfolio Rebalancer Optimizer/rebalance workflow downstream of portfolios and holdings.

PI Central Popular Investor operating dashboard; exact product boundary needs owner confirmation.

Schema Evidence

QuantDB API documents raw/data/signals/portfolio/app/dcc/agentx as the core schemas. Relationship details are metadata-only; no row data is published.

App Evidence

PM2 shows quantdb-api, vipsignals-admin, vipsignals-engine, vipsignals-client, AgentX, SmartPortfolio, SP Review, and Rebalancer online.

Open Question

Signal Centre is confirmed as a DCC consumer and live admin surface; confirm whether it is a separate product or the admin layer of VIPSignals.

Focused Projects

Current state, completed work, future work, and maturity.

TerminalX

Original #2 - trading terminal

Needs confirmation

What Was Done

Defined as the Bloomberg-style trading terminal and market/data workbench. Workspace contains TerminalX-related modules and terminalx-pods.

Overall State

Strategic product direction is clear, but current product maturity and latest shipped surface need owner confirmation.

Future Development

Clarify MVP scope: terminal shell, market overview, strategy views, alerts, data explorer, and integration with QuantDB/AgentX.

Owner confirmation needed

Evidence confidence: medium. Product maturity not confirmed.

AgentX

Original #3 - PI agent platform

Live / running

What Was Done

Live AgentX and staging services are online. Core rule established: eToro is the source of truth. Sizing uses master portfolio virtual balance, not copier investment amount.

Overall State

Production product with live users and staging flow. Security, strategy marketplace, and eToro auth/session reliability remain active work areas.

Future Development

Stabilize eToro auth, finish Strategy Marketplace safely, harden admin/auth flows, improve monitoring, and link with Strategy Builder and PI Central.

Live product, hardening needed

Evidence confidence: high. Running in PM2 on port 3035 plus staging.

Portfolio Rebalancer

Original #5 - optimizer and rebalance workflow

Live / running

What Was Done

Service is running. Investigation work covered optimizer behavior, position grouping, and rebalancing/execution safety concerns.

Overall State

Operational service, but product readiness and execution permissions need confirmation before prioritization.

Future Development

Define target user, execution boundaries, simulation vs live mode, alerts, audit trail, and integration with AgentX/SmartPortfolio.

Running service

Evidence confidence: medium-high. PM2 online; product maturity needs confirmation.

SmartPortfolio

Original #6 - smart portfolio creation/review

Live / running

What Was Done

SmartPortfolio app, validation service, and SP Review workbench are running. Workbench supports review/vetting of strategy and portfolio candidates.

Overall State

Active product/workbench stack. Maturity depends on whether the target is internal review, PI-facing creation, or production deployment.

Future Development

Clarify product owner workflow, validation gates, compliance checklist, publishing path, and relationship to AgentX Strategy Store.

Running internal product

Evidence confidence: high for runtime, medium for business maturity.

VIPSignals

Original #8 - signal product stack

Live / running

What Was Done

Client, admin, engine, and paper-trade monitor are online. Reliability audits and dev-to-prod transition work exist in the workspace.

Overall State

Operational signal platform with multiple live processes. Business priority and readiness for external users need confirmation.

Future Development

Confirm user segment, signal QA, monitoring, paper/live execution boundaries, and whether it feeds AgentX or remains standalone.

Live stack

Evidence confidence: high for runtime, medium for market readiness.

QuantDB / Unified Data API

Original #9 - data platform

Platform layer

What Was Done

Unified data platform consolidated into quantdb with schemas for raw, data, signals, portfolio, app, dcc, and agentx. API is online on port 3055.

Overall State

Core platform dependency for prices, fundamentals, factors, signals, macro, portfolio, and strategy analytics.

Future Development

Improve data lineage, PIT/as-of coverage, dataset versioning, quality dashboards, and expose clean APIs for Strategy Builder, TerminalX, and AgentX.

Production platform

Evidence confidence: high. API is online; maturity of each dataset still varies.

Signal Centre

Added project - signal decision/admin surface

Live / running

What Was Done

Documented as the #1 DCC consumer for Gold/Platinum data and signal inputs. The live admin surface is mapped to signalcentre.quantclaw.org through the vipsignals-admin process.

Overall State

Operational signal/admin layer that sits between the data backbone and downstream signal products. Product boundary versus VIPSignals still needs owner confirmation.

Future Development

Clarify ownership, strengthen signal QA, connect directly to QuantDB/DCC quality status, and define which signals feed AgentX, VIPSignals, and PI workflows.

Live admin surface

Evidence confidence: high for runtime, medium for product boundary.

PI Central

Original #21 - Popular Investor center

Needs confirmation

What Was Done

Defined as the central product direction for Popular Investor workflows. Workspace contains PI command-center research and demo assets.

Overall State

Product concept and research are present. Current app surface, owner, and deployment status need confirmation.

Future Development

Define the first PI workflow: agent management, content/CMO tasks, portfolio insight, strategy marketplace, or onboarding cockpit.

Concept / research

Evidence confidence: medium. Needs Shay confirmation.

GPU Quant Sub-Agent

Original #31 - GPU worker for quant research

Blocked

What Was Done

Plan defined: dedicated GPU sub-agent for backtests and ML strategies, with local/free orchestrator and Qlib-style engine.

Overall State

Not running as intended because current OCI machine is CPU-only. Needs GPU capacity before it can become a production worker.

Future Development

Provision GPU instance, install quant stack, connect to Strategy Builder and QuantDB, and set cost/runtime controls.

Blocked on GPU instance

Evidence confidence: high. Blocker is explicit.

Strategy Builder / Vibe-to-Python Runner

Added project - natural language to Python strategy

Design / planned

What Was Done

Concept identified as first-class: user describes a strategy, system creates Python, runs validation/backtest, logs the run, and can graduate candidates into Strategy Store or AgentX.

Overall State

Product direction is clear. Implementation maturity needs confirmation; existing strategy/backtest folders and run logs can serve as foundation.

Future Development

Build prompt-to-spec, spec-to-Python, sandboxed execution, result review, six-gate validation, run log, and publish/monitor path.

Planned product

Evidence confidence: medium. Needs owner confirmation on MVP status.

Questions For Shay

Needed to avoid guessing.

What maturity scale should we use: 1-5, traffic-light, or stages such as Concept, Prototype, Internal Alpha, Beta, Live, Scaled?
For TerminalX, what exists today that should be counted as shipped: UI, data views, watchlists, alerts, terminal shell, or only research/spec?
For Signal Centre, should it be treated as a standalone product, the VIPSignals admin layer, or the shared signal governance layer for all apps?
For PI Central, is this a standalone product, an AgentX module, or a CMOClaw/PI dashboard?
For Strategy Builder, do we already have an MVP screen or only backend strategy scripts/run logs?
For SmartPortfolio and Portfolio Rebalancer, should maturity be judged by internal readiness or client-facing readiness?
Which of these projects are intended for immediate eToro/internal use versus external/public users?
Who is the business owner for each project, and what is the target date for the next milestone?