Any input.
The right action — gated by you.
Drop in a meeting, a document, or a chat. One validation gate checks it for the right team and real signal, then drafts the action it deserves — a board ticket, a draft PR, or a cited doc. Noise correctly lands nowhere. Every card cites its source, and nothing writes until you approve.
Takes work in any shape
A meeting, a document, a chat, a commit — each enters as one normalized event through a single pipeline. Adding a new input means writing a normalizer, nothing else.
Judges before it acts
One gate checks every input for the right team and real signal. Noise correctly lands nowhere — the proof it sells judgment, not just generation.
Acts on the real thing — gated by you
What survives becomes a drafted ticket, PR, or cited doc on your real board and repo. Each cites the exact source line and waits for your approval.
What's actually running
Each service below does one real job. Live status is the same probe the rest of the app uses — not a mock.
See what your teammate has already built for you
Your Day is the push-model home: a standup draft written for you, the items that moved while you were away, and anything the teammate has drafted and left waiting on your approval — all built from real captured events, badged sample or live so you always know what's real.
Your day
What the teammate prepared while you were away — skim, approve, go · see how it works →
Got an idea from a hallway chat or your own head? Drop it — the teammate files it into the pipeline and drafts the ticket.
One chat sees across your meetings, docs, threads, and board — and can draft a gated action.
How your work flows
One chat that oversees everything — and a crystal-clear map of what happens to anything the teammate ingests.
Overseer
Ask across your meetings, docs, threads, board, and repos. It answers from what it remembers, or drafts a gated action — and traces the path below.
Skills Forge
Standardize any output — a PRD, stories, a build spec, a status roll-up — to the same shape every pod uses. Pick a skill, seed it, review the draft, then send it to memory or the board.
Diverse triggers, one event, one gated path
Whatever comes in — a meeting, a document, a chat, a commit — is normalized to a single event shape and run through one mandatory gate. Pick a trigger to see exactly what's kept and where it goes.
How it works
One live picture: any input → the brain → a gated action. Watch it flow, or talk to the Overseer.
Teams Bot
Documents
Documents (xlsx / docx / ppt / pdf → text) come in through Intake, get classified, and land in Memory. Watch them flow through here.
Overseer
The one chat you talk to. Ask across meetings, docs & the board, or say “draft a ticket for…” — it answers or drafts a gated action, and everything it drafts lands in the queue below.
Technical PM teammate
Orchestrator
Memory / Knowledge
Pending actions human gate
Landed decisions
Board
What the teammate writes, on the real board — verify accuracy before it ever touches production ADO
Overseer
The one chat. Ask across your meetings, docs, threads & board — or drop a request in any shape. It reasons over the whole backlog, catches duplicates, and drafts the right ticket · gated by you
What do you need?
Describe it however it comes to mind — vague is fine. I'll search the team's 2,600+ work items, flag anything that already exists, and draft a ticket for your approval.
Meetings
Your week on the calendar — join & capture continue in so prep, capture & follow-ups stay in one thread