data-processing-workflows

To automate data processing pipelines, this Skill coordinates minutes division, speaker extraction, and politician matching through a deterministic execution order with explicit inputs, outputs, and staging tables. It uses a scriptable command interface to enforce the required processing sequence end-to-end.

Yes, you can extract speakers from minutes and match them to politicians automatically. The pipeline runs speaker extraction on processed minutes, then uses LLM-assisted matching to link identified speakers and conference members to known politician records.

The web scraping workflow supports optional Google Cloud Storage uploads. It manages scraped data and GCS URIs for later processing, allowing you to scrape minutes by council ID and upload the resulting files directly to your cloud storage bucket.

The best way to ensure traceability and reproducibility in governance analytics is to enforce a deterministic execution order with command-based orchestration. This approach uses explicit inputs, outputs, and staging tables for review to guarantee every pipeline run is verifiable.

Yes, you need staging tables to review minutes processing and conference member extraction. The pipeline enforces staging tables for intermediate data review before proceeding to downstream tasks like speaker extraction and politician matching.

For ad hoc investigations, the Skill requires strict adherence to its deterministic execution order and command-based orchestration. It does not support skipping pipeline stages, meaning you must process minutes, extract speakers, and match politicians in the enforced sequence.