github automation pipeline

this started as frustration with reports landing in slack and getting lost. the first pipeline is event-driven:

1. a google form writes a row into sheets
2. an apps script trigger transforms the row into a structured payload, computes a priority based on a small ruleset, and dispatches a repository_dispatch event to github
3. a github actions workflow opens an issue with the right labels and assigns a reviewer based on a routing table
4. failure modes feed back into a tracking sheet, not silently dropped

labels like source:form, needs-triage, ready, in-progress, blocked, resolved, p1, p2, and p3 turn messy submissions into an engineering workflow instead of a message pile.

broader operator layer

• daily 7am operational briefs that combine gmail, github repo updates, calendar context, and action items into one morning summary.
• openclaw-style agent workflows for personal ops, repo monitoring, email formatting, and task summaries.
• github projects workflows for product feedback triage and status reporting.
• apps script and github actions glue code that turns human forms into structured engineering tasks.

the common pattern is simple: if the same coordination step happens twice, i try to turn it into a system with inputs, routing, labels, and an observable failure mode.