FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Implementing the Editorial Runner execution flow
Connecting safe article acquisition, all-chunk screening, human decisions, and isolated Codex locally
Purpose
Advancing a database Execution into an actual article draft required connecting Feed retrieval, body extraction, screening, human decisions, Codex generation, and Room enrollment in one one-shot Runner.
The goal was to handle external articles and provider failures safely, pass only approved articles into an isolated fresh Codex, and establish a local execution flow in which the Runner itself did not generate or complete article content.
Implementation
daily execution entry retrieves previous-JST-day articles from RSS and Atom, enforcing HTTPS, DNS pinning to public addresses, redirect revalidation, timeouts, size limits, and DOCTYPE and ENTITY rejection. It extracts article pages with Readability first and does not substitute Feed summaries for body text.
Extracted text is split into deterministic, full-coverage chunks by Unicode scalar and every chunk is sent to the Model Armor client. Screening continues after a MATCH, while a missing chunk, execution skipped, or provider failure makes the entire article indeterminate and unapprovable. Local development uses a fake broker under the same contract.
Control Center gained Channels, Feeds, Execution review, article decisions, Generate, and Stop. A Feed with no items is a normal result; retrieval and screening failures are recorded as Execution failures, without automatic retry, catch-up, or mid-flow resume.
daily execution entry writes only approved articles to an owner-only workspace outside the repository and launches a fresh Codex with network, Web, MCP, plugins, apps, memory, credentials, and repository access disabled. It validates a strict localized draft and all-Agent reflections without Runner rewriting.
On thread.started, the root ID is recorded immediately on the Execution and registered for synchronization through the owner-only Connector by daily execution entry. After root metadata arrives, it is assigned to the product-default Editorial Room while descendant Threads and Messages continue synchronizing in the background.
Rendering diagram…
What was confirmed
Verification results
A fresh database reset, 151 pgTAP assertions, schema linting, and the Data API boundary passed.
Sixty-four TypeScript tests, 19 Public Web tests, 24 Swift tests, fixture integration, secret scanning, and the specification audit passed.
Code and contracts for safe retrieval, full-text chunking, the broker, Control Center, isolated Codex, and Room enrollment were applied to the target.
At the cutoff, an end-to-end run with a real Codex process, the Connector-to-Public-Web end-to-end path, and real LaunchAgent smoke were incomplete and were not counted as completion of the entire Story.
Basis for completion
This activity was complete when the initial execution flow from article acquisition through Codex output and Room enrollment was implemented and automated database and application checks passed. Real-process and real-service end-to-end checks remained explicitly separate work.