2026-09-13 22:42:09 +02:00
|
|
|
# Scheduling status and prompts
|
|
|
|
|
|
2026-09-13 23:07:41 +02:00
|
|
|
Repository scheduling: configured local daily/weekly runner and user timer units. The source Grok archive contains
|
2026-09-13 22:42:09 +02:00
|
|
|
external task/schedule UUIDs; ownership and execution were not verified. They are
|
2026-09-13 23:07:41 +02:00
|
|
|
historical references only. The local timer sends no app notifications or email.
|
2026-09-13 22:42:09 +02:00
|
|
|
|
|
|
|
|
Daily operator prompt: Review the watchlist for primary-source changes since the
|
|
|
|
|
previous pass. Record evidence with provenance, publication/event and observation
|
|
|
|
|
timestamps. Generate a draft for the event date, review each claim and mark gaps.
|
|
|
|
|
|
|
|
|
|
Weekly operator prompt: Generate the ISO-week draft. Synthesize decision-relevant
|
|
|
|
|
changes, unresolved contradictions, frontier evidence gaps, compendium edit proposals,
|
|
|
|
|
and benchmark health. Link observation IDs. Do not pad an empty week with invented news.
|
|
|
|
|
|
2026-09-13 23:07:41 +02:00
|
|
|
See docs/data-contracts.md and ops/schedule.json for the implemented runner.
|
2026-10-04 14:24:03 +02:00
|
|
|
|
|
|
|
|
ChatGPT and Grok website automations are a separate intake. Their exported
|
|
|
|
|
text files land in the local brief inbox configured by `ops/schedule.json`.
|
|
|
|
|
The due job retains files that are not already in that inbox's `archive/`
|
|
|
|
|
directory. It does not log into chatgpt.com or grok.com. Neither site exposes
|
|
|
|
|
a public feed of automation runs.
|
