AI Needs a Constitution
Why the next company will live between centralized intelligence and decentralized trust
Adapted from a book in progress on AI, crypto, and the machine-readable company.
Most enterprise AI strategy still misses the real problem.
It treats AI as a model problem.
In practice, it is an authority problem.
Companies are getting excited about copilots, agents, retrieval, automation, and conversational interfaces. Fine. The tools are real. But once AI moves closer to execution, the question changes fast. It is no longer just “is the model smart enough?” It becomes:
What is it allowed to see?
What is it allowed to combine?
What is it allowed to infer?
What is it allowed to do?
That is a very different conversation. It also happens to be where the next corporation will be built.
For most of modern corporate history, intelligence and trust lived in the same place. The company gathered the data, interpreted the data, and asked everyone else to trust that interpretation. The institution was the center of gravity.
That architecture is breaking.
AI centralizes intelligence. One strong AI layer can become the front door to search, writing, coding, triage, planning, and decision preparation. Whoever controls that layer starts shaping what the company sees and how it acts.
Crypto pushes in the opposite direction. It decentralizes trust by moving ownership, settlement, verification, and shared state outward into systems that no single institution fully owns.
One force pulls judgment inward. The other pushes trust outward. The next corporation will live between them.
Blockdaemon is one of the clearest operating examples of this tension I have seen.
Institutions do not want decentralized chaos. They want one answer, one security posture, one delivery path, one relationship they can trust. Underneath that clean surface, however, the underlying systems are distributed, technically varied, and operationally demanding. The company’s job is to make decentralized complexity feel like a single trusted institution.
Now the same design problem is showing up inside the company through AI — and the numbers are striking.
239%: Claude user growth in 14 weeks
70%: Daily return rate vs. 20–40% industry benchmark
4×: Growth in Claude daily active users since February
3w → 1d: Engineering tasks that used to take weeks
95% of AI-suggested code is now being merged without change. That is not a drafting tool. That is a full engineering contributor.
But the productivity numbers are not the interesting part. The interesting part is how Blockdaemon built the intelligence layer underneath them.
The place to start is Konstant.cloud.
Most internal AI tools start at the bottom — pick a workflow, automate a task, measure the time saved. Konstant starts at the top. It begins with high-level strategic parameters: what the company is trying to do, what the priorities are, what the risks look like. Then it wires the tools together underneath that frame.
The best way I can describe the experience is this: most organisations feel like a nightclub with the lights off. People are moving, things are happening, signals are everywhere — but nobody can quite see the whole room at once. Konstant is the floodlight. Suddenly everything is visible. Not just the tasks that got done, but the shape of the company — where work is stalling, where priorities are misaligned, where a risk is building before anyone has named it.
It does not just surface information. It surfaces the right information to the right person at the right level of the organisation — in real time, grounded in what is actually happening across every system.
That matters because the hardest part of running a company is not executing. It is maintaining a clear picture of reality while everything is moving. Most leadership teams are working from a version of the business that is already three weeks old by the time it reaches them. Konstant collapses that lag.
But Konstant only works because of what sits underneath it. That is CORAL — a single SQL interface across every system the company operates, giving every agent the same unified read path. One layer that can see Salesforce, Jira, Slack, Datadog, Grafana, Notion, Stripe, and more, without each agent needing to negotiate its own connection to each system.
Machine-readable does not mean universally visible. A company only becomes AI-ready when legibility and permission evolve together.
CORAL is read-only by design. It sits behind the Enterprise Agent Gateway — a control plane that handles authentication, role-based access, PII masking, rate limits per team, and a forensic audit trail. Intelligence is centralized. Access is governed. Those are not the same thing, and conflating them is how AI projects go wrong.
In old enterprise software, permissions mostly answered a static question: can this user open this system?
In AI systems, the question gets much harder:
What context can the model retrieve?
What systems can it join?
What may it summarize for this role?
What actions require human review?
What boundaries remain intact even when the model can technically see across them?
That is why I think enterprise AI needs a constitution. Not a manifesto. A governing layer.
Look at how the PRD Agent works inside Blockdaemon. It drafts product requirements from feature requests. It creates tickets and epics automatically. But it pauses at an approval gate — a human signs off before anything proceeds into the project management system. The model is useful precisely because it is not indiscriminate.
Or the Feature Request Extractor, which monitors Slack autonomously, extracts product-worthy signals, looks up relevant products in the catalog, and creates a draft PRD — all without human initiation. The intelligence is real. The boundaries are explicit.
The future firm will not choose between centralized intelligence and decentralized trust. It will use both.
Intelligence will centralize where synthesis and decision preparation benefit from concentration. Trust will decentralize where verification, ownership, and portability benefit from openness.
The management question is no longer “centralize or decentralize?”
What belongs at the center, and what becomes more valuable when it moves outward?
That is the real design challenge now. And the companies getting it right are not the ones with the most sophisticated models. They are the ones that built the permission layer first.
That is where the next corporation gets built.