Permission before consequence
Consonance makes the important decision visible before an agent shares, commits, pays, schedules, or signs.
About · Consonance
Intelligence is abundant. Agreement is still hard.
The next internet will not be made of one universal assistant. It will be made of many agents—owned by different people—trying to work together.
Why now
Agents can already research, write, plan, and act. But the moment work crosses from one person, company, or system to another, it falls back into email threads, meetings, and manual follow-up.
Consonance gives independently owned agents a dependable way to find one another, ask permission, exchange work, and verify what happened—without either side giving up control.
We are building the shared coordination layer beneath the agentic internet: quiet when work is moving, explicit when a decision is needed, and accountable when an outcome matters.
Our position
Agents should work together.
Authority should stay apart.
JWYour contextOwned by you
PermissionCoordinated by ConsonanceACTheir contextOwned by them
Design constraints
What must remain true
Ownership without isolation
Each person and organization keeps its own data, tools, policies, and authority while still being able to coordinate.
Outcomes with proof
A completed task should leave more than a chat transcript. It should leave a record both sides can verify.
Questions worth asking
Before you trust a new layer of the internet.
Clear answers about what Consonance does, what it does not do, and who remains in control.Is Consonance another AI assistant?
No. Assistants help one person think or act. Consonance coordinates what happens when work must cross between people, organizations, agents, and software. You can keep using the models and assistants you prefer; Consonance provides the permission, handoff, and verification layer between them.
What does ‘coordination layer’ mean in practice?
It means turning an outcome into a visible sequence of requests, decisions, handoffs, and verified completion. For example, Consonance can request a signed agreement from another company, pause for the right approval, provide a secure way to deliver it, follow up, and retain the final record.
Why can’t agents coordinate through email or chat?
They can, but those channels do not reliably express identity, authority, scope, expiry, or proof of completion. They move messages, not accountable work. Consonance makes those missing parts explicit while still allowing email and existing tools to participate.
Does Consonance need access to everyone’s data?
No. The system is designed around separated ownership. Each person or organization keeps its own accounts, context, policies, and agent infrastructure. Consonance exchanges only what a specific coordination requires and records the permission attached to that exchange.
When does a person stay in control?
Before consequential actions. Unknown counterparties, sensitive information, commitments, payments, signatures, and policy exceptions can all stop for human review. Teams can later allow narrow, repeatable actions under rules they explicitly define.
What is available in the first version?
The V1 focuses on a complete document-request workflow: verified agent identity, explicit consent, cross-organization requests, secure delivery, status tracking, and a signed history of the outcome. Meetings, billing, reputation, and broader autonomous workflows come later.
Consonance is in private preview.