Conversation
Add the v0.1.9.4 walk-forward spec, tickets, ticket YAML, and batch plan. Carry forward the current horizon and methodology reference updates into the new version branch.
Mark the walk-forward packet active, close LDG-2612 after review, and update roadmap, design index, horizon, and AGENTS for the v0.1.9.4 implementation cycle.
Implement fold constructors, deterministic fold-list identity, and internal run/sweep experiment windows for v0.1.9.4 Batch 1. Mark LDG-2613 and LDG-2614 review-ready after Claude review patches.
Implement v0.1.9.4 Batch 2: window-aware precomputed feature validation, projection slicing for fold windows, scalar selection-rule constructors, minimal metric classification, and classed fail-closed selection errors.
Implement the first ledgr_walk_forward happy path over fold-local train sweeps, scalar selection, selected test runs, opening-state policy, deterministic seeds, and persisted session/fold/score rows.
Extend the walk-forward orchestrator with FAILED, INTERRUPTED, and PARTIAL persistence semantics, preserve failed train candidate score rows, add failure and interrupt coverage, document the test-run failure condition, and park the canonical run-return stream helper in horizon.
Expose read-only walk-forward reopen helpers, extract promotion-ready fold candidates with explicit rationale for latest, verify linked run identity, and make promotion respect candidate cost identity alongside risk identity.
Lead walk-forward results with train/test degradation, document MVP scope and caveats, and add Batch 7 documentation contract coverage.
Refresh release metadata, horizon dispositions, active agent context, identity contract documentation, and generated Rd/NAMESPACE surfaces for the walk-forward packet.
Mark walk-forward as completed, record release-gate evidence, update release context, fix installed-package source-guard portability, and index new walk-forward reference topics.
Use an internal walk-forward interrupt hook for partial-session coverage so installed Linux checks do not depend on strategy-level timestamp behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v0.1.9.4 walk-forward evaluation. Branch CI is green on the latest release commit e079da0.