feat(git-setup): convert ingested connector timestamps at write time#163
Merged
Conversation
Upstreamed from accumulated instance experience into the Timezone Handling
section (assembles into all three brains — mode: briefing/consolidation/
dreaming/research, connector-agnostic):
Connector payloads frequently carry UTC timestamps (trailing Z / +00:00).
Never copy one verbatim into the KB / an action item / a DM as if it were
already in the display zone — rendered in {{TIMEZONE}} it can shift hours
and cross a calendar-day boundary, and the drift changes with DST. Parse
the source zone and convert to {{TIMEZONE}} at write time. Complements the
existing "never use bare date" generation rule.
Generic, zone-agnostic; originating example dropped.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md
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.
Part of the de-personalized Patterns batch — upstreaming accumulated instance rules into the engine phases (Phase-1 work for the connector-based migration, #156). Follows the method from #157.
What
One rule added to
phases/core/git-setup.md(Timezone Handling section; assembles into all three brains —mode: [briefing, consolidation, dreaming, research], which is correct for a connector-agnostic timestamp rule):KnowledgeGraph._load_schemaandvalidateraise uncaught exceptions on user-customizable YAML #46) — connector payloads frequently carry timestamps in UTC (trailingZ/+00:00). Never copy one verbatim into the KB, an action item, or a DM as if it were already in the display zone: rendered in{{TIMEZONE}}it can shift by hours and across a calendar-day boundary, and the drift changes with DST. Parse the source's zone and convert to{{TIMEZONE}}at write time, then label the result.This is the ingestion counterpart to the existing "never use bare
date— alwaysTZ={{TIMEZONE}}" rule, which only covers timestamp generation. Stays within the engine's single-{{TIMEZONE}}model (the dual/current-timezone idea is deliberately not introduced here — it's a separate design change).Verification
_assemble(cfg, kind): lands in SKILL + DREAMING + RESEARCH (matches the file's four-mode frontmatter); correct for a connector-agnostic rule.America/...), so it holds for any configured{{TIMEZONE}}.🤖 Generated with Claude Code