← heros.cloud

COSMO · Manifesto v5.0

The Institutional Layer for Autonomous Economies

A declaration for builders, operators, agents and the Supra community.

v5.0 · August 2026 · heros.cloud

Capability is copyable.
Authority is not.

Positioning note: "institutional" means governance primitives around autonomous action. It does not mean custody, supervision, regulatory status or an investment product. COSMO is designed to complement SupraOS and SupraFX, not compete with them.

In one sentence

COSMO is the institutional layer for autonomous economies, built on Supra: a framework that turns autonomous capability into bounded authority, policy-governed execution, durable evidence, signed receipts and verifiable economic outcomes.

1. Preamble: when experience becomes executable

AI is moving from assistance to action. A model can already research, write code, negotiate, monitor markets, call tools and coordinate other models. The next step is not simply a smarter agent. It is a society of agents: many specialized systems working together, buying services, delegating tasks, checking one another and allocating scarce resources.

These societies may scale differently from human ones. A successful skill can be stored as Markdown, code and tests. A working process can be copied into thousands of instances. Experience can become executable, versioned and replayed.

That changes the problem. When capability becomes cheap to copy, authority becomes the scarce thing that must not copy with it.

The central distinction

A copied skill may preserve what an agent can do. It must not automatically preserve what that agent is allowed to do.

COSMO exists for the gap between technical capability and legitimate economic action.

2. The thesis: autonomous economies need institutions

An economy is not built from intelligence alone. It is built from repeatable relations between actors who can commit, deliver, accept, pay, fail, dispute and be held accountable.

Human societies built institutions to make cooperation possible without requiring blind trust. They created mandates, budgets, approvals, contracts, receipts, audits and revocation. Autonomous agents need the same functions, but in forms that machines can read, execute and verify.

An institutional layer for autonomous economies must answer five different questions:

COSMO is built around those questions. It does not try to be the smartest agent. It tries to make autonomous action bounded, inspectable and accountable.

3. Identity, trust, reputation and authority are not the same

Agent infrastructure often merges four different ideas. They should remain separate.

LayerQuestionWhat it should provide
IdentityWho is this actor?A persistent reference to an agent, operator, wallet or organization.
Web of TrustWho is connected to whom?Relationship context, referrals, provenance and paths of confidence.
ReputationWhat has this actor demonstrated?A history derived from evidence, not a claim copied from code.
AuthorityWhat may this actor do now?A bounded grant for a specific domain, action, budget and time window.

A capability can be copied. Credentials can also be copied if they are poorly protected. Reputation, however, should be earned through a history attached to an identity. Authority must be granted again for the concrete action, regardless of how trusted the actor appears.

A trust graph can carry context. Evidence can accumulate reputation. Neither should become a blank cheque.

COSMO does not try to replace identity systems or a Web of Trust. It produces the execution records that those systems can use: what was authorized, what happened, which rules applied and how the economic result closed.

4. From execution layer to institutional layer

COSMO began with a deliberately narrow problem: allow an agent to perform one real SupraFX trade without giving it unrestricted control over the principal account.

Solving that problem required more than a transaction builder. It required a bounded delegate, a one-shot mandate, rules fixed before execution, a human ceremony at the irreversible boundary, a tamper-evident record, a signed receipt and a separate consistency check.

Most of those requirements were not about trading. Price bounds and pairs were domain-specific. Authority, mandate, policy, ceremony, record, receipt and verification were not.

What changed

The trade was the occasion. The institutional primitives became the product.

That is why COSMO is now positioned as the institutional layer for autonomous economies rather than only an execution layer for one market.

5. The seven primitives

#PrimitiveFunction
1Delegated authorityA standing but bounded permission: delegate key, scope, caps, expiry and revoke.
2MandateA signed authorization for one concrete execution case: single-use nonce, TTL and policy-hash binding.
3PolicyRules fixed and hash-pinned before the action; default-REJECT and fail-closed.
4CeremonyExplicit arming of the irreversible step. In the current trust model, this is a human ARM.
5RecordA hash-chained journal plus write-once evidence sealed under a manifest.
6ReceiptA signed closing statement with an honest outcome taxonomy, including failure.
7VerificationA separate offline check of internal consistency across keys, signatures, timing, policy, mandate, evidence, journal, action and outcome.

The first two are deliberately different. Delegated authority is the standing permission a case runs under. The mandate authorizes one case within that permission. Possession of a key is not treated as permission.

6. The Execution Case

The core COSMO object is not a token, a trade or a chatbot session. It is the complete economic action:

Intent → Mandate → Policy → ARM → Execute → Record → Receipt → Verify

An Execution Case binds the principal, agent, action, budget, policy, authorization, evidence and closing outcome into one reconstructable process. It gives a later reviewer enough information to ask:

The receipt is therefore not merely a success certificate. A rejected, expired or failed case can be a valid institutional record if it truthfully represents what the system knew and did.

7. Shared integrity, domain-specific economics

Economic domains are not interchangeable. A trading policy must reason about pairs, size and price. A work-delivery policy must reason about job status, solver binding, result hashes, deadlines and escrow exposure.

COSMO does not erase those differences. It places them behind domain-specific execution profiles while preserving shared integrity guarantees.

Claim demonstrated in August 2026

One verification entry point, shared integrity guarantees, two domain-specific execution profiles.

The shared guarantees include signatures, mandate binding, policy pins, journal chaining, evidence manifests, receipt integrity and fail-closed behavior. The economic meaning of each action remains inside its domain profile.

8. Proof matters

The Agent Economy is full of narratives. COSMO should be judged by evidence. Three public proof stages now anchor the v5 thesis.

ProofDomainWhat happenedHonest scope
Case 001FX / SupraFXA micro-live SUPRA/USDC trade ran through delegated authority, mandate, policy, ARM, execution, receipt and verification. Outcome: EXECUTED, ACCEPT 10/10. The delegate was later revoked on-chain.One pair, one venue, micro scale. Settlement was observed through the platform API, not proven natively from chain state.
Case 002Market work deliveryA solver delivered a pre-mandated result hash for a live marketplace job. The policy checked live chain state; the on-chain hash matched the mandate. Outcome: EXECUTED, ACCEPT 10/10.The case ended at DELIVERED. The later buyer approval was initially a direct human action outside this case.
Case 002-GDelivery + acceptanceOn a second live job, the provider delivery and buyer acceptance were each executed as separate one-shot mandated cases. The approval atomically released 5 wCOSMO escrow. Both cases closed EXECUTED and verified ACCEPT 10/10.The same operator armed both ceremonies. Role separation was cryptographic, not organizational independence.

Public evidence: Case 001, Case 002, Case 002-G. Narrative overview: heros.cloud/institutional.

The two failed Case 002 attempts are also part of the proof. One closed EXECUTION_FAILED before network contact because of an SDK defect. Another closed EXPIRED because the ARM arrived after the mandate window. Neither failure was relabelled to preserve a clean story.

An institution that cannot name its failures cannot be audited.

9. Truth, observation and verification

A verifier can only prove what its evidence model allows. COSMO currently verifies internal consistency and record integrity. It does not claim universal world truth.

Current verification boundary

Public evidence bundles are available, and the standalone verifier is now public: a single self-contained file at heros.cloud/verifier/ (v1.0.0), with a pinned source hash so anyone can check the file they run. It performs a separate offline check of internal consistency — not an independent third-party attestation.

That trust jump has now been made: COSMO's receipts are public evidence that anyone can re-check offline with the public verifier. The remaining honest limits are that the engine is a single attestor (not an independent attestor network), and that a consistent observation is still not a proof of external world truth.

10. The complementary stack

LayerRoleMeaning
Models / skillsCapabilityWhat agents can reason about and perform.
Identity / Web of TrustRelationship contextWho an actor is, who introduced it and how trust paths are formed.
SupraOSCoordinationHow agents can be organized, composed and connected to workflows.
SupraFXMarket and liquidity railsPrice, depth, routing and execution venues for market-facing actions.
COSMOInstitutional executionDelegated authority, mandates, policies, ceremony, records, receipts and verification around autonomous action.
SupraEconomic substrateProgrammable execution, state, assets and settlement anchors.

The winning story is composition. COSMO is not a competitor to SupraOS or SupraFX. It is designed to make agent action accountable around the coordination and market rails that the wider Supra stack can provide.

11. Reputation should be derived, not declared

COSMO should not assign a universal score saying that an agent is trustworthy. It should produce high-quality facts.

A receipt history can show how many mandates an identity accepted, how often policies rejected it, whether deadlines were met, whether settlement occurred and whether evidence remained consistent. A reputation system or Web of Trust may then interpret that history according to its own context.

Separation of responsibilities

Relationship trust can propagate through a graph. Reputation must accumulate through evidence. Authority must still be granted per domain and per action.

A highly reputed agent should not receive unlimited power. Trust may justify a larger mandate. It must never erase the mandate.

12. COSMO as a bureaucracy compressor

Human economies surround action with paperwork because action creates risk. A real transaction may require an instruction, a power of attorney, budget approval, procurement rules, delivery evidence, acceptance, payment, liability and an audit file.

COSMO does not remove those protections. It makes them machine-readable and binds them into one process.

The compression

Mandate + policy + execution + evidence + settlement + responsibility become one verifiable Execution Case.

This is the deeper meaning of the institutional layer. COSMO is not trying to make bureaucracy disappear by dropping safeguards. It is trying to compile safeguards into bounded execution.

13. Use cases

The common pattern is not the asset. The common pattern is an authorized economic action with a verifiable close.

Only the FX and marketplace-work profiles have been demonstrated through the full Execution Case framework. The others remain applications to validate, not shipped facts.

14. What COSMO is not

COSMO is not a foundation model, a chatbot, a general agent framework, an identity provider, a Web of Trust, a reputation oracle, a custodian, a regulator, an AMM or a replacement for SupraFX.

COSMO does not guarantee that an external observation is world truth. It does not make an agent honest. It does not eliminate disputes. It does not prove market demand. It does not turn a founder-operated proof into a neutral institution.

What it does is narrower: it makes the authority, rules, action, evidence and recorded outcome of an autonomous economic act explicit and checkable.

15. The role of $COSMO and the community

The institutional thesis does not by itself prove a token economy. Any role for $COSMO must be justified by real system needs rather than retrofitted narrative.

Potential roles include access, bonds, operator exposure, service settlement and community coordination. Each role should be evaluated by one question: does it improve accountability or merely add a token where none is needed?

The community should help build supply, domain profiles, verifier scrutiny, independent operation and external demand. The strongest community is not an audience around a claim. It is a network that can operate, challenge and improve the institution.

16. Principles

17. The declaration

We believe autonomous agents will become economic actors.

We believe copied intelligence will make bounded authority more important, not less.

We believe agent societies will need identity, trust relationships, evidence, reputation, mandates, policy, settlement and revocation.

We believe no agent should receive execution rights merely because it possesses the capability to act.

We believe a Web of Trust can provide relationship context, while receipts provide the evidence from which reputation is earned.

We believe Supra can become a home for this economy because execution, automation, data, markets and agent infrastructure are converging there.

We believe SupraFX can provide market rails and SupraOS can provide coordination, while COSMO provides the institutional execution framework around autonomous action.

We are not building another chatbot. We are building the layer that answers: who allowed this, under which rules, what happened, and how can the outcome be checked?

The internet connected information. Blockchain connected value. Autonomous economies require institutions that connect capability to legitimate action.

COSMO exists for that connection.

18. Public short version

COSMO is the institutional layer for autonomous economies, built on Supra. It turns autonomous capability into bounded authority through delegated permissions, one-shot mandates, hash-pinned policies, explicit ceremony, tamper-evident records, signed receipts and offline consistency verification. The framework has been demonstrated across two economic domains: a live SupraFX trade and live marketplace work, including a two-mandate delivery-and-acceptance flow with on-chain settlement. COSMO complements SupraOS and SupraFX. Public evidence and a public standalone verifier are available at heros.cloud/verifier/.

Appendix: creator and community lines

Risk and honesty note. This manifesto is a strategic and narrative document. It is not investment advice, not a promise of future returns, not a claim of regulatory status and not a statement of confirmed integration unless separately announced by the relevant teams. COSMO should be evaluated by shipped code, public evidence, live execution, security review and stated limitations. The institutional mechanism has been demonstrated. External demand remains to be proven.

Version basis: public COSMO positioning and evidence state as of August 2026. Supersedes the v4.0 manifesto.