core: make flow snapshot cost semantics explicit - #17
Merged
Conversation
Name every per-flow cost accessor as supplied cost so composition with an estimator cannot confuse scheduling estimates with actual resource service. Align the observable representation and contract documentation before publication.
pzhin
force-pushed
the
codex/unify-flow-snapshot-cost-vocabulary
branch
from
August 22, 2026 20:36
6043ede to
84f5fd9
Compare
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.
Summary
FlowSnapshotcost accessors to the explicit...SuppliedCost()vocabularytoString(), Javadoc, README, and the formal specification with caller-supplied scheduling-cost semantics...Cost()aliasesTesting
./mvnw --batch-mode --no-transfer-progress clean verify