Ingest
Reach for Ingest when a call, meeting or document holds something the base will need later, and you don't want a second file for a person or account that already has one.
- A call or transcript just ended. Ingest keeps the decisions, commitments and exact quotes, with each speaker named.
- A meeting reached decisions that live nowhere else. Ingest keeps them, along with the questions the meeting left open.
- A document makes an argument you will need again. Ingest keeps its thesis and the evidence behind it.
- A person or concept already has a record. Ingest adds a dated entry to it.
Ingest works only from the text you give it, so a source that isn't in front of it can't be filed.
Most of what a team learns never reaches the place someone will look. It sits in a transcript, a note or a thread nobody will search. Ingest turns that material into structured items our systems can find later.
It sorts the source by type first, because the type decides what's kept. A call gives up its decisions, commitments and exact quotes, with each speaker named, and a meeting gives up its decisions and open questions. A document gives up its thesis and evidence, but notes give up only their ideas. A conversation summary gives up only what you confirm, so Ingest never invents a decision the source doesn't hold.
Two Zones In Every Item
Each item has a compiled truth on top, one to three sentences saying what the base believes now, and a timeline below it. The top gets rewritten when the belief changes. The timeline is dated, newest first, and it only grows, so we can always check it against the exact words said. The old belief stays in the timeline, and we can still check it.
Search Before You Write
Before writing, Ingest searches the base for every person and concept the source names. A match gets a new dated entry, never a second file. If two records already exist for one person, Ingest stops and reports the duplicate rather than merging or adding a third.
A person with no record is never created on its own judgment. It asks by name first, and it creates the record only after you say yes.
Links, Tags And Folders
Every new item links to three or more real items, or to a proposed name still waiting for an answer. If an item can't reach three links, Ingest says so and asks whether to hold it. Each item goes into one folder, chosen by its domain.
| Domain | Folder |
|---|---|
| technical | technical/ |
| business | business/ |
| gtm | gtm/ |
| methodology | methodology/ |
| people | people/ |
| accounts | accounts/ |
| uncertain | uncertain/ |
Anything nobody can place goes to uncertain. Existing folder names in your base win. Tags come from your tag list, and any tag that isn't on it gets flagged.
Expiry Only For Time-Bound Facts
Ingest suggests a valid_until date for content with a known expiry, such as an event, a deadline or a quarter. You confirm the date before it's set, and standing decisions, account records and person records get no expiry, because they stay true until someone changes them. A dated fact about one of them, such as a renewal, gets its own item that carries the date.
You Approve Every Save
Ingest shows the full save plan before it writes a single file. The plan lists every path, every appended entry, every change to a compiled truth, every name waiting for an answer and every expiry suggestion. You can change any line first. After your yes, Ingest writes the files, opens each one to confirm its links point at real items, and reports the counts with a total, such as 5 items (2 new, 3 appends).
Where It Runs
Ingest runs in Claude Code, in Codex, or in ChatGPT as a custom GPT. It reads your base location and save rules from your client profile, so the Context OS setup comes first. If the profile has no Ingest section, it says so once and asks before every save.
What It Looks Like When It Works
On a Monday after a busy week, the account record opens with one current summary at the top, and the call quotes sit below it in date order. The buyer a rep met last Thursday has one record, not two.