alphaverify 0.1.0__tar.gz

alphaverify-0.1.0/LICENSE

@@ -0,0 +1,121 @@
+Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.

alphaverify-0.1.0/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.4
+Name: alphaverify
+Version: 0.1.0
+Summary: Conditional barrier-touch probability pipeline.
+Author: chengmarc
+License-Expression: CC0-1.0
+Project-URL: Homepage, https://github.com/doubletrends/alpha-verify
+Project-URL: Repository, https://github.com/doubletrends/alpha-verify
+Project-URL: Issues, https://github.com/doubletrends/alpha-verify/issues
+Keywords: quantitative-finance,technical-analysis,hypothesis-testing,multiple-testing,barrier-touch,market-research
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Environment :: GPU :: NVIDIA CUDA
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business :: Financial :: Investment
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: numpy>=2.0
+Requires-Dist: pandas>=2.2
+Requires-Dist: matplotlib>=3.8
+Requires-Dist: yfinance>=0.2
+Requires-Dist: openpyxl>=3.1
+Requires-Dist: safetensors>=0.5
+Requires-Dist: torch>=2.0
+Dynamic: license-file
+
+<div align="center">
+  <h1><strong>AlphaVerify</strong> - Multi-Asset Financial Strategy Debunker</h1>
+  <img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/alphaverify-icon-old.svg" alt="AlphaVerify icon" width="180">
+  <br>
+  <h3>Most “technical” indicators are essentially astrology with better charts.<br>  
+  AlphaVerify is built to put an end to all that bullshit.</h3>
+</div>
+
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/stats-dark.svg">
+    <img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/stats-light.svg" width="100%" alt="1,000 synthetic OHLC histories; 552 NASDAQ condition bins tested, across 57 features; 25 bins cleared, where pure chance predicts 27.6">
+  </picture>
+</p>
+
+# How to look at the figures
+Each figure tests one market condition. 
+
+**Left:** while the condition holds, is the NASDAQ more likely (red) or less likely (blue) to move by a given percentage within 30 days? 
+**Right:** the same test run on 1,000 random markets that contain no signal. To count as an edge, the real score (blue line) has to beat 95% of them (dashed line).
+
+## The golden cross - folklore
+
+Traders everywhere watch for the 50-day average to cross above the 200-day. Once it runs about 10% above, the heatmap looks decisive: the odds of a 4% drop jump, the odds of a 4% rise fall, a **24.5-point** swing. It looks like a real edge. It's folklore: random markets draw one at least this strong 8.4% of the time.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__ma_cross_50_200__bin_09.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__ma_cross_50_200__bin_09.png" width="100%" alt="MA Cross 50-200 bin 9: a 24.5 percentage-point contrast below the null 95th percentile"></a>
+</p>
+
+## Above the 200-day - a textbook mirror
+
+"Stay long while price is above the 200-day" is trend following's first rule. With price 4% to 6% above it, the picture is a near-perfect mirror: rises more likely, drops much less likely, a **27.4-point** swing. Random markets draw one at least this strong 23% of the time.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__ma_ratio_200__bin_04.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__ma_ratio_200__bin_04.png" width="100%" alt="MA Ratio-200 bin 4: a 27.4 percentage-point contrast well inside the synthetic null"></a>
+</p>
+
+## Low bond yields - the 42-point edge
+
+Cheap money lifts stocks; everyone knows that. When the 10-year Treasury yield sat below 1.34%, the NASDAQ was far more likely to rally 8% within a month: a **42-point** swing that grows steadily with time. It looks like a macro regime you could trade. It isn't. Random markets draw one at least this strong 7.6% of the time. Close, but not an edge.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__tnx_level__bin_01.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__tnx_level__bin_01.png" width="100%" alt="TNX Level bin 1: a 42 percentage-point upside contrast whose score still falls below the null 95th percentile"></a>
+</p>
+
+## Moderate yields - same signal, opposite story
+
+Move the yield to 2.5%-2.9% and the story flips: an 8% drop becomes likelier than a rise, a **21.2-point** swing. Read alone, it's a second, bearish regime. Random markets draw one at least this strong 41% of the time.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__tnx_level__bin_06.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__tnx_level__bin_06.png" width="100%" alt="TNX Level bin 6: a 21.2 percentage-point downside contrast, well inside the synthetic null"></a>
+</p>
+
+# Try it
+
+<p>
+  <img src="https://img.shields.io/badge/PyTorch-%E2%89%A5%202.0-EE4C2C?logo=pytorch&logoColor=white" alt="PyTorch >= 2.0">
+  <img src="https://img.shields.io/badge/CUDA-%E2%89%A5%2012.0-76B900?logo=nvidia&logoColor=white" alt="CUDA >= 12.0">
+</p>
+
+**PyTorch is mandatory. A dedicated CUDA-enabled GPU is strongly recommended.**
+
+The distribution, CLI, and Python package are named `alphaverify`.
+The repository name remains `alpha-verify`. `init` copies one of the shipped
+workspaces into `./workspaces`, which is where every later command looks for it.
+
+```
+python -m pip install alphaverify
+
+alphaverify init --workspace nasdaq_daily
+alphaverify measure
+alphaverify compare
+alphaverify validate
+alphaverify select
+alphaverify forecast
+```
+
+From a checkout, `python -m pip install -e .` installs the same CLI, and `init`
+is unnecessary because `workspaces/` is already there; run commands from the
+repository root and reinstall the editable package after updating it. To keep
+workspaces anywhere else, pass `--workspaces-dir DIR` or set `$ALPHAVERIFY_WORKSPACES`.
+
+After `validate`, the figure for every tested bin, including the four above, is in `workspaces/nasdaq_daily/03_validation/plot/`.
+
+Each pipeline command also accepts `--cuda` when a CUDA-capable PyTorch installation and device are available.
+
+# How it works
+
+| Stage | CLI Command | What it does | Mathematical form |
+|---|---|---|---|
+| 1 | measure | Measure conditional probabilities | `π_condition(r, δ, k, t)` |
+| 2 | compare | Compare them with the baseline | `G = π_condition − π_baseline` |
+| 3 | validate | Validate every supported bin against the null | `p̂_k < 0.05 or p̂_k ≥ 0.05` |
+| 4 | select | Retain cleared bins, rank them by evidence, and render their figures | `K_selected = {k : p̂_k < 0.05}` |
+| 5 | forecast | List which nodes cleared and with which bins; combine those active on the last stored bar, one per family, and compare with their historical joint rate | `N_cleared = {node(k) : k ∈ K_selected}`; `logit P = logit π_baseline + Σ_k (logit π_k − logit π_baseline)` |
+
+
+Validation writes `03_validation/`; selection consumes only a current validation result and writes `04_selection/`; the forecast consumes only a current selection and writes `05_forecast/`. Every cleared bin is retained—there is no top-k ranking or secondary economic gate.
+
+# Repository map
+
+- [Source architecture](https://github.com/doubletrends/alpha-verify/blob/master/src/alphaverify/README.md) — implementation boundaries, data flow, artifact contracts, and null mechanics.
+- [Workspaces](https://github.com/doubletrends/alpha-verify/blob/master/workspaces/README.md) — experiment declarations, plugins, generated artifacts, and safe workspace changes.
+
+AlphaVerify is research software, not investment advice.
+
+The complete numerical specification is available as LaTeX in
+[`mathematics.tex`](https://github.com/doubletrends/alpha-verify/blob/master/mathematics.tex).

alphaverify-0.1.0/README.md

@@ -0,0 +1,108 @@
+<div align="center">
+  <h1><strong>AlphaVerify</strong> - Multi-Asset Financial Strategy Debunker</h1>
+  <img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/alphaverify-icon-old.svg" alt="AlphaVerify icon" width="180">
+  <br>
+  <h3>Most “technical” indicators are essentially astrology with better charts.<br>  
+  AlphaVerify is built to put an end to all that bullshit.</h3>
+</div>
+
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/stats-dark.svg">
+    <img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/stats-light.svg" width="100%" alt="1,000 synthetic OHLC histories; 552 NASDAQ condition bins tested, across 57 features; 25 bins cleared, where pure chance predicts 27.6">
+  </picture>
+</p>
+
+# How to look at the figures
+Each figure tests one market condition. 
+
+**Left:** while the condition holds, is the NASDAQ more likely (red) or less likely (blue) to move by a given percentage within 30 days? 
+**Right:** the same test run on 1,000 random markets that contain no signal. To count as an edge, the real score (blue line) has to beat 95% of them (dashed line).
+
+## The golden cross - folklore
+
+Traders everywhere watch for the 50-day average to cross above the 200-day. Once it runs about 10% above, the heatmap looks decisive: the odds of a 4% drop jump, the odds of a 4% rise fall, a **24.5-point** swing. It looks like a real edge. It's folklore: random markets draw one at least this strong 8.4% of the time.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__ma_cross_50_200__bin_09.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__ma_cross_50_200__bin_09.png" width="100%" alt="MA Cross 50-200 bin 9: a 24.5 percentage-point contrast below the null 95th percentile"></a>
+</p>
+
+## Above the 200-day - a textbook mirror
+
+"Stay long while price is above the 200-day" is trend following's first rule. With price 4% to 6% above it, the picture is a near-perfect mirror: rises more likely, drops much less likely, a **27.4-point** swing. Random markets draw one at least this strong 23% of the time.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__ma_ratio_200__bin_04.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__ma_ratio_200__bin_04.png" width="100%" alt="MA Ratio-200 bin 4: a 27.4 percentage-point contrast well inside the synthetic null"></a>
+</p>
+
+## Low bond yields - the 42-point edge
+
+Cheap money lifts stocks; everyone knows that. When the 10-year Treasury yield sat below 1.34%, the NASDAQ was far more likely to rally 8% within a month: a **42-point** swing that grows steadily with time. It looks like a macro regime you could trade. It isn't. Random markets draw one at least this strong 7.6% of the time. Close, but not an edge.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__tnx_level__bin_01.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__tnx_level__bin_01.png" width="100%" alt="TNX Level bin 1: a 42 percentage-point upside contrast whose score still falls below the null 95th percentile"></a>
+</p>
+
+## Moderate yields - same signal, opposite story
+
+Move the yield to 2.5%-2.9% and the story flips: an 8% drop becomes likelier than a rise, a **21.2-point** swing. Read alone, it's a second, bearish regime. Random markets draw one at least this strong 41% of the time.
+
+<p align="center">
+  <a href="https://github.com/doubletrends/alpha-verify/blob/master/docs/bin_figure__tnx_level__bin_06.png"><img src="https://raw.githubusercontent.com/doubletrends/alpha-verify/master/docs/bin_figure__tnx_level__bin_06.png" width="100%" alt="TNX Level bin 6: a 21.2 percentage-point downside contrast, well inside the synthetic null"></a>
+</p>
+
+# Try it
+
+<p>
+  <img src="https://img.shields.io/badge/PyTorch-%E2%89%A5%202.0-EE4C2C?logo=pytorch&logoColor=white" alt="PyTorch >= 2.0">
+  <img src="https://img.shields.io/badge/CUDA-%E2%89%A5%2012.0-76B900?logo=nvidia&logoColor=white" alt="CUDA >= 12.0">
+</p>
+
+**PyTorch is mandatory. A dedicated CUDA-enabled GPU is strongly recommended.**
+
+The distribution, CLI, and Python package are named `alphaverify`.
+The repository name remains `alpha-verify`. `init` copies one of the shipped
+workspaces into `./workspaces`, which is where every later command looks for it.
+
+```
+python -m pip install alphaverify
+
+alphaverify init --workspace nasdaq_daily
+alphaverify measure
+alphaverify compare
+alphaverify validate
+alphaverify select
+alphaverify forecast
+```
+
+From a checkout, `python -m pip install -e .` installs the same CLI, and `init`
+is unnecessary because `workspaces/` is already there; run commands from the
+repository root and reinstall the editable package after updating it. To keep
+workspaces anywhere else, pass `--workspaces-dir DIR` or set `$ALPHAVERIFY_WORKSPACES`.
+
+After `validate`, the figure for every tested bin, including the four above, is in `workspaces/nasdaq_daily/03_validation/plot/`.
+
+Each pipeline command also accepts `--cuda` when a CUDA-capable PyTorch installation and device are available.
+
+# How it works
+
+| Stage | CLI Command | What it does | Mathematical form |
+|---|---|---|---|
+| 1 | measure | Measure conditional probabilities | `π_condition(r, δ, k, t)` |
+| 2 | compare | Compare them with the baseline | `G = π_condition − π_baseline` |
+| 3 | validate | Validate every supported bin against the null | `p̂_k < 0.05 or p̂_k ≥ 0.05` |
+| 4 | select | Retain cleared bins, rank them by evidence, and render their figures | `K_selected = {k : p̂_k < 0.05}` |
+| 5 | forecast | List which nodes cleared and with which bins; combine those active on the last stored bar, one per family, and compare with their historical joint rate | `N_cleared = {node(k) : k ∈ K_selected}`; `logit P = logit π_baseline + Σ_k (logit π_k − logit π_baseline)` |
+
+
+Validation writes `03_validation/`; selection consumes only a current validation result and writes `04_selection/`; the forecast consumes only a current selection and writes `05_forecast/`. Every cleared bin is retained—there is no top-k ranking or secondary economic gate.
+
+# Repository map
+
+- [Source architecture](https://github.com/doubletrends/alpha-verify/blob/master/src/alphaverify/README.md) — implementation boundaries, data flow, artifact contracts, and null mechanics.
+- [Workspaces](https://github.com/doubletrends/alpha-verify/blob/master/workspaces/README.md) — experiment declarations, plugins, generated artifacts, and safe workspace changes.
+
+AlphaVerify is research software, not investment advice.
+
+The complete numerical specification is available as LaTeX in
+[`mathematics.tex`](https://github.com/doubletrends/alpha-verify/blob/master/mathematics.tex).

alphaverify-0.1.0/pyproject.toml

@@ -0,0 +1,76 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "alphaverify"
+version = "0.1.0"
+description = "Conditional barrier-touch probability pipeline."
+readme = "README.md"
+requires-python = ">=3.12"
+license = "CC0-1.0"
+license-files = ["LICENSE"]
+authors = [{ name = "chengmarc" }]
+keywords = [
+  "quantitative-finance",
+  "technical-analysis",
+  "hypothesis-testing",
+  "multiple-testing",
+  "barrier-touch",
+  "market-research",
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Environment :: GPU :: NVIDIA CUDA",
+  "Intended Audience :: Science/Research",
+  "Intended Audience :: Financial and Insurance Industry",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Office/Business :: Financial :: Investment",
+  "Topic :: Scientific/Engineering :: Information Analysis",
+]
+dependencies = [
+  "numpy>=2.0",
+  "pandas>=2.2",
+  "matplotlib>=3.8",
+  "yfinance>=0.2",
+  "openpyxl>=3.1",
+  "safetensors>=0.5",
+  "torch>=2.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/doubletrends/alpha-verify"
+Repository = "https://github.com/doubletrends/alpha-verify"
+Issues = "https://github.com/doubletrends/alpha-verify/issues"
+
+[project.scripts]
+alphaverify = "alphaverify.cli:main"
+
+[tool.setuptools]
+# The shipped workspaces are distributed as `alphaverify.templates`, the source
+# `alphaverify init` copies from. Adding a workspace means adding it here too;
+# tests/test_workspace_data.py fails when one is missing.
+package-dir = { "" = "src", "alphaverify.templates" = "workspaces" }
+packages = [
+  "alphaverify",
+  "alphaverify.domain",
+  "alphaverify.infrastructure",
+  "alphaverify.pipeline",
+  "alphaverify.presentation",
+  "alphaverify.templates",
+  "alphaverify.templates._shared",
+  "alphaverify.templates.btc_daily",
+  "alphaverify.templates.btc_hourly",
+  "alphaverify.templates.nasdaq_daily",
+]
+
+[tool.setuptools.package-data]
+"alphaverify.templates.btc_daily" = ["universe.json"]
+"alphaverify.templates.btc_hourly" = ["universe.json"]
+"alphaverify.templates.nasdaq_daily" = ["universe.json"]
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]

alphaverify-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

alphaverify-0.1.0/src/alphaverify/__init__.py

@@ -0,0 +1 @@
+"""Conditional barrier-touch probability pipeline."""

alphaverify-0.1.0/src/alphaverify/cli.py

@@ -0,0 +1,185 @@
+"""Command-line interface for the barrier-touch pipeline."""
+
+from __future__ import annotations
+
+import argparse
+from collections.abc import Callable
+from dataclasses import dataclass
+from pathlib import Path
+
+from alphaverify.domain import tensor_runtime
+from alphaverify.infrastructure.scaffold import available_templates, copy_workspace
+from alphaverify.infrastructure.workspace import (
+    STAGE_DIRECTORIES,
+    WORKSPACES_DIRNAME,
+    Workspace,
+    workspaces_root,
+)
+from alphaverify.pipeline.reporting import RULE, ansi_styles, color_enabled
+from alphaverify.pipeline.step_01_surface import cmd_surface
+from alphaverify.pipeline.step_02_shift import cmd_shift
+from alphaverify.pipeline.step_03_validation import cmd_validation
+from alphaverify.pipeline.step_04_selection import cmd_selection
+from alphaverify.pipeline.step_05_forecast import cmd_forecast
+
+
+@dataclass(frozen=True)
+class Command:
+    name: str
+    summary: str
+    handler: Callable[[Workspace], None]
+    stage: str
+
+
+COMMANDS = (
+    Command(
+        "measure",
+        "Measure raw conditional probabilities",
+        cmd_surface,
+        stage="surface",
+    ),
+    Command(
+        "compare",
+        "Compare raw probabilities to baseline",
+        cmd_shift,
+        stage="shift",
+    ),
+    Command(
+        "validate",
+        "Validate all eligible bins vs null",
+        cmd_validation,
+        stage="validation",
+    ),
+    Command(
+        "select",
+        "Select cleared bins and heatmaps",
+        cmd_selection,
+        stage="selection",
+    ),
+    Command(
+        "forecast",
+        "Cleared nodes and their forecast",
+        cmd_forecast,
+        stage="forecast",
+    ),
+)
+COMMAND_BY_NAME = {command.name: command for command in COMMANDS}
+
+# Setup, not a stage: it writes the workspace that the stage commands then read.
+INIT_COMMAND = "init"
+
+
+def overview(color: bool) -> str:
+    """Root help: setup, then the pipeline commands in order with their artifact directories."""
+    accent, bold, dim, reset = ansi_styles(color)
+
+    def heading(text: str) -> list[str]:
+        return [f"  {accent}{bold}{text}{reset}", ""]
+
+    def row(name: str, summary: str, target: str) -> str:
+        return (
+            f"    {bold}{name}{reset}{' ' * (12 - len(name))}"
+            f"{summary:<38}→ {dim}{target}{reset}"
+        )
+
+    lines = [
+        f"{accent}{RULE}{reset}",
+        "AlphaVerify",
+        "Conditional barrier-touch probability pipeline",
+        f"{accent}{RULE}{reset}",
+        "",
+        *heading("Setup"),
+        row(INIT_COMMAND, "Copy a shipped workspace here", f"{WORKSPACES_DIRNAME}/NAME/"),
+        "",
+        *heading("Pipeline"),
+    ]
+    for command in COMMANDS:
+        lines.append(row(command.name, command.summary, f"{STAGE_DIRECTORIES[command.stage]}/"))
+    lines += [
+        "",
+        *heading("Options"),
+        "    --workspace NAME        Select a workspace",
+        "    --workspaces-dir DIR    Workspace root (or $ALPHAVERIFY_WORKSPACES)",
+        "    --cuda                  Use CUDA numerical kernels",
+        "    -h, --help              Show this help",
+    ]
+    return "\n".join(lines) + "\n"
+
+
+class RootParser(argparse.ArgumentParser):
+    """Root help is the command overview; subcommands keep argparse option help."""
+
+    def format_help(self) -> str:
+        return overview(color_enabled())
+
+
+def _add_workspace_options(parser: argparse.ArgumentParser) -> None:
+    parser.add_argument("--workspace", metavar="NAME", default="nasdaq_daily")
+    parser.add_argument(
+        "--workspaces-dir",
+        metavar="DIR",
+        default=None,
+        help=(
+            "directory holding workspaces "
+            f"(default: $ALPHAVERIFY_WORKSPACES, else ./{WORKSPACES_DIRNAME})"
+        ),
+    )
+
+
+def _add_run_options(parser: argparse.ArgumentParser) -> None:
+    _add_workspace_options(parser)
+    parser.add_argument(
+        "--cuda",
+        action="store_true",
+        help="run numerical barrier kernels on CUDA (requires an available CUDA PyTorch device)",
+    )
+
+
+def build_parser() -> argparse.ArgumentParser:
+    parser = RootParser(prog="alphaverify")
+    commands = parser.add_subparsers(
+        dest="command", metavar="COMMAND", parser_class=argparse.ArgumentParser
+    )
+
+    _add_workspace_options(
+        commands.add_parser(
+            INIT_COMMAND,
+            help=f"copy a shipped workspace ({', '.join(available_templates())}) into place",
+        )
+    )
+    for command in COMMANDS:
+        _add_run_options(commands.add_parser(command.name))
+    return parser
+
+
+def cmd_init(name: str, workspaces_dir: str | None) -> None:
+    """Write one shipped workspace declaration where the stage commands will look for it."""
+    root = workspaces_root(workspaces_dir)
+    written = copy_workspace(name, root)
+    accent, bold, dim, reset = ansi_styles(color_enabled())
+    print(f"\n{accent}{RULE}{reset}")
+    print(f"{accent}{bold}Workspace {name}{reset} → {root / name}")
+    print(f"{accent}{RULE}{reset}\n")
+    for path in written:
+        print(f"  {dim}{path.relative_to(root)}{reset}")
+    option = "" if root == Path.cwd() / WORKSPACES_DIRNAME else f" --workspaces-dir {root}"
+    print(f"\n  next: alphaverify measure --workspace {name}{option}\n")
+
+
+def main(argv: list[str] | None = None) -> None:
+    parser = build_parser()
+    args = parser.parse_args(argv)
+    if args.command is None:
+        parser.print_help()
+        return
+    if args.command == INIT_COMMAND:
+        cmd_init(args.workspace, args.workspaces_dir)
+        return
+    ws = Workspace(args.workspace, args.workspaces_dir)
+    tensor_runtime.configure(args.cuda)
+
+    COMMAND_BY_NAME[args.command].handler(ws)
+
+
+if __name__ == "__main__":
+    main()

alphaverify-0.1.0/src/alphaverify/domain/__init__.py

@@ -0,0 +1 @@
+"""Pure numerical models and feature transforms."""