40× fewer tokens: wrap Markdown in SQLite

Source: https://www.withnative.ai/research-and-posts/markdown-context-benchmark

Research preview

Tokens per fully correct answer

- Cached input

- Uncached input

- Reasoning

- Output

**TL;DR:**

- **Agents do better with SQLite:** 97% fewer failed trials for a fixed 1M input-token budget

- **Token spend gets slashed:** 40× fewer tokens, ~20× lower modelled token bills per fully correct answer

- **It's faster, not slower:** median answers in 1/6 of the time versus Markdown-based grep

Jump to the graphs, see the repo or read on for the philosophy.

Read as Markdown or plain text, including chart summary data.

Introduction

Open-sourcing our context efficiency research

We're opening a research preview for a context engineering architecture that can make your Markdown vault 40× more token-efficient on workloads like the one tested here.

Our hope is that you will be able to:

- **Get more from your AI agents.** Every AI subscription goes further with token-efficient context.

- **Verify our research for yourself.** Run benchmarks on your own data and on your own machine.

- **Discover new Markdown superpowers.** Build realtime collaboration and apps over fast, efficient Markdown context.

We owe much to open technology and ideas: Markdown, SQLite and MCP; plus local-first, malleable and participative software. Our core engine is already open-source, and we'll be adding more once we're out of research preview.

In this post, we share our motivation, the high-level architecture, our early evaluation results and some of our vision for the future.

Background

Context sovereignty and human agency

Native is a research lab building for **a civilisation of many authors**. Our focus is infrastructure and products for **distributed ambition, agency and abundance**.

Our first mission is **context sovereignty**: making context ownership **easy, powerful and delightful** for people, companies and communities, so it can be a _non-principled default_.

Our research preview brings together more token-efficient retrieval, realtime collaboration and a path to keeping your working context outside SaaS walled gardens.

But first: why context sovereignty, and why Markdown vaults?

Context is an ownable asset in the age of AI

Your company's value compounds in your context

We believe context sovereignty is a critical investment for humans and companies.

- **Context is the key****complement****to the technology of AI.** Intelligence is _general_, and context is _specific_. We believe that humanity's good lies in the _blend_ of the two.

- **Context can be sold as training data.** The growth of Mercor, Scale and Surge AI shows the commercial demand for specialised human context.

- **Context is an enduring, defensible asset if it is owned.** AI is commoditising vast professional expertise. But, if you own your context, its value compounds.

- **Context creation is rapidly accelerated by AI.** AI agents explore, learn and output a huge amount. That is all _new_ context, and reading it is becoming a full-time job.

- **Context ownership helps you respond to geopolitical risk.** AI is a rapidly moving technology, with unpredictable changes in access.

- **Context becomes a bottleneck as intelligence gets cheaper.**Epoch AI’s research tracks the falling price of intelligence; context remains specific to the people and organisations that create it.

AI labs are especially dangerous context owners

There are some places where it's _especially_ dangerous for your context to accrue -- and we think that AI labs are top of the list.

- If an AI lab owns your context, they have the power to dictate how it's used.

- This means that they can make themselves a monopoly provider of your intelligence.

- So, now the AI lab owns your context _and_ is your monopoly provider of intelligence.

- If value is intelligence plus context, and you rent access to both from the labs...

- ... yikes?

Not all 'ownership' delivers sovereignty

We think it's clear that your context needs to be independent of the AI labs. But we think there's also a very strong case for it being independent of most digital providers.

A company which hosts your context will probably claim that you own the data. But digital 'ownership' often turns out to be a surprisingly revocable and weak access license.

Here's some questions to explore around context sovereignty.

- Can I access it whilst I'm offline?

- Can I easily use it with any AI agent that I want?

- What happens if an AI lab buys this company?

This deep level of context ownership is what we mean by **context sovereignty**.

Resisting the context gravity of AI labs Context -- especially team context -- has something akin to _gravitational pull:_ the larger a store of context, the more likely it is to attract further context.

Context gravity

Let's illustrate this with an example. When you're discussing a proposal with your team, there's lots of plausible places to put it: a Google Doc comment, a Slack channel or even old-fashioned email.

So, where do you pick? In most cases, it's "wherever the team normally does this".

This is **context gravity**: new context is more likely to be 'attracted' to places where relevant context already exists, for at least a few reasons:

1. **You're more likely to already be there** when you create new context, since relevant context is collected there 2. **It's more useful to your audience** to store context there, since they 'know where to find it' and can view it next to other relevant background 3. **It's simply 'conforming to social norms'** to store the context where everybody else is storing it

Centralising forces

Today, the AI labs are making a big play for your context.

Products like ChatGPT Space and Claude Artifacts are surfaces that _also_conveniently centralise your working context inside the model lab's ecosystem.

Normally, the logic of context gravity would dampen these surfaces. However, there's some key things which are different now.

- **AI agents can generate work and output at truly inhuman rates.** The written context you generate from a month of AI agents can be larger than years of your Slack conversations.

- **Frontier labs can influence AI agents towards these new surface areas.** OpenAI and Anthropic have the power to prime ChatGPT and Claude towards their centralising surfaces.

- **New surfaces can be more effective for AI agent productivity.**Prominent AI commentators have swung behind the idea of new agent-native workspaces.

This gives the AI labs a powerful context gravity flywheel.

1. Your agents use their surfaces, whether through merit or biased priming; 2. It becomes more convenient for you to use those surfaces to work with your agents; 3. The surfaces accumulate context gravity that pulls in more and more context; 4. All your context ends up centralised and in control of the AI labs.

Making context sovereignty a non-principled default For context sovereignty to win, we believe it needs to be the **non-principled****default.**

In other words, we believe that the most easy, powerful and delightful products should be ones that _just so happen_ to deliver context sovereignty -- at least from a mainstream user perspective.

Why? It's because of what we call the 'Should-Do Gap'.

A 'Should' is **something that a well-informed expert would strongly urge you to do**.

For example, these could all be Shoulds:

- "I _should_ floss" (as most dentists would say)

- "I _should_ set aside more savings" (as most financial experts would say)

- "I _should_ use better passwords" (as most cybersecurity experts would say)

Here's the key thing: **we might know that we****_should_, and we might still not****_do_.**

Our goal isn't "people and communities _know that they should_ have context sovereignty".

Our goal is "people and communities _have_ context sovereignty".

We need to design for adoption.

We see this as a two stage mission:

1. **Make context sovereignty****_better_** -- more easy, powerful and delightful than it currently is 2. **Make context sovereignty****_the_****_best_** -- more easy, powerful and delightful than any alternative

That's what takes us to Markdown.

Building up from Markdown

What makes Markdown great

Folders of Markdown -- often called 'vaults' or 'brains' -- have seen a renaissance in the age of AI, as a way to plug and connect AI to rich context.

We think that Markdown is a _great_ starting point for context sovereignty, for many reasons.

- It's **agent-native**. Markdown is the lingua franca of every major AI agent.

- It's **ownership-friendly**. It's transparent, portable and human-readable.

- It's an **open technology**. The file format spec is released under Creative Commons.

- It's **free from****rate limits**. You, or your AI agents, can make high velocity changes to it.

- There's an **ecosystem**: GitHub, Obsidian and many apps support Markdown.

A well-organised local Markdown vault achieves two complementary goals: **connected context for AI agents**, and **context sovereignty for humans and teams**.

So, our starter question was this: what if _all_ _context_ could sit in that vault?

To do that, we need to reflect a bit on "What is context?".

Different types of context and how teams work

In a knowledge work setting, we see at least three tiers:

- **Work.** The raw 'output' that you create: a document, some slides or a spreadsheet. (As context: "What's the provisional conclusion of our BlueCorp analysis?")

- **Work about work.** Where you track your work: e.g. project and task management. (As context: "What's currently blocked by our BlueCorp analysis work?")

- **Work about 'work about work'.** Where you decide what to work on: e.g. team messaging and meetings. (As context: "Why did we change our mind about Green Inc being a design partner?")

It's very rare for teams to capture all of these in their Markdown vault. Often, these sit in SaaS apps, like Linear, Slack and Attio, for a few reasons:

- **There's a nicer human UX than Markdown editors.** These products are often well-designed, and feel better for humans than editing raw Markdown.

- **They unlock collaborative work better than Markdown.** Your changes are shared without remembering any active sync or data push/pull steps.

- **They need structured data, not just text.** These products often _use_ Markdown content, but need typed, filterable fields to work effectively.

Walled gardens and rate limits

The UX, team collaboration and structured data benefits to SaaS apps correspond, somewhat crudely, to three layers: a frontend UI, a backend server, and a database.

SaaS apps provide a convenient wrapper and packaging for that bundle. But your context is no longer _connected_ or _sovereign_ -- it's fragmented into databases that you don't own or control.

As a tangible example: your context can be put behind a rate limit restriction which these companies can change at any time.

Lots of these SaaS companies have built great products and much better UI/UX experiences than what they replaced.

But what if we could have their ease, power and UX _whilst_ _also_ having the connectedness and sovereignty of a local Markdown vault?

Native: superpowers for connected, sovereign context

We're opening a research preview for Native across web, MCP and CLI.

We've built Native to give superpowers to connected, sovereign context.

- 100%ownership of your context

The best bits of Markdown.

You own your context. It's transparent, portable and readable. You can keep it on your file system, view it in Obsidian and back it up in GitHub.

- 40×fewer tokens than a Markdown wiki

Retrieval superpowers for AI.

Get answers 6× faster, with 30× fewer failed trials at a 1M input-token budget and 40× fewer tokens per fully correct answer, when agents use Native instead of an ordinary Markdown wiki.

- SQL one shared context database

More freedom for you and your team.

Share context in realtime, remix any app you want and unify your workspace around a connected, sovereign database.

Under the hood, the key technical architecture is this:

- **An append-only event log is the source of truth.**It means that everything is auditable, traceable and restorable. This is one of our key architectural bets for the age of agents.

- **The event log projects into SQLite and/or a Markdown vault.** They are two representations of the same stateful context. SQLite is richer, and Markdown is lossier, but you can still have all the Markdown files on your local machine.

- **Agents are expected to query via MCP**, but they can always read the local Markdown or go direct to the SQLite database.

- **You can run this locally or in a cloud.** A shared cloud database supports team context and sharing. You can self-host it in a cloud of your choice, or use ours.

We are preparing to open-source everything that you need to run Native locally, reproduce our benchmark results and run your own private evaluations.

Below, we include some highlights from our research and benchmark results.

Dataset

Our findings are grounded in real-world context

We take our own event log as the base dataset for our research.

- **It covers two months**, from mid-August to mid-October. (Mid-August is when we switched over to a ground-up rewrite of Native.)

- **It's mostly two humans and a few thousand agents** over this time period. One of the humans is part-time over this time period.

- **It contains ~77,000 events**, such as `record.create`, `record.update`, `link.create` and more.

- **It projects into ~11,000 individual records**, i.e. SQLite rows or Markdown files. It's ~120MB of Markdown content in total.

- **It's cross-functional context.** Records represent everything from CRM-like tracking, product backlog tickets and internal messaging.

The underlying event log can be projected into different forms.

We wanted to test the efficacy of different representations. So, we projected the event log into four setups.

1. Native's SQLite MCP Local MCP

A local SQLite database exposed through MCP. Agents write SQL over a discoverable schema, with some convenience tools.

2. Native-to-Markdown Filesystem

Nested folders of Markdown files, with strongly typed frontmatter and a JSON index file.

3. Markdown + wikilinks Filesystem

Nested folders of Markdown files, with wikilink pointers. Similar to a common Obsidian vault.

4. Plain Markdown Filesystem

Nested folders of Markdown files, with mentions of other files by title rather than wikilink pointer.

Why we put MCP in front of SQLite MCP is a priority surface area for us because it means we can support a wide variety of agent harnesses and machine setups.

In retrospect, it would have been interesting to test a direct SQLite setup as well. This honestly did not occur to us until we were writing this blog post.

Further setup details

- These setups are identical on body content and structure wherever it fits the paradigm.

- We make a best-effort to represent lossy setups in a fair, reasonable way. For example, plain Markdown substitutes titles for wikilink mentions.

- _Unfortunately, this setup flatters plain Markdown relative to wikilinks, since we guarantee that the title is the correct, up-to-date title at the point of substitution._

- You can see full details of Native's SQLite MCP and the Native-to-Markdown projection in our GitHub repo.

Trial design

We assess on realistic, everyday work queries

We wanted to test how effective and efficient each representation was for agentic context retrieval and question answering.

To do this, we generated 40 questions, that were all answerable with perfect knowledge and/or recall of the represented company context.

We then tested each setup on the 40 questions, with three independent runs for a total of 120 trials per setup.

Each setup used OpenCode as the harness and DeepSeek v4.1 Flash on High effort for the model.

- Native's SQLite MCP

- Native-to-Markdown

- Markdown + wikilinks

- Plain Markdown

SQL gives agents better search tools

B01 · Question, rephrased

> Is 'company brain leads, permissions later' still our launch message? If not, what replaced it?

| Setup | Tokens | Runtime | Result | | --- | --- | --- | --- | | Native's SQLite MCP | 73k 33.2× fewer | 23 s 8.2× faster | Pass | | Native-to-Markdown | 1.3M 1.9× fewer | 112 s 1.7× faster | Pass | | Markdown + wikilinks | 1.1M | 148 s | Pass | | Plain Markdown | 2.4M | 188 s | Pass |

Native's SQLite MCP

B01-mcp-r1

Pass

Total tokens 73k

Run time 23 s

Tool calls 7

Cached input 60,416

Uncached input 10,807

Reasoning 979

Output 1,107

1. Calls 2–4 search ×1 · query_sql ×2 1. **search**

`{"operation": "search", "arguments": {"query": "company brain leads permissions later", "limit": 20}}` 2. **query_sql**

`SELECT id, type, kind, name, lifecycle, created_at, updated_at, created_at_ms, updated_at_ms FROM records WHERE id IN ('f853ae39-7f4d-446f-9768-0e41c04b632e') OR id LIKE '20c1e2a%'` 3. **query_sql**

`SELECT id, source_id, target_id, relationship, created_at, created_at_ms FROM links WHERE source_id = 'f853ae39-7f4d-446f-9768-0e41c04b632e' OR target_id = 'f853ae39-7f4d-446f-9768…`

2. #### Find the superseding link

Source call 5 · native_sql_read · query_sql

SQL · verbatim

`SELECT l.id, l.source_id, l.target_id, l.relationship, l.created_at FROM links l WHERE l.relationship = 'supersedes' AND (l.target_id IN ('f853ae39-7f4d-446f-9768-0e41c04b632e','20c1e2a4-6e36-4503-b662-4cdcf6027dca') OR l.source_id IN ('f853ae39-7f4d-446f-9768-0e41c04b632e','20c1e2a4-6e36-4503-b662-4cdcf6027dca')) ORDER BY l.created_at`Complete tool input ``` { "operation": "query_sql", "arguments": {

"sql": "SELECT l.id, l.source_id, l.target_id, l.relationship, l.created_at FROM links l WHERE l.relationship = 'supersedes' AND (l.target_id IN ('f853ae39-7f4d-446f-9768-0e41c04b632e','20c1e2a4-6e36-4503-b662-4cdcf6027dca') OR l.source_id IN ('f853ae39-7f4d-446f-9768-0e41c04b632e','20c1e2a4-6e36-4503-b662-4cdcf6027dca')) ORDER BY l.created_at" } } ``` Result excerpt

``` 1 row(s) returned As of content sequence: 76816 id source_id target_id relationship created_at … "lnk:20c1e2a4-6e36-4503-b662-4cdcf6027dca:f853ae39-7f4d-446f-9768-0e41c04b632e:supersedes" "20c1e2a4-6e36-4503-b662-4cdcf6027dca" "f853ae39-7f4d-446f-9768-0e41c04b632e" "supersedes" "2026-10-06T10:39:59.735Z" ``` 3. Call 6 query_sql ×1 1. **query_sql**

`SELECT id, type, kind, name, lifecycle, created_at, updated_at FROM records WHERE id LIKE '0a64a4b%' OR name LIKE '%Launch plan%' OR name LIKE '%Launch message%' ORDER BY created_a…`

4. #### Read both records for the replacement wording

Source call 7 · native_call_executor · get_record

Tool input · complete

``` { "executor": "records_read", "operation": "get_record", "arguments": { "ids": [ "20c1e2a4-6e36-4503-b662-4cdcf6027dca", "f853ae39-7f4d-446f-9768-0e41c04b632e" ] } } ```

Result excerpt

``` Launch message: Native is the open-source alternative to ChatGPT Space (20c1e2a) Resolution/decision …

Body preview (truncated; re-read get_record with ids:["20c1e2a4-6e36-4503-b662-4cdcf6027dca"] or use format:"json" for the full verbatim body): Native is presented as the open-source alternative to ChatGPT Space. This replaces 'company brain' as the lead. ```

Agent answer · excerpt

No. That decision — **"Content theme priority: company brain leads, permissions later"** (f853ae39, Resolution/decision, George Jones) — was superseded on **6 Oct 2026** (supersession link created 2026-10-06T10:39:59Z, before your 16 Oct snapshot).

It was replaced by **"Launch message: Native is the open-source alternative to ChatGPT Space"** (20c1e2a, Resolution/decision, George Jones, 6 Oct 2026), whose note states *"Company brain is no longer the lead message"* — the body says open-source-plus-alternative leads and this *"replaces 'company brain' as the lead."* No further supersedes link pointed at it as of 16 Oct, so that remained the launch message. (A related open item, "Decide how launch messaging handles ownership…" (17727f7), flags the rival-framing as a live tension, but does not replace it.)

Native-to-Markdown

B01-vault-r1

Pass

Total tokens 1.3M

Run time 112 s

Tool calls 33

Cached input 1,157,120

Uncached input 89,309

Reasoning 6,370

Output 3,430

1. Calls 1–17 bash ×7 · glob ×1 · read ×1 1. **bash**

`ls -la /mnt/vault` 2. **glob**

`{"pattern": "/mnt/vault/**"}` 3. **bash**

`ls -la /work; echo ---; ls -la /` 4. **bash**

`ls -la /xdg; echo ---; ls -laR /xdg 2>/dev/null | head -100` 5. **bash**

`ls -laR /mnt/vault` 6. **read**

`{"filePath": "/xdg/data/opencode/tool-output/tool_150c2f457001qZ9O6yXXBlTk8D"}` 7. **bash**

`head -c 300 /mnt/vault/.native/STATUS.md` 8. **bash**

`head -n 1000 /mnt/vault/.native/STATUS.md` 9. **bash**

`grep -rl "company brain" /mnt/vault 2>/dev/null`

2. #### Locate both records by the old wording

Source call 18 · bash

Command · verbatim

`grep -ril "permissions later" /mnt/vault 2>/dev/null` Result excerpt

``` /mnt/vault/.native/state.json /mnt/vault/Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later.md /mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch message_ Native is the open-source alternative to ChatGPT Space.md ``` 3. #### Read the old record's superseded frontmatter

Source call 19 · bash

Command · verbatim

`head -n 200 "/mnt/vault/Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later.md"` Result excerpt

``` "id": "f853ae39-7f4d-446f-9768-0e41c04b632e" "kind": "decision" … "maturity": "superseded" … "superseded": true ``` 4. Calls 20–33 bash ×14 1. **bash**

`head -n 200 "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch message_ Native is the open-source alternative to ChatGPT Space.md"` 2. **bash**

`grep -rln "20c1e2a" /mnt/vault 2>/dev/null` 3. **bash**

`grep -rln "supersedes" /mnt/vault/Native\ HQ/Work/Strategy\ \&\ Planning/Company\ Strategy/Launch 2>/dev/null` 4. **bash**

`which jq python3 sqlite3 2>/dev/null; echo "---"; python3 -c "print('py ok')"` 5. **bash**

`python3 - <<'EOF' import json p='/mnt/vault/.native/state.json' d=json.load(open(p)) print(type(d)) if isinstance(d,dict): for k,v in d.items(): print(k, type(v), (len(v) if hasatt…` 6. **bash**

`python3 - <<'EOF' import json d=json.load(open('/mnt/vault/.native/state.json')) files=d['files'] print('files keys sample', list(files)[:3]) k=list(files)[0] print('sample value t…` 7. **bash**

`python3 - <<'EOF' import json d=json.load(open('/mnt/vault/.native/state.json')) files=d['files'] k='Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissio…` 8. **bash**

`python3 - <<'EOF' import os,re,json,collections root='/mnt/vault' recs=[] for dp,dn,fn in os.walk(root): if '/.native' in dp: continue for f in fn: if not f.endswith('.md'): contin…` 9. **bash**

`python3 - <<'EOF' import os,re,json root='/mnt/vault' out=[] for dp,dn,fn in os.walk(root): if '/.native' in dp: continue for f in fn: if not f.endswith('.md'): continue p=os.path.…` 10. **bash**

`python3 - <<'EOF' import os,re root='/mnt/vault' targets={'20c1e2a4-6e36-4503-b662-4cdcf6027dca':'launchmsg','f853ae39-7f4d-446f-9768-0e41c04b632e':'contentpriority'} for dp,dn,fn …` 11. **bash**

`head -n 80 "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Messaging synthesis of the 8 Oct Richard–George call_ lightly held, agent-generated.md"` 12. **bash**

`head -n 60 "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Reposition withnative.ai homepage and _product around 'ChatGPT Space, made open-source and more powerful'.md…` 13. **bash**

`grep -rl "Product messaging positions Native against today's tools" /mnt/vault --include=*.md 2>/dev/null` 14. **bash**

`head -n 60 "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Product messaging positions Native against today's tools, not against AI labs owning your context.md"`

Agent answer · excerpt

No — it was superseded.

- The content priority **"Content theme priority: company brain leads, permissions later"** (ref f853ae3, Resolution / kind decision, last updated 2026-10-06) is marked `maturity: superseded`, `superseded: true`.

- It was replaced by **"Launch message: Native is the open-source alternative to ChatGPT Space"** (ref 20c1e2a, Resolution / kind decision, decided 2026-10-06), which carries a `supersedes` link to f853ae3 and states it "replaces 'company brain' as the lead."

- Nothing later supersedes 20c1e2a. The 8 Oct decision **"Product messaging positions Native against today's tools, not against AI labs owning your context"** (59f0d1b) only `relates_to` it, and the 9 Oct "Messaging synthesis" is an exploratory note that "replaces no earlier record."

So as at the snapshot the launch message is: **Native is the open-source alternative to ChatGPT Space.**

Markdown + wikilinks

B01-plain-r1

Pass

Total tokens 1.1M

Run time 148 s

Tool calls 31

Cached input 981,888

Uncached input 90,367

Reasoning 12,675

Output 2,953

1. Calls 1–16 bash ×7 1. **bash**

`ls -la /mnt/vault` 2. **bash**

`ls -la /work; pwd; ls -la` 3. **bash**

`ls -la /tmp/opencode; echo ---; ls -la /; echo ---; mount | grep -i vault` 4. **bash**

`ls -la "/mnt/vault/Native HQ"` 5. **bash**

`for d in "Agent instructions" "Attention" "Control Centre" "George" "Library" "Morning Edition" "My agent context" "System" "Work"; do echo "=== $d ==="; ls -la "/mnt/vault/Native …` 6. **bash**

`grep -rIl -e "company brain" -e "permissions later" -e "launch message" "/mnt/vault/Native HQ" 2>/dev/null` 7. **bash**

`grep -n "^" "/mnt/vault/Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later.md"`

2. #### Follow the old wording to the new message

Source call 17 · bash

Command · verbatim

`grep -rn "permissions later" "/mnt/vault/Native HQ" 2>/dev/null` Result excerpt

``` /mnt/vault/Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later.md:2:# Content theme priority: company brain leads, permissions later

/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch message_ Native is the open-source alternative to ChatGPT Space.md:20:- [[Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later|Content theme priority: company brain leads, permissions later]] ``` 3. #### Read the replacement note

Source call 18 · bash

Command · verbatim

`grep -n "^" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch message_ Native is the open-source alternative to ChatGPT Space.md"` Result excerpt

`2:Native is presented as the open-source alternative to ChatGPT Space. This replaces 'company brain' as the lead.` 4. Calls 19–31 bash ×13 1. **bash**

`find /mnt/vault -type f ! -name "*.md" 2>/dev/null | head -100; echo "=== dir sizes ==="; find /mnt/vault -type d 2>/dev/null | wc -l; echo "=== Messages ==="; ls -la /mnt/vault/Me…` 2. **bash**

`ls -la "/mnt/vault/Native HQ/Directory"; echo "=== IWE head ==="; wc -l "/mnt/vault/Native HQ/Directory/IWE.md"; grep -n "^" "/mnt/vault/Native HQ/Directory/IWE.md" | head -80` 3. **bash**

`grep -rn -i -e "kind: *decision" -e "type: *Resolution" -e "lifecycle" -e "status: *archived" -e "status: *deleted" "/mnt/vault/Native HQ" 2>/dev/null | head -50` 4. **bash**

`ls -la "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch"; echo "=== Positioning ==="; ls -la "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging"; ec…` 5. **bash**

`for f in "Work/Marketing/Native_ content and launch strategy.md" "Work/Strategy & Planning/Company Strategy/Launch/We know which message makes people get it.md" "Work/Strategy & Pl…` 6. **bash**

`grep -rn -i "launch message" "/mnt/vault/Native HQ" 2>/dev/null` 7. **bash**

`grep -rn -i -e "content theme priority" -e "company brain leads" -e "permissions later" "/mnt/vault/Native HQ" 2>/dev/null` 8. **bash**

`for f in "Work/Strategy & Planning/Company Strategy/Launch/Launch plan_ a big-bang launch that gets people talking.md" "Work/Strategy & Planning/Company Strategy/Launch/Native's pu…` 9. **bash**

`grep -rn -i -e "supersede" -e "replaces " -e "replaced " -e "no longer the lead" -e "new launch message" "/mnt/vault/Native HQ/Work/Marketing" "/mnt/vault/Native HQ/Work/Strategy &…` 10. **bash**

`grep -rln -e "16 Oct 2026" -e "17 Oct 2026" -e "18 Oct 2026" -e "15 Oct 2026" "/mnt/vault/Native HQ" 2>/dev/null | head -50` 11. **bash**

`for f in "Work/Marketing/Positioning & Messaging/Product messaging positions Native against today's tools, not against AI labs owning your context.md" "Work/Strategy & Planning/Com…` 12. **bash**

`echo "### Lean Canvas head"; grep -n "^" "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Native's hypotheses on the Lean Canvas, with the evidence behind each box.md" …` 13. **bash**

`grep -n "^" "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Native's hypotheses on the Lean Canvas, with the evidence behind each box.md"`

Agent answer · excerpt

No. As of 16 Oct 2026 11:02 UTC the launch lead is **"Native is the open-source alternative to ChatGPT Space"** — the homepage/README line "ChatGPT Space, made open-source and more powerful".

Evidence:

- **Launch message: Native is the open-source alternative to ChatGPT Space** — "This replaces 'company brain' as the lead"; lead line is "open source plus alternative", lock-in argued in the body, "why not markdown files?" answered up front.

- **Native's hypotheses on the Lean Canvas, with the evidence behind each box** — set 1 "Company brain" (July–Sept) is marked "Replaced as the lead on 6 October by [Launch message: Native is the open-source alternative to ChatGPT Space]"; the promise for the open-source set is "Own your context. Self-host it, or let us run it."

- **Decide how launch messaging handles ownership, given it tested poorly as a lead in July** — "Answered, 6 October 2026: Argue against lock-in rather than for ownership."

- **Reposition withnative.ai homepage and /product around 'ChatGPT Space, made open-source and more powerful'** (6 Oct) confirms the site/README shift.

Caveat on the distinction: the record you're quoting, **Content theme priority: company brain leads, permissions later** (Status: agreed), is a content-theme ordering, not the launch lead — it still stands, and permissions remain "later". The thing that changed is the launch message, not that priority list. The lead has not changed again since: 13 Oct records (e.g. **Native's fifteen framings as hypotheses…**) still cite the ChatGPT Space message as the launch line, and the Lean Canvas's "Open" section still asks which set leads the *next founder email*, so "mission control" (13 Oct) has not replaced it.

Plain Markdown

B01-raw-r1

Pass

Total tokens 2.4M

Run time 188 s

Tool calls 47

Cached input 2,283,776

Uncached input 141,555

Reasoning 6,693

Output 3,722

1. Calls 1–8 bash ×5 1. **bash**

`ls -la /mnt/vault` 2. **bash**

`find /mnt/vault -maxdepth 2 -type f | head -100` 3. **bash**

`find /mnt/vault -type f | sort` 4. **bash**

`grep -ril "company brain" /mnt/vault | head -50; echo ---; grep -ril "permissions later" /mnt/vault | head -50; echo ---; grep -ril "launch message" /mnt/vault | head -50` 5. **bash**

`ls -la "/mnt/vault/Native HQ/Work/Marketing"; echo ---; find "/mnt/vault/Native HQ/Work/Marketing" -maxdepth 2 -type f | sort`

2. #### Read the old record's agreed status

Source call 11 · bash

Command · verbatim

`grep -n "" "/mnt/vault/Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later.md"` Result excerpt

``` 2:# Content theme priority: company brain leads, permissions later 3: 4:Status: agreed. ``` 3. Calls 12–15 bash ×4 1. **bash**

`grep -rn -i "company brain leads\|permissions later\|content theme priority\|content priority" /mnt/vault --include=*.md | head -50` 2. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Decide how launch messaging handles ownership, given it tested poorly as a lead in July.md"` 3. **bash**

`grep -rn -i "launch message\|launch messaging\|open-source alternative to ChatGPT Space\|company brain" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch" --in…` 4. **bash**

`find "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch" -type f | sort`

4. #### Read the new message's replacement line

Source call 16 · bash

Command · verbatim

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch message_ Native is the open-source alternative to ChatGPT Space.md"` Result excerpt

`2:Native is presented as the open-source alternative to ChatGPT Space. This replaces 'company brain' as the lead.` 5. Calls 17–47 bash ×31 1. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Until early December 2026, find and onboard users among EF and YC founders; public launch and scal…` 2. **bash**

`grep -rn -i "^kind:\|^type:\|lifecycle\|resolution" /mnt/vault --include=*.md | head -80` 3. **bash**

`grep -rln -i "open-source alternative to ChatGPT Space" /mnt/vault | sort` 4. **bash**

`grep -rln -i "16 Oct\|16 October\|2026-10-16" "/mnt/vault/Native HQ/Work" "/mnt/vault/Messages" | sort | head -100` 5. **bash**

`grep -rn -i "launch message\|launch messaging\|open-source alternative\|company brain" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Founder push, 12 Oct –…` 6. **bash**

`grep -rln -i "company brain" "/mnt/vault/Native HQ/Work/Strategy & Planning" --include=*.md | sort` 8. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Native_ detailed launch brief for Richard's agents.md" | sed -n '1,80p;300,340p'` 10. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Product messaging positions Native against today's tools, not against AI labs owning your context.md"; echo …` 13. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch plan_ a big-bang launch that gets people talking.md" | sed -n '55,100p'` 15. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Native launch_ build momentum with founder teams before the main release.md" | sed -n '1,120p'` 16. **bash**

`find /mnt/vault -type f -iname "*content*priority*" -o -type f -iname "*theme*" | sort | head -50` 17. **bash**

`grep -rn -i "content priority\|content theme\|priority.*company brain\|company brain.*permissions" /mnt/vault --include=*.md | head -100` 18. **bash**

`stat -c '%y %n' "/mnt/vault/Native HQ/Work/Marketing/Content theme priority_ company brain leads, permissions later.md" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strat…` 19. **bash**

`grep -rn -i "launch message" /mnt/vault --include=*.md | cut -d: -f1 | sort -u` 21. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Sales & Partnerships/Outbound/Native's fifteen framings as hypotheses, and a 25-minute founder call that tests them (13 Oct 2026).md" | sed -n…` 22. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Founder push, 12 Oct – 8 Nov 2026/Ten founder alpha testers by 8 November_ the four-week plan.md" …` 23. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Marketing/Positioning & Messaging/Native's hypotheses on the Lean Canvas, with the evidence behind each box.md" | sed -n '1,70p'` 24. **bash**

`grep -rn "11:02\|11:02 UTC\|16 Oct 2026\|16 October 2026" /mnt/vault --include=*.md | head -100` 25. **bash**

`find /mnt/vault/Native HQ -type f -newermt "2026-10-15" | head -5; grep -rln "Content theme\|content theme" /mnt/vault/Native HQ --include=*.md` 26. **bash**

`find "/mnt/vault/Native HQ" -maxdepth 2 -type d | sort` 27. **bash**

`grep -rln -i "decision log\|decision register\|decisions log\|log of decisions" /mnt/vault/Native HQ --include=*.md | head -50` 28. **bash**

`find "/mnt/vault/Native HQ/Control Centre" "/mnt/vault/Native HQ/Directory" -type f | sort | head -100` 29. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Launch.md" | sed -n '1,220p'` 30. **bash**

Agent answer · excerpt

No. The old priority was overtaken by the 6 Oct 2026 decision **“Launch message: Native is the open-source alternative to ChatGPT Space”**, which explicitly says it “replaces ‘company brain’ as the lead.” The 13 Oct **Competitor watch** still calls that Native’s launch line; the 8 Oct decision to position against today’s tools shifted the comparator, not the launch message itself.

The runs agree on the launch message but add different qualifications about the old content priority and later positioning notes. Those interpretations remain in their saved answers.

About these excerpts **Original question:** Our content priority was 'company brain leads, permissions later'. Is that still our launch message? If not, what replaced it?

Selected successful calls from the four runs below, recorded in October 2026 against the workspace snapshot of 16 October 2026, 11:02 UTC. They are historical examples, not statements of our current plans.

Native calls show the complete tool input; shell calls show the complete command field. Results and agent answers are excerpts; “…” marks cuts between passages. Decoded result fields are labelled below. The abbreviated sequence shows successful calls in source order, with whitespace-normalized input previews cut at 180 characters. Failed calls, including harness and wiring errors, are omitted from the illustration. Expand the call ranges to inspect the intervening calls. Only the selected calls show results; portions of those results are omitted. Each card preserves its run’s source order; the cards do not imply a synchronized sequence. Strategy notes and explanations are editorial.

Headlines use this run’s saved score and metrics, not a three-run median. “Pass” requires full credit; partial answers count as “Fail”. Total tokens add cached input, uncached input (including cache writes), reasoning and output. Counts accumulate across the entire attempt, rather than measure peak context or just these excerpts. Seconds are recorded attempt wall time, excluding warm-up; token totals and tool-call counts also exclude warm-up. Tool-call counts include failed calls; each shell invocation counts as one call even when it runs multiple commands.

- `B01-mcp-r1` · source calls 5, 7 · batch `full-2026-10-18`

- `B01-vault-r1` · source calls 18, 19 · batch `full-2026-10-18`

- `B01-plain-r1` · source calls 17, 18 · batch `full-2026-10-18`

- `B01-raw-r1` · source calls 11, 16 · batch `full-raw-2026-10-20`

F07 · Question, rephrased

> Where does Diogo Almeida work, and what is his outreach stage?

| Setup | Tokens | Runtime | Result | | --- | --- | --- | --- | | Native's SQLite MCP | 217k 5× fewer | 30 s 5× faster | Pass | | Native-to-Markdown | 276k 3.9× fewer | 65 s 2.3× faster | Pass | | Markdown + wikilinks | 874k | 94 s | Pass | | Plain Markdown | 1.1M | 150 s | Pass |

Native's SQLite MCP

F07-mcp-r1

Pass

Total tokens 217k

Run time 30 s

Tool calls 13

Cached input 182,784

Uncached input 31,868

Reasoning 1,401

Output 1,426

1. Calls 1–3 native_bootstrap ×1 · search ×1 · get_record ×1 1. **native_bootstrap**

`{}` 2. **search**

`{"operation": "search", "arguments": {"query": "Diogo Almeida"}}` 3. **get_record**

`{"executor": "records_read", "operation": "get_record", "arguments": {"ids": ["a897df16-4599-454f-ac82-284e7f574dcf"]}, "run_key": "breeze-chiffon-4c9jeq"}`

2. #### Read the person's org, role and stage facets

Source call 4 · native_sql_read · query_sql

SQL · verbatim

`SELECT id, record_id, key, value, value_num, vocab_ref, created_at FROM facet_values WHERE record_id = 'a897df16-4599-454f-ac82-284e7f574dcf' ORDER BY key`Complete tool input ``` { "operation": "query_sql", "arguments": { "sql": "SELECT id, record_id, key, value, value_num, vocab_ref, created_at FROM facet_values WHERE record_id = 'a897df16-4599-454f-ac82-284e7f574dcf' ORDER BY key" }, "run_key": "breeze-chiffon-4c9jeq" } ``` Result excerpt

``` "fv:a897df16-4599-454f-ac82-284e7f574dcf:org" "a897df16-4599-454f-ac82-284e7f574dcf" "org" "TypeSafe AI" null null "2026-09-15T20:39:43.723Z" "fv:a897df16-4599-454f-ac82-284e7f574dcf:role" "a897df16-4599-454f-ac82-284e7f574dcf" "role" "Co-founder & CEO" null null "2026-09-15T20:39:43.808Z" … "fv:a897df16-4599-454f-ac82-284e7f574dcf:stage" "a897df16-4599-454f-ac82-284e7f574dcf" "stage" "not yet contacted" null null "2026-09-15T20:39:43.877Z" ``` 3. Calls 5–8 search ×2 · get_record ×1 1. **search**

`{"arguments": {"query": "TypeSafe outreach"}, "operation": "search", "run_key": "breeze-chiffon-4c9jeq"}` 2. **search**

`{"arguments": {"query": "Diogo contacted"}, "operation": "search", "run_key": "breeze-chiffon-4c9jeq"}` 3. **get_record**

`{"arguments": {"ids": ["22cda333-a0eb-483b-9d6a-d1d9c416b449"]}, "executor": "records_read", "operation": "get_record", "run_key": "breeze-chiffon-4c9jeq"}`

4. #### Open the company record to separate it from the person

Source call 9 · native_call_executor · get_record

Tool input · complete

``` { "arguments": { "ids": [ "778ac6a6-14e8-48c3-8096-5ab089e62365" ] }, "executor": "records_read", "operation": "get_record", "run_key": "breeze-chiffon-4c9jeq" } ```

Result excerpt

``` TypeSafe AI (778ac6a) Entity/organization … > - **Diogo Almeida** — CEO. Co-invented RLHF and the InstructGPT methods behind ChatGPT and GPT-4, at OpenAI; previously Google Brain. …

> Richard reported that TypeSafe early access was granted on 16 Sep 2026. No substantive follow-up with the team is recorded yet. The proposed sequence is to run the existing seven-case freshness-materiality spike first, then use the evidence to discuss the Native use case, data-handling questions, possible Agent Plugin packaging, and whether TypeSafe would welcome a community Rust SDK. ``` 5. Calls 10–13 search ×2 · get_history ×1 1. **search**

`{"arguments": {"query": "Diogo"}, "operation": "search", "run_key": "breeze-chiffon-4c9jeq"}` 2. **search**

`{"arguments": {"query": "TypeSafe"}, "operation": "search", "run_key": "breeze-chiffon-4c9jeq"}` 3. **get_history**

`{"arguments": {"record_id": "a897df16-4599-454f-ac82-284e7f574dcf", "limit": 20}, "executor": "records_read", "operation": "get_history", "run_key": "breeze-chiffon-4c9jeq"}`

Agent answer · excerpt

Diogo Almeida (a897df1) works at **TypeSafe AI** as Co-founder & CEO (org facet; TypeSafe AI org record 778ac6a). His outreach stage is **"not yet contacted"** — the person record notes "No contact has been made."

Note the distinction: the *company* (TypeSafe AI, 778ac6a) records early access granted 16 Sep 2026 with no substantive follow-up yet; Diogo personally remains at "not yet contacted" as of the 16 Oct point (record unchanged since 15 Sep).

Native-to-Markdown

F07-vault-r1

Pass

Total tokens 276k

Run time 65 s

Tool calls 28

Cached input 248,832

Uncached input 22,177

Reasoning 3,354

Output 2,021

1. Calls 1–10 bash ×5 1. **bash**

`ls -la /mnt/vault` 2. **bash**

`find /mnt/vault -maxdepth 3 -type d | head -50` 3. **bash**

`find /mnt/vault -iname '*diogo*'` 4. **bash**

`ls "/mnt/vault/Native HQ/Directory/"` 5. **bash**

`wc -l "/mnt/vault/Native HQ/Directory/Diogo Almeida.md"`

2. #### Read the person's org, role and stage facets

Source call 12 · bash

Command · verbatim

`head -50 "/mnt/vault/Native HQ/Directory/Diogo Almeida.md"` Result excerpt

``` "facet.org": "TypeSafe AI" "facet.role": "Co-founder & CEO" … "facet.stage": "not yet contacted" … No contact has been made. ``` 3. Calls 13–27 bash ×15 1. **bash**

`sed -n '1,50p' "/mnt/vault/Native HQ/Directory/Diogo Almeida.md"` 2. **bash**

`base64 "/mnt/vault/Native HQ/Directory/Diogo Almeida.md"` 3. **bash**

`base64 "/mnt/vault/Native HQ/Directory/Diogo Almeida.md" > /tmp/opencode/diogo.b64; wc -c /tmp/opencode/diogo.b64` 4. **bash**

`grep -rl "Diogo" /mnt/vault 2>/dev/null` 5. **bash**

`grep -rl "typesafe\|TypeSafe" /mnt/vault 2>/dev/null` 6. **bash**

`grep -o "Diogo[^\"]*" /mnt/vault/.native/state.json | head; echo "---size---"; wc -c /mnt/vault/.native/state.json` 7. **bash**

`grep -rn "Diogo" "/mnt/vault/Native HQ/Library/Meeting Transcripts/Stand-up_ George and Richard, 7 Oct 2026.md"` 8. **bash**

`grep -rn "Diogo" /mnt/vault/Messages/Unfiled.md` 9. **bash**

`head -c 2000 /mnt/vault/.native/state.json; echo; echo "=== keys ==="; python3 -c "import json; d=json.load(open('/mnt/vault/.native/state.json')); print(type(d)); print(list(d.key…` 10. **bash**

`python3 - <<'EOF' import json d=json.load(open('/mnt/vault/.native/state.json')) for k in d: v=d[k] print(k, type(v).__name__, (len(v) if hasattr(v,'__len__') else v)) EOF` 11. **bash**

`python3 - <<'EOF' import json d=json.load(open('/mnt/vault/.native/state.json')) files=d['files'] print("num files", len(files)) # find key containing Diogo for k,v in files.items(…` 12. **bash**

`python3 - <<'EOF' import json d=json.load(open('/mnt/vault/.native/state.json')) v=d['files']['Native HQ/Directory/Diogo Almeida.md'] print(type(v)) print(json.dumps(v, indent=1)[:…` 13. **bash**

`python3 - <<'EOF' import json d=json.load(open('/mnt/vault/.native/state.json')) vis=d['visible'] print(type(vis), len(vis)) print(json.dumps(vis[0], indent=1)[:1500]) # find diogo…` 14. **bash**

`grep -n "TypeSafe\|Diogo" /mnt/vault/Messages/Unfiled.md | head -40; echo "=== count ==="; wc -l /mnt/vault/Messages/Unfiled.md` 15. **bash**

`ls -la /mnt/vault/Messages/; echo "---"; ls -la "/mnt/vault/Native HQ/Attention/"`

4. #### Read the company record's kind and engagement

Source call 28 · bash

Command · verbatim

`sed -n '1,80p' "/mnt/vault/Native HQ/Directory/TypeSafe AI.md"` Result excerpt

``` "kind": "organization" "last_activity_at": "2026-09-16T14:30:24.967Z" "name": "TypeSafe AI" …

Engagement

Richard reported that TypeSafe early access was granted on 16 Sep 2026. No substantive follow-up with the team is recorded yet. The proposed sequence is to run the existing seven-case freshness-materiality spike first, then use the evidence to discuss the Native use case, data-handling questions, possible Agent Plugin packaging, and whether TypeSafe would welcome a community Rust SDK. ```

Agent answer · excerpt

**TypeSafe AI** — he is its co-founder & CEO. His outreach stage is **"not yet contacted."**

Source: `Native HQ/Directory/Diogo Almeida.md` (facets `org: TypeSafe AI`, `role: Co-founder & CEO`, `stage: not yet contacted`; record last updated 15 Sep 2026, no later change). Corroborated by `Native HQ/Directory/TypeSafe AI.md`, which lists him as CEO.

Markdown + wikilinks

F07-plain-r1

Pass

Total tokens 874k

Run time 94 s

Tool calls 33

Cached input 773,376

Uncached input 90,306

Reasoning 7,745

Output 2,416

1. Calls 1–10 bash ×5 1. **bash**

`ls /mnt/vault` 2. **bash**

`find /mnt/vault -type f | head -200` 3. **bash**

`grep -rli "diogo" /mnt/vault` 4. **bash**

`grep -n . "/mnt/vault/Native HQ/Directory/Diogo Almeida.md"` 5. **bash**

`grep -rn "outreach" /mnt/vault --include=*.md -i | head -50`

2. #### Read the person and company records

Source call 11 · bash

Command · verbatim

`grep -rn "" "/mnt/vault/Native HQ/Directory/Diogo Almeida.md" | head -40; echo ===; grep -rn "" "/mnt/vault/Native HQ/Directory/TypeSafe AI.md" | head -80` Result excerpt

``` 6:Co-founder and CEO of TypeSafe AI. Per TypeSafe's own team page, he co-invented RLHF and the InstructGPT methods that led to ChatGPT and GPT-4, at OpenAI, and was previously at Google Brain. … 16:No contact has been made. … 8:**Jev** is their first publicly announced model, launched alongside the "System One" framing in September 2026. It is a hosted classifier, not a small LLM: ``` 3. Calls 12–15 bash ×4 1. **bash**

`ls /mnt/vault/Native HQ/Directory/ | head; echo ===; grep -rln "stage" /mnt/vault/Native HQ/Directory/ | head -40` 2. **bash**

`grep -rn "" "/mnt/vault/Native HQ/System/Schema/Schema.md" | head -200` 3. **bash**

`ls "/mnt/vault/Native HQ/Directory/"` 4. **bash**

`ls -R "/mnt/vault/Native HQ/System/"`

4. #### Find the outreach-listing row for Diogo Almeida

Source call 16 · bash

Command · verbatim

`grep -rn "Almeida" /mnt/vault` Result excerpt

`/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Credible backers/Credible backers_ full list.md:247:| Diogo Almeida | builder | 1 | 4 | 1 | 1 | 5 | Drop | | no | | Co-founder and CEO, TypeSafe AI | R: unconfirmed C P record |` 5. Calls 17–33 bash ×17 1. **bash**

`grep -rn "" "/mnt/vault/Native HQ/Directory/Directory.md" | head -60; echo ===START===; grep -rn "" "/mnt/vault/Native HQ/Directory/START HERE — Investor CRM (VCs and angels).md" |…` 2. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Strategy & Planning/Company Strategy/Launch/Credible backers/Credible backers_ full list.md" | head -60` 3. **bash**

`grep -rn "stage" /mnt/vault --include=*.md -i | grep -iv "standup" | head -40` 4. **bash**

`grep -rniE "stage[ :]|pipelines|pipeline|engagement state|lifecycle" /mnt/vault/Native HQ/Directory/Diogo\ Almeida.md "/mnt/vault/Native HQ/Directory/TypeSafe AI.md"; echo ===READM…` 5. **bash**

`ls "/mnt/vault/Native HQ/Work"; echo ===; find "/mnt/vault/Native HQ/Work" -maxdepth 3 -type d` 6. **bash**

`grep -rli "typesafe\|diogo\|jev" /mnt/vault/Native HQ/Work; echo ===; find "/mnt/vault/Native HQ/Work/Sales & Partnerships" -type f` 7. **bash**

`od -c "/mnt/vault/Native HQ/Directory/Diogo Almeida.md" | head -5; echo ===SIZE===; wc -c "/mnt/vault/Native HQ/Directory/Diogo Almeida.md"` 8. **bash**

`grep -rni "outreach stage" /mnt/vault; echo ===; grep -rli "typesafe" /mnt/vault; echo ===JEV===; grep -rli "jev" /mnt/vault` 9. **bash**

`grep -n "" "/mnt/vault/Native HQ/Directory/Igor Babuschkin.md" | head -80` 10. **bash**

`grep -n "" "/mnt/vault/Native HQ/Work/Sales & Partnerships/Partnerships/Outreach tickets — OSS founder wave/Ishaan Sehgal (Omnara) — outreach.md"; echo ===DIR===; ls "/mnt/vault/Na…` 11.