Zain Dana HarperThe Build products

PRODUCTS · THE BUILD SUITE

Tools with their maturity named plainly.

A source-visible suite separate from the accountability research: forecasting and paper-trading toolkits, color utilities, and a shared interface layer. Distribution, source availability, and product readiness are different claims; this page keeps them separate.

Four companion packages (build-color, build-ui, build-oracle, build-engine) are distributed on PyPI; the remaining companion tools ship from source. Availability is not represented as end-to-end readiness.

forecasting · paper trading · interface · color · source-visible with explicit maturity boundaries

The forecasting & trading toolkits, paper-first by design.

build-oracle is a toolkit for predicting trends in data over time and spotting unusual breaks or jumps: ARIMA with automatic order selection, structural-break (changepoint) detection by information criterion (a score that picks the simplest explanation that still fits the data), and feature engineering, which builds extra signals like recent averages, lag values, and Fourier terms to help the model see patterns. The honest forecasting layer the others build on.

build-finance is a rule-based trading toolkit for stocks and crypto: backtesting (running a strategy against old data to see what would have happened), portfolio optimization using named methods (Markowitz, Black–Litterman, Hierarchical Risk Parity, Risk Parity), and strategies like an EMA-crossover momentum filter. It runs the analysis and the backtest; it doesn’t pretend a backtest is a promise.

build-engine is the self-adjusting loop on top: it trains forecasters, turns forecasts into signals, paper-trades or backtests them, and feeds the results back to adjust its own internal settings (the numbers that determine how the model behaves). It is paper-trading by default, and live brokerage is deliberately hard to switch on. It refuses to run live unless you set an explicit risk-acknowledgement in the environment. The guardrail is the feature.

These are real toolkits, honestly beta. Nothing here is financial advice, and the design assumes you’ll paper-trade first; it makes that the path of least resistance on purpose.

The shared interface and color layers.

build-ui is the shared controls library for the companion GUI tools. build-ecosystem installs the companion set, and build-color is the color-science member, with its own page. Each package’s repository and tests remain the authority for its exact maturity.

Where they really are.

build-oracle, build-finance, and build-engine are source-visible beta toolkits with named methods and paper-first defaults. build-ui and build-ecosystem are the shared controls and companion installer. Each readiness claim on this page is bounded to the named public package and its current evidence.

Source-visible, distribution paths named, and readiness claims bounded to evidence.

GitHub: HarperZ9  ·  Color member: build-color →  ·  ← the map  ·  the index