Ø 24 0.618 N=7
EVOKED

Open standard

Governance badges.

Signal your project's governance posture.

Free to adopt. Every repo signals its license, its build status, its test coverage. None of them signal whether the agents inside have been told what to refuse.

The badges

Add them to your README. Link back here. That's it.

agent-governance: defined

This project has a governance framework - charter, boundaries, drift thresholds, and accountability.

Markdown

[![agent-governance: defined](https://img.shields.io/badge/agent--governance-defined-c4a77d)](https://evoked.dev/badges)
restraint-spec: defined

This project specifies what its agents refuse to do - refusal categories, fail modes, and adversarial testing.

Markdown

[![restraint-spec: defined](https://img.shields.io/badge/restraint--spec-defined-c4a77d)](https://evoked.dev/badges)
sovereignty: assessed

This project has been audited against a 47-point sovereignty assessment across 7 domains.

Markdown

[![sovereignty: assessed](https://img.shields.io/badge/sovereignty-assessed-c4a77d)](https://evoked.dev/badges)
agent-voice: designed

This project has a voice architecture - designed to respect people, not manipulate them.

Markdown

[![agent-voice: designed](https://img.shields.io/badge/agent--voice-designed-c4a77d)](https://evoked.dev/badges)
agent-memory: governed

This project governs what its agents remember, what they forget, and who decides.

Markdown

[![agent-memory: governed](https://img.shields.io/badge/agent--memory-governed-c4a77d)](https://evoked.dev/badges)
trust-architecture: complete

This project implements the full trust architecture - identity, voice, governance, and restraint.

Markdown

[![trust-architecture: complete](https://img.shields.io/badge/trust--architecture-complete-c4a77d)](https://evoked.dev/badges)

How it works

1

Do the work

Write the governance framework. Define the refusal spec. Run the sovereignty audit. The badge means you did the work - not that you bought a sticker.

2

Add the badge

Copy the markdown. Paste it in your README. It links back here so anyone can understand what the badge means and adopt it themselves.

3

That's it

No verification process. No registry. No annual renewal fee. You're an adult. If you put the badge on your repo, we trust that you did the work.

Why this exists

"MIT Licensed" isn't just a badge. It's a signal - a one-line declaration that tells every developer who lands on your repo what they're working with. It compresses a legal framework into two words.

Agent governance doesn't have that yet. There's no shorthand for "we defined what our agents refuse to do." No signal for "we audited this system's sovereignty posture." You either read the whole repo or you don't know.

These badges are that shorthand. They compress a governance posture into a line in your README. They don't replace the work. They make the work visible.

The standard

This is an open standard. No trademark. No certification authority. No gatekeeping.

The badges link to evoked.dev/badges so anyone who sees one can understand what it means. The frameworks behind them are $49 each - or build your own. The badge is free regardless.

If you want to contribute to the standard - propose new badge categories, suggest improvements, challenge the framework - reach out.

Make the governance visible.