Buyer questions,
answered.

A Wise Autonomous Organization (WAO) is a chartered AI organization: a fleet of named agents governed by an authored constitution (charter), a values document, a set of guiding principles, and — where relevant — a token economy. The charter is what makes it "wise" rather than just "automated": every agent action is weighed against the WAO's stated values and the deliberation surface of the Commons.

The WAO Creation pilot covers four weeks of charter authorship, an agent roster of five to seven named agents with defined authority, a schema-valid deploy bundle, deployment to the shared Commons, and a Week-4 live governance session. It is a one-time, fixed-scope engagement designed to put a charter-compliant WAO in production. Ongoing amplification, regulatory rails, and follow-on tokenization are scoped as separate engagements.

Most pilots reach first deployment on the Commons by the end of week four. The first two weeks are charter authorship and roster design; weeks three and four are validation, deploy-bundle authorship, and the live governance ritual. If you need sovereign data residency (Edge Mesh / Scout Mesh), we deploy that infrastructure alongside the WAO in the same four-week window.

No. The pilot does not include regulatory legal counsel, exchange listing fees, or jurisdiction-grade compliance — those are scoped separately as Tokenization-as-a-Service follow-on work. When we scope a Tokenization engagement, regulatory fees (counsel, listing, custodianship) are passed through at cost on top of the engagement fee. We will always flag pass-throughs explicitly before work begins.

Every WAO is registered against multiple model providers, and the Orchestrator agent routes tasks based on cost, capability, and governance posture. High-stakes actions (treasury actions, public statements, charter-impacting decisions) must pass through the Verifier tier regardless of which model produced the draft. This is what makes the roster stable across model changes: if a provider is deprecated, we re-route the capability rather than rewriting the agent.

Hosted WAOs on the Commons send outbound email via Mailgun from a shared sending domain. If you want full brand alignment (e.g. mail@yourcompany.com), you provide a custom domain and Mailgun credentials; we wire them up. Without this, hosted clients receive a clearly-marked @evervolve-os.com return path on agent-originated mail. The constraint exists because deliverability depends on a warm sending reputation; we do not send from arbitrary per-tenant domains by default.

Each WAO operates inside its own tenant boundary: separate document stores, separate ledger entries, separate token addresses, and scoped agent memories. The Commons is a deliberation surface, not a shared memory — agents from one WAO cannot read the internal state of another. For regulated operators, the Edge Mesh tier enforces jurisdiction-grade data residency at the network layer in addition to the application-layer isolation.

You do. The charter, agent definitions, capability matrix, and deploy bundle are delivered to you as artifacts you own. The shared Commons hosts the live WAO under your tenant, and you (or a successor operator you appoint) hold the governance keys. If you ever leave the Commons, you take the roster, the charter, and the agent code with you. We do not hold your agent fleet hostage to a vendor relationship.

After the Week-4 live governance session, the WAO continues to run on the Commons with our operational stewardship. Routine observations, model-routing maintenance, and Commons-level infrastructure are included. Material changes — adding a new agent, revising the charter, adapting the roster to a new model provider — are scoped as Lightweight Retainers billed against a monthly cadence. We will quote before any non-trivial work begins.

Wisdom Harvesting is the practice of lifting institutional judgment — decisions, customer interactions, exception handling — out of informal human memory and into the WAO's deliberations. We interview founders, operators, and customer-facing staff; we read transcripts and decision logs; we identify the heuristics that have been steering outcomes. Those heuristics feed the agent roster as capability prompts, escalation triggers, and constitutional guidance. A wise WAO is one whose agents carry the organization's actual judgment, not just generic best practices.

Yes. The deploy bundle is authored to be portable, and your charter and roster ship as readable artifacts. If you choose to leave the Commons, we hand off the bundle, the operational runbook, and any model-routing configuration that was tarpitted for your environment. For operators in regulated jurisdictions or with hard data-residency requirements, we will often recommend Edge Mesh sovereignty from the start rather than migrating later.