Objective
Import the remaining EWS and EWG inputs through an explicit datastore workflow, then rebuild the monthly and daily Piard strategy reports offline without report-path cache mutation or loss of valid AllocateSmartly allocation content.
Approach
Added the fixed-scope import-piard-inputs command. It reads or explicitly refreshes the two Yahoo/yfinance caches, validates adjusted-OHLCV schema and requested coverage, records both file and canonical close-series hashes, preserves existing observations on overlap, and commits both tickers plus durable provenance in one transaction. The command can create a consistent non-overwriting SQLite backup before import.
The dependent rebuild exposed a pre-existing sharding bug: read_as_allocations did not route default market-database requests to market_as.sqlite, unlike the other AS readers and writers. Routing that reader through the shared shard resolver keeps the existing Piard AS allocation charts intact on fresh exports.
Results
- Imported 7,653 EWS and 7,653 EWG daily closes from 1996-03-18 through 2026-08-20.
- Preserved all 791,591 original OHLCV rows with zero missing rows and zero changed closes.
- Rebuilt both Piard variants with 295 monthly return observations and 616 allocation rows each using an offline report run.
- Published daily-path maximum drawdowns of -38.72% for the monthly variant and -39.21% for the daily redesign.
- Preserved all 12 recent and 228 yearly AllocateSmartly allocation rows for the monthly product; the canonical AS allocation-block hash is unchanged.
- Confirmed that report generation did not change the tracked database or either EWS/EWG cache fingerprint.
Validation
- Focused datastore and report-export suites passed.
- The imported SQLite database returned
integrity_check=okand remains below the tracked size limit. - Coverage, static-report, browser-facing, pipeline, and shared-artifact gates are run through their canonical producers before shipping.
Publication boundary
Raw Yahoo observations remain in the private repository datastore and are not exposed by the static site. Public artifacts contain only derived strategy returns, allocations, statistics, drawdowns, and coverage metadata. The operator command requires no account login or API key and emits no authenticated request data.