Voices

What people wrote about my work, in their own words, on the platform where they wrote it.

15 voices about The Curator · Show all

Enrique Barclay

Inside Sales Engineer @ Commvault | Ex-...

On LinkedIn

The 80% mark is the exact line I watch too. What made it click for me was treating the handoff md as a real artifact, not a scratchpad: I write it like a new engineer is taking over cold, then let the session die. Do you keep one rolling spec per project, or branch it per major feature?

Nardus du Plooy

Cotrugli Business School Vanguard member

On LinkedIn

I installed the Curator and then ingested Drazen Kapusta's Art of Vanguard Leadership. What came back wasn't a summary. It was 20 structured wiki pages: NEO Era, Vanguard Leadership, Wolf-Dog-Sheep Patterns, Fear as Data, Reputational Capital. Each one was cross-linked to the others. I then pulled those pages into the Navigator app I've been building for the Vanguard MBA, as a Second Brain Vault the students can query on their phones. The distinction between storing and compounding became real in that moment. Storing is a pile. Compounding is architecture. I then asked The Curator "What is the Sheepdog principle?" and it answered from the book with a source citation. That's not search. That's thinking.

IndaPoint Technologies Pvt. Ltd

Company page

On LinkedIn

We think this is a strong step toward making knowledge management more accessible without sacrificing ownership or portability. Keeping the knowledge base as plain Markdown on the user's own machine is especially valuable it reduces vendor lock-in while making the information usable across tools, agents, and workflows.
The agent memory layer is also interesting because persistent context can reduce repeated discovery and help agents build on previous decisions rather than starting from scratch.
How do you see teams balancing shared organizational knowledge with privacy and individual control as agent memory becomes more common?

Raymond NISINGIZWE

CEO& FOUNDER: Digital GreenShield Africa an...

On LinkedIn

The Curator brain is very valuable for our Digital GreenShield Africa because it transforms scattered agricultural data (farmers, climate, crops, finance) into a connected knowledge system. Instead of storing information in isolated dashboard, DGSA can use a knowledge graph where every farmer, weather event, and crop is linked, farmer ,NGOs ,Government to interact ,making it easier to detect hidden patterns like drought → low yield → loan risk. This helps DGSA move from simple data reporting to intelligent decision-making, prediction, and real-time insights for farmers and financial partners.

Nardus du Plooy

Cotrugli Business School Vanguard member

On LinkedIn

The ingestion bottleneck is real. It's not a lack of curiosity, it's the friction between saving something and actually making it yours. I think the domain-based approach is the smartest part. One focused wiki per topic, getting richer with every source you add. That's what makes this different from every "save everything" tool that… more

Valentine Nguemne

Software Engineer, Head of engineering, ...

On LinkedIn

Just cloned and tested it : amazing!
Though i exagerated and exhausted my free quota for gemini already.
Can't wait to see it grow into using a free LLM hahaha.

Mehdi Zare

On X

This is the part that feels durable: a shared handoff layer matters more than which model opens the session. The context contract is the real harness.

mao mao

On X

shared memory is the bit my agents keep missing; I've had to paste the same project constraints into three separate sessions before.

Pablo

On X

menu bar at-a-glance for a context engine is such a Mac shape. love that the wiki surface lives there.same instinct on my side with Ventus. keep the controls in the menu bar and stay quiet until the machine spikes.

Harry Ashton

On X

Oh incredible I did think of Obsidian as you read this and saw you're using the map for it. Very useful indeed, a common across all teams/projects but I wonder how efficient this is as opposed to maintaining skills? Or is that a work in progress? :)

Ademola

On X

Yeah, that was the part that clicked for me too

The more I dug into it, the less it felt like a tool for "AI memory" and more like a layer that lets the context survive while everything around it keeps changing

I am glad the visual got that across 🙏

Ademola

On X

“Your context survives” is the promise
“Here is exactly what the agent is starting with” makes it to be tangible

That feels like a really strong visual story too

Tejas Sharma

On Medium

been building something like this too. the graph view is where it gets interesting. around 30 to 40 sources in, you start seeing clusters you didn't plan for. connections between things you read months apart that you never consciously linked.

Robin Good

On Substack

Wow. This is really very good.

Thanks for having created The Curator and having made available to everyone!

.

I am trying to buy some extra time to test and explore it as much as possible.
A few small feedback points from a non-expert, non-technical user:

.

Lious

On Substack

The explicit separation between technical maturity and the unproven real-group test is the strongest part of this account. A shared knowledge system can pass concurrency and deletion tests yet still fail socially: unclear ownership, unresolved contradictions, or corrections that never propagate. For the first cohort, which evidence would matter most beyond uptime: correction latency, source attribution, conflict resolution, or whether contributors can explain how a shared conclusion changed?