diff --git a/workplans/IR-WP-0008-external-brief-intake.md b/workplans/IR-WP-0008-external-brief-intake.md index 1f8c811..19abef9 100644 --- a/workplans/IR-WP-0008-external-brief-intake.md +++ b/workplans/IR-WP-0008-external-brief-intake.md @@ -4,12 +4,12 @@ type: workplan title: "Ingest external automation briefs" domain: infotech repo: intelligence-radar -status: active +status: finished flavor: implementation owner: grok topic_slug: custodian created: "2026-10-04" -updated: "2026-10-04" +updated: "2026-10-05" state_hub_workstream_id: "48ae162a-f232-5cbd-8b7a-c6fac6b03d72" --- @@ -60,8 +60,7 @@ briefs for the same period. An existing digest file is left as it is. ```task id: IR-WP-0008-T03 -status: wait -blocking_reason: "chatgpt.com and grok.com keep automation runs in the signed-in account. The shared ChatGPT weekly conversation is one snapshot, not a result feed. grok.com publishes no public link or export API. This repository does not send an account session to either site." +status: cancel priority: medium state_hub_task_id: "4829c33d-acc1-5357-b75f-93542d322a00" ``` @@ -76,3 +75,21 @@ Rechecked 2026-10-04: the inbox has no new export. It still holds the empty 3 October Grok file and the 27 September ChatGPT file whose archive name is already taken by different bytes. email-connect has no Intelligence Radar feed. No session was sent to chatgpt.com or grok.com. Stays wait. + +Rechecked 2026-10-05: inbox unchanged. Moved to IR-WP-0009-T01. + +## Closure and residual handoff — 2026-10-05 + +User requested closure. The delivered increment is the brief inbox. `import-briefs` +and `run-due` retain ChatGPT and Grok exports with their original bytes. Every due +run reports `needs_session` for both providers. `make check` passes. T03 is `cancel` +because pulling the websites still depends on an export or authorized feed outside +this repository. It has not been achieved; it moves to the record below. + +| Original scope | Authoritative follow-up | +| --- | --- | +| T03 pull website automation runs without an operator | IR-WP-0009-T01 | + +Two inbox files still need an operator: the empty 3 October Grok file and the +27 September ChatGPT file, whose name collides with different archived bytes. +Both are tracked in IR-WP-0009-T02. diff --git a/workplans/IR-WP-0009-website-brief-feed.md b/workplans/IR-WP-0009-website-brief-feed.md new file mode 100644 index 0000000..a4e1236 --- /dev/null +++ b/workplans/IR-WP-0009-website-brief-feed.md @@ -0,0 +1,45 @@ +--- +id: IR-WP-0009 +type: workplan +title: "Pull website automation briefs from an authorized feed" +domain: infotech +repo: intelligence-radar +status: active +flavor: implementation +owner: grok +topic_slug: custodian +created: "2026-10-05" +updated: "2026-10-05" +--- + +Residual of IR-WP-0008. The brief inbox is the unattended path for ChatGPT and +Grok automation briefs. This workplan holds the work that the inbox does not cover. + +## Pull website automation runs without an operator + +```task +id: IR-WP-0009-T01 +status: wait +blocking_reason: "chatgpt.com and grok.com keep automation runs in the signed-in account. The shared ChatGPT weekly conversation is one snapshot, not a result feed. grok.com publishes no public link or export API. This repository does not send an account session to either site." +priority: medium +``` + +Carried from IR-WP-0008-T03. Pulling the websites waits on a real export or an +authorized account feed. That feed must not rely on guessed private endpoints. +Until one exists, `run-due` keeps reporting `needs_session` for both providers. +An export saved to the inbox, including one saved from Grok's email delivery, +is still retained. + +## Resolve the two inbox leftovers + +```task +id: IR-WP-0009-T02 +status: todo +priority: low +``` + +The empty `261003-intelligenceRadarDaily_grok.txt` stays in the inbox. So does +`260927-intelligenceRadarDaily_chatgpt.txt`, whose name is already taken under +`archive/` by different bytes. The new bytes are already retained. An operator +decides whether to delete the empty file and how to name the second copy in the +archive. The importer must not overwrite archived bytes.