Record the new-logger activation timestamp in project docs and analysis constants #8

Closed
opened 2026-09-09 03:53:47 +00:00 by agent-pi · 1 comment
Collaborator

The hardened logger went live at 2026-09-09 13:52:03 AEST (first connect marker: 13:52:03.421890+10:00). Records before that moment lack the _age_s map and event lines; records after have them. Future analysis needs this boundary recorded durably, and the pre-existing deployment-events constant in analyze.py is the established place for split points.

The hardened logger went live at 2026-09-09 13:52:03 AEST (first connect marker: 13:52:03.421890+10:00). Records before that moment lack the _age_s map and event lines; records after have them. Future analysis needs this boundary recorded durably, and the pre-existing deployment-events constant in analyze.py is the established place for split points.
Author
Collaborator

Plan of attack

  • AGENTS.md Logger metadata bullet: append the activation timestamp (2026-09-09 13:52 AEST / 03:52 UTC), noting that field presence (_age_s in record) is the reliable discriminator, not dates.
  • analyze.py: add DEPLOY_LOGGER_METADATA = datetime(2026, 9, 9, 3, 52, 3, tzinfo=timezone.utc) alongside DEPLOY_IRR10_ONLY_GATE, same comment style.
  • Constant + docs only, no behaviour change; test suites stay green. Branch fix/issue-8-logger-activation-note, commit :memo: record new-logger activation timestamp, PR into main with Closes #8.
**Plan of attack** - `AGENTS.md` Logger metadata bullet: append the activation timestamp (2026-09-09 13:52 AEST / 03:52 UTC), noting that field presence (`_age_s` in record) is the reliable discriminator, not dates. - `analyze.py`: add `DEPLOY_LOGGER_METADATA = datetime(2026, 9, 9, 3, 52, 3, tzinfo=timezone.utc)` alongside `DEPLOY_IRR10_ONLY_GATE`, same comment style. - Constant + docs only, no behaviour change; test suites stay green. Branch `fix/issue-8-logger-activation-note`, commit `:memo: record new-logger activation timestamp`, PR into main with Closes #8.
Sign in to join this conversation.
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
marvin8/IrradiationToPowerProduction#8
No description provided.