Hi,
My name is Vlad and I'm a co-founder of Extella AI. Being a founder myself I know that we tend to fall into a trap: the deeper knowledge you have about your product, the harder it gets to talk about it without feature and technical-dumping. Chip and Dan Heath call this the "Curse of Knowledge" in their book "Made to Stick". Once you know everything, your forget how this information sounds to people who don't know your product.
The advice they give is to find the core idea of your product and make it compact.
Let's make this a little more challenging and therefore interesting:
Pitch your product in as many words as there are letters in its name. I'll go first.
EXTELLA -> 7 words. "Self-evolving AI shaped entirely by your work"
P.S. we are launching on Product Hunt tomorrow, check us out
Voquill
Intereting. Just curious how this handles conflicts or inconsistencies when it starts learning across different workflows. Good luck!
Absolute Cryptography
@henry_habibΒ Good question β and an honest one.
Conflicts surface explicitly, not silently. When two Rules contradict, the agent flags it during interaction. You decide which stays, or you merge them into a new Rule that resolves the tension. Nothing conflicting quietly accumulates in the background.
For knowledge across workflows, Concepts handle it the same way. When similar knowledge comes in from different sources, the system deduplicates and merges rather than stacking duplicates. If there's a genuine inconsistency β two workflows that learned opposite things β it gets surfaced for human resolution, not auto-resolved by the system.
But here's where it gets more interesting.
You can teach the agent exactly how to handle ambiguity β not just flag it, but resolve it. You define Rules for how to research a contested claim, how to fact-check, how to assess recency and relevance, how to weigh conflicting sources by importance. The agent learns your epistemology, not just your preferences. Once those Rules exist, the same judgment you'd apply manually gets applied automatically β every time, at scale.
You can also teach the agent to recognize the boundaries of its own knowledge. Rules and Concepts can encode a self-assessment protocol: when the agent hits a gap, it doesn't guess β it identifies what it doesn't know, flags it, and can trigger an automated research or learning workflow to close that gap. It learns to know what it doesn't know.
And then the final step: you automate the configuration work itself. Once the agent understands your standards for conflict resolution, fact-checking, and self-improvement β you build Experts that handle that process automatically. New knowledge comes in, gets verified against your criteria, gets merged or flagged, gets added to memory β without you touching it.
The goal of human involvement is not to be always present. It's to teach the system well enough once that it stops needing you for that class of decisions entirely. Every hour you spend teaching the agent reduces the next thousand hours of manual intervention to zero.
That's the trajectory the architecture is designed for. You start in the loop. You work yourself out of it.
Thank you for asking!
This is a great companion when you are on a cross between creativity and technology!
I built some tools for my TTRPGs and automated script writing with this tool
Absolute Cryptography
Absolute Cryptography
If you want to test Pro today β here's how it works:
1. Apply code PRO-PLAN to activate the plan first
2. After that, top up credits inside the app using code PHPROMO50 (first 50 users)
If you already have an Anthropic or OpenAI key, connect it instead of buying credits.
Either works, but the Pro activation has to go first.