feat(alpha): model explicit execution costs and capacity - #84
Conversation
|
Warning Review limit reached
Next review available in: 17 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (13)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Change contract
Bind explicit taker execution costs and top-N book-capacity assumptions into alpha-harness evaluation protocols and evidence, deduct them consistently across formula and ONNX evaluation, and fail closed when required spread/depth evidence is missing or capacity is exceeded.
Out of scope
Dependency or merge order
None. This PR is based directly on
mainand can merge independently.Focused validation
cargo fmt --manifest-path rust_hft/Cargo.toml --package alpha-domain --package alpha-engine --package alpha-onnx-evaluator --package alpha-store --package alpha-harness -- --checkCARGO_BUILD_JOBS=1 cargo test --manifest-path rust_hft/Cargo.toml -p alpha-domain -p alpha-engine -p alpha-onnx-evaluator -p alpha-store -p alpha-harness(214 passed; 1 credential-gated live LLM test ignored)CARGO_BUILD_JOBS=1 cargo clippy --manifest-path rust_hft/Cargo.toml -p alpha-domain -p alpha-engine -p alpha-onnx-evaluator -p alpha-store -p alpha-harness --all-targets -- -D warningsRollout / rollback impact
New fields default to zero/false and are omitted from canonical serialization at defaults, preserving legacy protocol hashes and behavior. Research missions opt in through explicit CLI flags; invalid partial capacity configuration is rejected. Roll back by reverting this PR; no data migration or live-execution state is involved.