Filing what you drop
A proposal for review — after Snoopy reads what you dropped, it files it onto the right pages, tells you what it did, and every line it wrote carries a chip that opens the exact spot it came from.
Today, after Snoopy reads a file, that is where it ends. The file is searchable, but nothing on any page changed — the next person still has to know the file exists to find it.
This proposal makes one promise: whatever you drop, Snoopy files it onto the right pages — a short, readable summary where one is worth having, a line on the pages it concerns, and every line it writes carries a chip that opens the exact spot it came from: the page of the file, or the message in the chat. If it is not sure which page, it asks in one line. If it cannot file it, it says why. And a page never becomes a dumping ground: it reads like something a person wrote, with the sources tucked into the sentences, the way a wiki does.
Read it as a script.
How pages are organised
Every page belongs to one of five collections, or to none (a plain page — a topic, a how-we-do- things, anything a person names). Five is the starting set; the team can add more later, and the filing rules follow whatever collections exist.
| Collection | What it is | Sections the agent files under |
|---|---|---|
| Company | A customer, supplier, or partner | Overview · Current status · People · Projects · Meetings · Documents |
| Person | Anyone the team works with, inside or outside | Overview · Working with · Meetings · Notes |
| Project | Any bounded effort — a deal, a pilot, a launch, a product | Overview · Current status · Decisions · People · Meetings · Documents |
| Meeting | One meeting, from its notes, transcript, or recording | Attendees · Summary · Decisions · Actions |
| Document | Anything else dropped that is worth its own page — a report, a long article, a proposal | Summary · Key points · Related |
| Plain page | A topic, a way of working, an idea — whatever a person names | free-form |
A section only appears once it has something in it. A new company page with one quote on it has an Overview line and a Documents line, not six empty headings.
Two things are deliberately not collections. A decision is a line under Decisions on the project or meeting page — a page per decision would be a filing card, not a page. A topic is a plain page; the agent never invents one on its own.
What gets its own page, and what gets a line
The agent makes a summary page (a Meeting or a Document) when the source carries more than a line or two worth keeping, or when it touches more than one page — a meeting nearly always does. A single quote, a contract, a company profile usually do not: they become one line on the page they are about, with the chip on that line. The examples below are the guide; there is no rule about line counts.
It makes a Company, Person, or Project page when the source is about them — or when they took part: a meeting's attendees each get a page. A name that merely passes by in the text does not; it stays as text, and earns a page the second time it appears, when the agent finds the earlier mention. Extraction starts simple — the attendees, and the people, companies and projects the source is about — and is written so it can be improved later without the pages changing shape.
A fact is written once, on the page it is most about; the other page shows it as a backlink. "Priya — point of contact from October" is written on Acme Corp under People, and Priya's page lists Acme Corp among its backlinks. The meeting page names its attendees, so each attendee's page shows the meeting as a backlink without a Meetings line ever being written on it.
The five outcomes
Every drop lands in exactly one of these, after the reading step you already know.
1 · Meeting notes, about pages that already exist
Made a meeting page, Acme pilot kickoff · 14 Aug — launch 15 Sep agreed, three success measures, four actions — and noted it on Acme Corp and Acme pilot. Tap any of them to check, or tell me if something's wrong.
2 · A quote for a company that has no page yet
There was no page for them, so I made Ferrous Supply Co and noted the quote on it — warehouse racking, ฿184,000, valid until 30 Sep. Rename the page if you'd call them something else.
3 · Two pages could be the right one
Which Acme is this — Acme Corp (logistics) or Acme Studio (design)? Or a new company? Reply to this message with the one you mean and I'll file it.
4 · A name it reads as one page, with a hedge
Noted on Acme Corp — renewal terms, 12 months from 1 Dec, 8% uplift. I read "Acme" as Acme Corp; say if it's not.
5 · It is already on the page
Nothing new for Acme pilot — the launch date and the success measures are already there from the kickoff notes.
6 · Nothing worth filing
7 · Dropped in a private channel or a DM
I don't file from a private channel — pages are shared with the whole workspace. It's kept and searchable here; drop it in a shared channel if it should be on a page.
8 · A note you ask it to file
9 · An ordinary message
10 · The same file, dropped again — or a newer version of it
11 · You correct it
12 · Several files at once
• Q3-expenses.pdf — read all 10 pages, filed as Q3 2026 expenses
• Acme-pilot-kickoff.pdf — read all 6 pages, filed as Acme pilot kickoff · 14 Aug and noted on Acme Corp
• payroll.pdf — needs a password, not filed
Can you re-save payroll unlocked?
13 · A name that only passes by
14 · What the pages look like afterwards
This is the part we most want a reaction to. Two pages after case 1. A page reads like an ordinary document — headings, bullets, a table where one fits — with two kinds of chip inline: a page chip (links to another page — this already exists) and a source chip (opens the exact spot in the file or message the line came from — new). The source chip is a compact marker; its locator — the file and the page, or the channel and the day — shows on hover.
Attendees
- Priya and Somchai, from Acme Corp 📄
- Vee and Turbo, for us 📄
Summary
- Kickoff for the Acme pilot — scope confirmed as the Bangkok warehouse only 📄
- Launch agreed for 15 September 📄
Decisions
- Three success measures 📄 — on-time delivery above 95%, damage rate under 0.5%, a signed renewal by December
Actions
- Vee to send the SLA draft by 5 Sep 📄
- Priya to confirm warehouse access 📄
Overview
- Logistics company, Bangkok. Our pilot customer since August 📄
Current status
- Pilot launching 15 Sep — see Acme pilot
- Opening a second logistics office in Bangkok 🔗
People
- Priya — point of contact from October 💬
Meetings
- 14 Aug — Acme pilot kickoff · 14 Aug: launch date and success measures agreed
Documents
| Document | What it says |
|---|---|
| Renewal terms 📄 | 12 months from 1 Dec, 8% uplift |
The chip sits in the sentence, like a footnote you can tap. It is a small marker; hovering it — or tapping it on a phone — shows where the line came from: the file and the page, or the channel and the day. Tapping opens that spot. Nothing is hidden behind a "Sources" tab; the sources are the page. This is deliberately the Obsidian / wiki feel rather than a form with fields.
Notice the two kinds of line on Acme Corp. The Meetings line points at a page (there was a lot to keep, so the meeting got one); the Documents line points straight at the file (a four-page contract is one line, so the chip goes on the line). The Overview line came from the meeting notes, so it carries a file chip too.
Two choices you may disagree with: pages use ordinary headings, bullets and the occasional small table — written like a normal document, with a heading appearing only once it has content; and the agent only adds to a page — it never rewrites a line a person wrote, and never deletes. A page can therefore carry an out-of-date line next to a newer one. Keeping a page current is a later tidy-up: an agent, on request ("tidy the Acme page") or on a schedule, proposes a rewrite of a page that keeps every chip and every line a person wrote, and it applies only if nothing is lost — otherwise it asks. The chips are what make that safe to automate.
What the agent keeps, even when you never look
Every filing decision — what it would change, on which pages, from which spot in the source, how sure it was, and what happened (filed, asked, nothing new, refused) — is kept. Not on the page, not in the chat: underneath, so that later you can ask "why is this line here?" and get the file and the page it came from, and so that we can measure how often it filed wrongly, asked when it did not need to, or missed something. This proposal does not add a screen for that; it only promises the record exists from the first filing onward.
What we would like you to react to
What we heard, and what changed
- The five collections — kept. Company · Person · Project · Meeting · Document, plus plain pages.
- Page or line (cases 1, 2) — kept. A meeting gets a page; a quote or a contract gets a line with a chip.
- The confirmation line (case 1) — kept. It names the pages and what was added, and the names are tappable.
- The page afterwards (section 14) — changed. Headings, bullets, and a table where one fits, written like a normal document.
- Sources inline, never hidden — changed. Still inline, but the chip is now a compact icon; the file and page show on hover, or on a tap on mobile.
- The hedge (case 4) and who gets a page (case 13) — changed in part. The hedge stays and a passing name still gets no page, but a meeting's attendees now do; and a fact is written once, on the page it is most about, with the other page showing it as a backlink.
- Adding only, never rewriting — kept for a first version, with a tidy-up pass noted as a later story.
- Notes filed only when asked (case 8) and "nothing new" / "nothing worth filing" said out loud (cases 5, 6) — kept.
Answered by the owner (2026-08-29)
- Reply-and-mention as the first-version way to answer a question or correct a filing (cases 3 and 11) — accepted for now; the plain follow-on message is a later story.
- The compact chip — hover on desktop, tap on mobile — accepted; every source chip is compact, none stays expanded.
Not in this proposal, named so it is not assumed: a question card with buttons (case 3 is plain text on purpose); answering a question with a plain next message, no reply and no mention (case 3 needs reply-and-mention for now); a "Needs your input" list of open questions; remembering corrections as lessons; rewriting a page to keep it current; the team adding its own collections (the rules are written to allow it; the control comes later); a private knowledge space; searching old chat messages; receipts (they keep their own path); and any admin "why did it decide that" screen. Each is its own later proposal. Also changing: the agent stops making the separate "Reference" and "Topic" entries it makes today — pages with chips replace them.
Reading what you drop
A proposal for review — what Snoopy says back when you drop a file or a link, in every case it can hit.
Filing what you drop (v2.1)
The filing proposal after Vee's review and the design session that followed — page links instead of pills, no hedging, pages that update like a wiki, and no source marker on the page at all, because the trace is kept underneath where the agent reads it and you never have to.