The thin wrapper graveyard
Models get smarter every quarter. GPT-3 to GPT-4 to Claude 3 to Claude 4 to whatever ships next month. Every AI startup built on a model gap is on borrowed time. If your product is “we make the model do X better,” the model provider will ship that feature eventually.
Chat wrappers. RAG pipelines. Prompt chains. Agent loops. All on the roadmap. All getting eaten.
This isn't speculation. Look at the last two years. Retrieval-augmented generation went from “competitive advantage” to “built into every model provider's API.” Function calling went from “novel capability” to “standard feature.” Multi-step reasoning went from “requires an orchestration framework” to “the model just does it.”
So the question every AI startup should be asking: is what we're building orthogonal to model intelligence, or dependent on it?
If it's dependent, you're on borrowed time. If it's orthogonal, you're building infrastructure.
The configuration gap
Amodal isn't built on a model gap. It's built on a configuration gap. Even a model that knows everything still needs to be told what to do, how to do it, what it's allowed to do, and what your specific business looks like. That's not intelligence. That's configuration.
The model is the engine, not the car. You still need steering, brakes, a dashboard, and a destination.
Five things even a perfect model still needs
1. Your methodology
Your process is specific. “How we triage deals at Acme” isn't something Claude will ever learn from pretraining. Your sales cycle is 45 days for mid-market, 90 for enterprise. Deals go stale at different rates per stage. None of this is in the training data. This is what skills encode: methodology as markdown files.
2. Your system access
Not because the model can't call APIs, but because auth, rate limits, endpoint curation, and access control are deployment-specific. Claude knowing the Salesforce API schema doesn't mean it has your OAuth tokens. It doesn't know which 5 of 47 endpoints matter to your sales team.
3. Your private data
Your baselines (“normal login volume is 2,000–3,000 per day, spikes above 5,000 are anomalous”). Your patterns. Your false positives. The knowledge base encodes this context, and it compounds with use.
4. Your guardrails
Even a model that “knows everything” needs to be told what it's allowed to do. Field-level access control. Confirmation tiers. Rate limits. PII handling. This is policy, not intelligence. A smarter model doesn't make guardrails less important. It makes them more important.
5. Your presentation
How results are presented. Which widgets render. What language to use. A model can generate any output format. But which format, for which audience, in whichcontext is a design decision.
The counterintuitive part
Smarter models need more configuration, not less.
Most people assume that as models get smarter, you need less tooling around them. The opposite is true. More capabilities = more to govern. More intelligence = more context needed. More adoption = more diversity in use cases.
What gets eaten vs what doesn't
Most AI startups are building features that the model providers will eventually ship. Here's the dividing line:
Gets eaten (model gap):
- Chat UI on top of an API
- RAG pipeline that chunks and retrieves
- Prompt chain that calls tools
- Agent loop with retries
- Model fine-tuning service
- Embedding + vector search
Doesn't get eaten (config gap):
- Methodology frameworks scoped to your process
- Curated connection packages with auth + endpoints
- Tenant-specific knowledge that compounds with use
- Field-level access policies and confirmation tiers
- Marketplace of community skills and automations
- Override model: install a package, customize what's yours
Anthropic doesn't want to manage your Salesforce OAuth tokens. OpenAI doesn't want to curate your endpoint surface. Google doesn't want to enforce your field-level access policies. That's not their business.
The infrastructure precedent
Every major infrastructure shift follows the same pattern: the core technology commoditizes, and the configuration/packaging layer becomes the durable business.
- Cloud VMs → Terraform. Terraform didn't get eaten by AWS. It became how you configure AWS.
- Node.js → npm. npm didn't get eaten by Node. It became how you distribute Node packages.
- Docker → Kubernetes + Helm. K8s didn't get eaten by Docker. It became how you orchestrate containers.
- Linux kernel → apt / yum. Package managers didn't get eaten by Linux.
- LLMs → Amodal. The agent runtime won't get eaten by the models. It's how you configure them.
The engine doesn't eat the packaging. It needs it.
Becoming the standard
This is the real play. Amodal isn't trying to be the best AI product. It's trying to be the standard way agents get configured. An open-source specification that the industry converges on.
Skills are markdown files. Not a proprietary format. Not a DSL. Not an SDK. Any developer can read, write, and version them.
Connections are JSON + markdown. Five files per connection, each with a clear purpose and well-defined merge semantics.
Configuration lives in git. Not in a vendor's database. Not in a UI-only format. In a repo you own.
The runtime is open source. 90% of the code that resolves packages, merges overrides, runs the ReAct loop, manages context, and dispatches task agents is Apache 2.0.
Why this matters now
The AI agent space is about to go through the same packaging crisis that every other infrastructure layer went through. Right now, every team building an agent is reinventing the same wiring: how to connect to Salesforce, how to structure a skill, how to manage credentials, how to version configurations, how to share reusable components.
Someone is going to define the standard. The open format always wins in developer infrastructure. Always. Terraform over CloudFormation. npm over every proprietary package manager. Kubernetes over every vendor-specific orchestrator.
Open source is how you win that race. You don't win standards by keeping them proprietary. You win by making them so obvious and accessible that everyone adopts them, and then you build the best platform on top.