Configure Huginn for Automated Reporting

TSY-3 Order: #3 Presenting Findings Has Dependencies

Updated 1 month, 2 weeks ago

Purpose

Keep the published story's underlying data current. Huginn has no MCP connector today.

Read docs/huginn/README.md. Check sibling ../huginn for an existing Agent/Scenario.
Huginn UI URL is org-specific — record it in playbook notes. Search Scenarios for lake / Athena / Streamlit.
Agent type follows the Present Findings surface (HTTP GET of streamlit_mart_url from docs/deploy-manifest.yaml if Streamlit). Jupyter has no live URL — defer if that was the surface.
Dry-run once. Record Agent name, schedule, purpose.
Flag as a future MCP-connector candidate.

A scheduled refresh exists, or an explicit deferral is written in docs/huginn/README.md.

streamlit_mart_url is empty — defer and say so.

Tell one story: reconstructed cycle first, then impact, then the deficiency register (finding + decision + dE/dK/dI + receiver). dK …

Agent: Insights Communicator Role Turns the Operations Analyst's findings into a narrative a stakeholder can …

Published Findings Notebook/Dashboard Document Required
Produced by: Present Findings