Bug
Current Data Machine pipeline publishes on wire.extrachill.com create festival_wire posts without any post metadata, despite PostTracking documenting centralized tracking for all successful post-producing tool calls.
Evidence
Recent posts:
festival_wire post 7930, published 2026-07-11 by the active Reddit → AI → wordpress_publish pipelinefestival_wire post 7929, published 2026-07-11 by the same pipeline shape
For both:
wp --url=wire.extrachill.com post meta list <id>
returns no rows.
The source URL is present only in the rendered article's final source paragraph. _datamachine_post_handler, _datamachine_post_flow_id, and _datamachine_source_url are all absent.
Older Wire posts through June remain discoverable via:
wp --url=wire.extrachill.com datamachine posts recent --post_type=festival_wire
and report handler=wordpress_publish, flow_id, and pipeline_id, showing this is a regression rather than an unsupported pipeline shape.
The active pipeline is pipeline 1 on the Wire site and uses Reddit fetch → AI → wordpress_publish across flows 1–29.
Expected
Every successful post-producing pipeline tool invocation stores generic origin tracking centrally as documented by DataMachine\Core\WordPress\PostTracking. When source_url is available in the packet/publish input, it should also persist to _datamachine_source_url.
Impact
datamachine posts recent|by-flow|by-handler|by-pipeline cannot find current posts.- Aggregated journalism loses auditable source provenance.
- Domain plugins cannot reliably resolve a published item back to its flow/job artifact.
Fix this in Data Machine rather than adding Wire-specific tracking workarounds.
Bug
Current Data Machine pipeline publishes on
wire.extrachill.comcreatefestival_wireposts without any post metadata, despitePostTrackingdocumenting centralized tracking for all successful post-producing tool calls.Evidence
Recent posts:
festival_wirepost 7930, published 2026-07-11 by the active Reddit → AI →wordpress_publishpipelinefestival_wirepost 7929, published 2026-07-11 by the same pipeline shapeFor both:
returns no rows.
The source URL is present only in the rendered article's final source paragraph.
_datamachine_post_handler,_datamachine_post_flow_id, and_datamachine_source_urlare all absent.Older Wire posts through June remain discoverable via:
and report
handler=wordpress_publish,flow_id, andpipeline_id, showing this is a regression rather than an unsupported pipeline shape.The active pipeline is pipeline 1 on the Wire site and uses Reddit fetch → AI →
wordpress_publishacross flows 1–29.Expected
Every successful post-producing pipeline tool invocation stores generic origin tracking centrally as documented by
DataMachine\Core\WordPress\PostTracking. Whensource_urlis available in the packet/publish input, it should also persist to_datamachine_source_url.Impact
datamachine posts recent|by-flow|by-handler|by-pipelinecannot find current posts.Fix this in Data Machine rather than adding Wire-specific tracking workarounds.