saascode
web3 & on-chain infrastructure·run 074 · May 2026

Mosaicagent

A client-readable agent evidence passport that binds identity, versioned evaluations, policy events and attestations to portable signed records while keeping confidential data off public ledgers.

Genesis score6.08/10
Make Mosaicagent real.0/500
500 more votes and Mosaicagent is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
3Confirmed public evidence primitives
0Universal trust guaranteed
The case

Agencies change an agent's model, framework and hosting while clients need continuity about what was evaluated, which policies applied and what failed. Mosaicagent creates a portable identity and signed evidence history across approved migrations, with client-readable dimensions rather than a naked trust badge. The supplied research confirms a live agent leaderboard, a free public transparency log and public attestation infrastructure, while finding no verified agency portal joining them. Funding, service levels and public infrastructure fees are observed market references, not fixed product pricing. A shared schema could gain adoption, but network effects are hypothetical and portability depends on governance. A cryptographic signature proves who signed a record and that it was not altered; it does not prove the underlying claim, agent identity continuity or future safety. Identity, software version, evaluation run, result, policy event, attestation, anchor receipt, client interpretation and procurement decision remain separate. Only hashes and non-sensitive metadata belong on a public ledger. The product can make evidence portable and tamper-evident within a stated threat model. It cannot create objective trust or guarantee behavior.

Who pays — and why

An agency governance, security or client-success owner needing portable, reviewable evidence for agents deployed across changing technical implementations.

Market signalValidate by agencies, agent identities, versions, evaluation suites, policy events, attestations, client viewers and revocationsAgent evaluation and public attestation infrastructure are observed market references, not fixed product pricing
What it unlocks
A durable agent identity binding owner, purpose, deployment scope, software version, model role, tool permissions, policy version and migration lineage.
An evidence schema separating test suite, environment, evaluator, raw result, methodology, uncertainty, policy event, human attestation and expiry.
A signed publication chain from private evidence through approved digest, signature, public hash receipt, client verification, correction, revocation and superseding version.
How Genesis scored it
6.08across seven criteria
tension 7temporal 6blindspot 5buyer 8leverage 6convergence 5why-not 5
8
Buyer persona

Agency governance and client owners have a clear need for deployment evidence and portability.

7
Productive tension

Clients want one simple trust card, while honest evidence is multidimensional, contextual and time-bounded.

5
Why nobody did it

The distribution gap is clearer than the historical barrier to building it.

Why it scored well

A specific agency buyer, live evaluation primitive and free transparency infrastructure make portable agent evidence concrete.

What's holding it back

Network effects are speculative, identity continuity is difficult, one interface was unverified and a composite score can dangerously overstate trust.

Signals detected3 sources crossed
SignalCompetitor research

SignalInfrastructure research

SignalGap research

Direction briefmosaicagent-portable-agent-evidence.md
mosaicagent-portable-agent-evidence.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.