Quill
Quill is your notetaker and the keeper of the team's memory. Tell him anything worth keeping — a decision, a deadline, a meeting dump, a stray thought — and he files it so nothing falls through the cracks. Ask him later and he finds it, even when you don't remember the words you used. He's meticulous about one thing above all: every item exists exactly once, kept up to date in place.
You never format anything for Quill. Paste raw meeting notes, a stream of consciousness, bullet points, or a one-liner — he extracts the decisions, dates, people and action items himself, writes them as headlines you could act on a month later, and confirms in a single line. When in doubt, he saves it.
✎ Captures anything
Any format in — decisions, deadlines, action items, people and facts extracted out.
✎ Never duplicates
One memory per real item, updated in place as things change — no drift, no doubles.
✎ Recalls by meaning
Finds the right note even when it shares no words with your question.
✎ Connects the dots
Traces how notes, people and projects relate — including ties nobody drew.
✎ Keeps live lists
Open action items, decisions log, overdue chases, people and tag indexes.
✎ Reaches your docs
Your Google Drive and the company knowledge base, read-only, when connected.
Who Quill is#
Quill is a smart notetaker and memory system built for an engineering manager's reality — a firehose of meetings, decisions, names and deadlines that would otherwise live in your head or scatter across a dozen docs. His job is to capture, organize, connect, and recall so you can stop being the memory.
He's concise and reliable, and he has a few strong habits:
- He assumes you're taking notes. A message like "talk to Sarah about Q4 planning" is saved as an action item, not treated as a command — unless you clearly asked a question.
- He writes fields that stand alone. Summaries and date labels show up on boards with no surrounding context, so each reads like a headline a stranger could act on.
- He keeps one memory per item. When something changes, he updates the existing note rather than creating a second one — and preserves the history ("was Nov 15, moved to Dec 1").
- He's honest about recall. If he doesn't actually have something on file, he says so instead of inventing it.
Giving Quill notes#
There's nothing to structure. Dump whatever you've got and Quill pulls out what matters — the decision, the date, who's involved, what needs doing. He acknowledges vague input confidently and never asks "should I save this?" — he just does, then confirms in a line: "Got it — saved the Aurora deadline (Nov 15) and tagged Sarah as lead."
Capture anything#
Quill accepts any input format — meeting notes, pasted docs, quick thoughts, bullet points — and extracts the structure himself. From one dump he'll separate out decisions, deadlines (with dates in a real calendar format), action items (owner, the ask, the counterparty, and why), and the people and systems/projects involved, tagging each so it surfaces in the right views later. Dates and names are pulled automatically.
One item, never duplicated#
The discipline that makes the memory trustworthy: each deadline, task, decision or fact exists as exactly one memory that Quill keeps current. Before saving something that might already exist he searches first; if it's the same underlying item he updates it in place, and when work is finished he marks it done (so it drops off deadline boards but stays searchable as history) rather than rewriting the note. He'll also find and merge accidental duplicates on request.
He writes every field to stand alone on a board:
"Follow up due"
"Follow up with Maya — staging DB permissions for Tomás"
Saving links#
When a message is essentially a URL or a bare domain, Quill files it onto your Links board — it auto-fetches the page title and categorizes it, and you can add a note on why it matters. You don't need to type https; a bare host is enough.
Projects#
When several dated items clearly belong to one initiative — or you tell him something is (or isn't) a project — Quill organizes them on your timeline board. Naming a project lands it as a lane you can hang items and deadlines from, so a stream of notes becomes a tracked initiative.
Recall & search#
Ask Quill about the past and he searches memory before answering — "what did we decide about the ledger", "what's due this week", "what do we know about the budget freeze". He replies directly, leading with the note: "From your notes: …". Dated items also roll up into upcoming-deadline and overdue views.
Recall by meaning#
Quill's recall goes well beyond keyword search. He can match your question against the meaning of every note, so a memory surfaces even when it shares no words with what you asked. When you want the full picture of a topic he pulls a diverse set that covers distinct facts rather than paraphrases of the single best hit, and his deepest recall follows connections through a shared person or project to assemble an answer from evidence that isn't worded like the query at all.
Crucially, he checks a calibrated "do I actually have this?" signal before answering — so low confidence means he tells you he doesn't have it, instead of guessing.
Your live lists#
Quill maintains ready-made views over everything he's captured:
- Open action items — the team's live to-do list, newest first.
- Decisions log — every decision on record, for a "what did we decide about X" review.
- Overdue items — open items whose date has passed, good candidates to chase or close.
- People & tag indexes — everyone who appears across the notes (most-mentioned first) and every tag in use, plus the "everything about Dana" view.
- Timeline & digest — a chronological walk through recent notes, and a "state of the notes" digest: totals, category mix, open items, overdue count, upcoming dates, top people and tags.
The knowledge graph#
Every note lives in a typed knowledge graph — linked to the people, projects and other notes it relates to, with the relationship named (an action that mitigates a risk, a note that follows another). That's what lets Quill answer "how are these connected" with a real chain, and lets Sage trace connections across your whole world.
Beyond the links you imply, Quill also notices ties nobody drew — memories that keep getting recalled together. His "surprising connections" sweep surfaces the genuine huh, these two keep coming up together pairs, and he can roll the whole corpus up into its natural themes.
Consolidation & health#
Like a memory that sleeps, Quill runs a consolidation pass — abstracting recurring episodes into durable schemas and pruning weak, noisy links. It normally runs overnight, but you can trigger it after a big import. He can also tell you which memories are going cold (at risk of slipping out of recall) so you can reinforce, update, or prune the ones that are truly obsolete.
Google Drive#
With Google connected, Quill reaches your Drive — read-only. He searches by keyword across file names and full text, browses folders like you would, reads a single file (Docs come back as text, Sheets as CSV, Word and PDFs are extracted), and can download a file to your machine when you need it locally.
Company knowledge base#
Quill can search your company knowledge base through Google Vertex AI Search — a read-only window across Confluence, Slack, Google Drive, Gmail, Calendar and announcement corpora at once, or narrowed to one source. It's how "what does the company already know about X" gets answered from the real corpus rather than guesswork. He also connects to Notion when you link it, so your workspace pages are in reach too.
Calendar & deadlines#
Quill separates two kinds of time: the deadlines you saved to memory (the migration date, "follow up with Maya") and your real calendar synced from your Mac (actual meetings). He reads both, so "what's due this week" pulls from your notes and "am I free Thursday" checks your lived schedule.
Watches, studios & lessons#
Quill rounds out the team's shared toolkit: put a data pull on the Night Shift watchlist so it's re-checked and you're alerted on a material change; jump into the right studio with a one-click chip; and correct him — "always keep the ticket key", "file people under their full name" — and he records it as a durable lesson that changes how the team works from then on.