Repository navigation
Surface the calendar's new knowledge_cutoff field - #2
Merged
Merged
Conversation
GET /v1/events now serves knowledge_cutoff on every event: the market close that opens the event's one-day return window, which is the boundary on what information an agent may use (strictly before it). events_frame previously dropped unknown keys via its fixed column list, so the field is added to the schema (optional, for older cached payloads), the frame (parsed to UTC like event_datetime), the sample calendar (values computed with the same window-opening-close rule), and the column-order tests.
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
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.
What
GET /v1/eventsnow serves aknowledge_cutoffon every event — the market close that opens the event's one-day return window, i.e. the boundary on what information an agent may legally use (strictly before it). This PR surfaces it in the examples:schemas.CalendarEventgains the field (optional, so older cached/sample payloads still parse)frames.events_frameincludes it as a parsed UTC column (it was previously silently dropped by the fixed column list)Merge timing
Hold until the production API serves the field (currently live on dev + beta). The change is backward-tolerant either way — the schema field is optional.