Conversation
…mp decision logic
…behavior-equivalent
…ocessingPosition the causal ordering authority
…d a process_event_entry(...) wrapper that delegates to the existing canonical boundary
…resses the core contract: same ordered EventStreamEntry sequence + same explicit configuration => same derived StrategyState
…hat gives configuration a stable semantic identity/fingerprint for deterministic fold/replay contracts, without changing reducers
…onfiguration contract explicit
…ers navigate current core implementation contracts
… the execution-feedback boundary for future FillEvent ingress
…derSubmittedEvent
…bmittedEvent ingestion
…es the Control-Time Event boundary before implementation
…TimeEvent ingestion
…future runtime/adapter execution-feedback source must guarantee before canonical FillEvent ingress can be implemented
…eptual ExecutionFeedbackRecord source shape and guarantees required before future FillEvent ingress work
…t adapter/source gap
…current post-submission lifecycle authority split
… post-submission lifecycle authority split
…eneric adapter source capabilities and their semantic authority classifications without adding adapter APIs or hftbacktest-specific Core semantics
…ponsibilities for ProcessingContext and EventStreamCursor
…ime cursor behavior and future EventStreamCursor extraction invariants
…cords the current semantic implementation status
…target names and package structure before any mechanical rename
…ngchassis_core while preserving old nested imports through a compatibility shim
… and semantically aligned with the architecture described in the `docs` repository
…le and stable for downstream users such as Core Runtime
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
Finalize the current Core semantic processing milestone by aligning and validating the canonical processing API, event stream boundary, and public Core package surface.
Motivation
This change makes Core usable as the semantic foundation for Core Runtime. It confirms that canonical event processing is exposed through the public
tradingchassis_coreAPI and that Core remains venue-agnostic while preserving the current transitional boundaries.Type of Change
Technical Details
CoreConfigurationProcessingPositionEventStreamEntryprocess_event_entryfold_event_stream_entriesEventStreamEntry(position, event)with call-levelCoreConfiguration.core_runtime,trading_runtime, orhftbacktestin production code.Determinism & Reproducibility
Performance Impact
Tests
Validation performed:
python -m pytest -q tests/semantics/models/test_public_canonical_api_surface.py3 passedpython -m pytest -q tests/semantics198 passed./scripts/check.shBreaking Changes
None.
The public canonical processing API is validated, but no behavior or import path was changed.
Checklist