AI Chief of Staff
Jan – Apr 2026 on a team of 7 engineers
🔒 private repo — NExT Consulting
- Python
- LangGraph
- FastAPI
- PostgreSQL
32webhook types handled by the ingest worker
self-reported, private repo
consulting engagements go wrong quietly — a stalled Linear board, a channel that went silent, a PR nobody reviewed. this ingests all of it from Notion, Slack, Linear and GitHub and turns it into a prioritised risk briefing. i owned the event-driven core underneath it.
what i built
- the ingest worker, the part every webhook passes through before any agent sees it
- the concurrency model, which was the hard part: ordering has to hold inside a project without serialising across projects
- retry backoff and dead-letter handling, so a follow-up fetch that fails is retried and then parked rather than lost
how it works
- 1FastAPI validates the HMAC signature, extracts metadata, enqueues and returns 200 immediately
- 2webhook payloads are sparse, so a worker fetches the actual content from each platform's API
- 3each project gets its own Redis lock and a queue scored by event timestamp
- 4agents score the signals and the dashboard surfaces prioritised risk