u/alias454

Thought I’d share a follow-up on YATSEE since I posted here before and appreciated the feedback.

YATSEE has moved away from “a bunch of scripts” toward a cleaner local-first pipeline for processing public meeting audio.

YATSEE is not meant to be another AI meeting notes app. That space is crowded enough already.

What I’m more interested in is all the audio that already exists and usually stays buried. City council meetings, committee meetings, public hearings, interviews, field notes, research recordings, incident reviews, podcasts, lectures, and other long recordings that are technically public or available, but hard to inspect in practice.

AI summaries are not the interesting part. That’s the easy part.

The harder and more useful part is keeping the pipeline inspectable. Preserving the transcript. Cleaning up automatic speech recognition artifacts without changing meaning. Separating source text from model-generated interpretation. Making the output searchable without pretending it is perfect. Letting a person trace important claims back to the actual transcript or recording.

What's changed since the earlier versions?

• acquisition has been split out more cleanly into yatsee-fetch
• YATSEE core is more source-agnostic now
• inputs can come from fetched files, local files, yatsee-recorder output, or direct media links
• the CLI is split into clearer stages for config, audio, transcript, and intelligence work
• I’ve been experimenting with civic signal extraction for motions, resolutions, payments, contracts, questions, and other review points

The signal extraction piece is not meant to create official minutes; it serves as a light review scaffold.

You can see example output for my town on my dev site, though I haven’t shared the summaries yet because they’re still a little rougher than I want for public consumption: https://opengov-data.pages.dev/

The repo has been moved to its own org: https://github.com/YATSEE-Labs/YATSEE

Of course, I’m open to any feedback. Thanks.

Laid off today from a role I started 5 weeks ago. Apparently project funding was cut. I was told directly it was strictly financial and not a performance issue. This was completely out of the blue and I was shocked.

Before that, I was impacted by a RIF in August 2025 and took a short career break. I restarted my job search in late January but it is still a 9 month gap on my resume.

I'm a staff-level security engineer, but took this Security Engineer role because the work aligned with what I wanted to be doing. It wasn't really an engineering focused company, but I was brought on as the foundational security engineer to build out the program and help support IT and compliance needs.

Of course it's hard to really have an impact in 5 weeks but I had already built out a basic working security inventory/audit evidence pipeline that was surfacing real risks along with some other process improvement initiatives that were in the works.

Trying to figure out how to frame this going forward?

thanks