Council Certificate
The Council convened · 4 independent model seats
APPROVED
50% agreement · 2 approve / 2 revise / 0 veto / 0 abstain
“Council Certificate v1 — signing & transparency design”
item sha256 · 1cb3e64a42a1c6365d4879e1b777a2b74451ff7f8943aa33b45e3cb7f8e2fd02
The question put to the Council: “Aetherneum is shipping Council Certificates v1 exactly as specified in the attached design. Are the cryptographic bindings, the transparency ledger semantics, and the honestly-scoped threat model sound to ship as a public certification primitive?”

The seats

SeatVoteConfidenceHeadline
Anthropic Claude
claude-sonnet-4-20250514		 REVISE 80% Sound cryptographic design but needs key rotation plan and clearer provenance limitations.
Groq Llama
llama-3.3-70b-versatile		 APPROVED 90% Council Certificates v1 design is sound
Cerebras GPT-OSS
gpt-oss-120b		 REVISE 78% Design is largely sound but needs key‑management and transparency improvements before public release
Moonshot Kimi
moonshot-v1-32k		 APPROVED 95% Council Certificates v1 is sound for shipping as a public certification primitive

Where the panel disagreed

“Sound cryptographic design but needs key rotation plan and clearer provenance limitations.” — Anthropic Claude, voted revise
“Design is largely sound but needs key‑management and transparency improvements before public release” — Cerebras GPT-OSS, voted revise

Risks raised

  • No key rotation mechanism specified for long-term operational security — Anthropic Claude
  • Provenance limitation may not be sufficiently prominent to users — Anthropic Claude
  • Single point of failure in issuer's admin plane for certificate integrity — Anthropic Claude
  • Key management errors — Groq Llama
  • Issuer infrastructure compromise — Groq Llama
  • Issuer key compromise or insider falsification of model votes — Cerebras GPT-OSS
  • Git repository anchoring may be mutable without additional signed attestations — Cerebras GPT-OSS
  • Lack of cryptographic proof of model provenance could undermine trust — Cerebras GPT-OSS
  • Key rotation and backup recovery procedures are not formally defined — Cerebras GPT-OSS
  • Key management and migration to Vault Transit — Moonshot Kimi
  • Potential for future changes in cryptographic standards — Moonshot Kimi

Provenance

certificate id
ae1-498e-cfdc-1a62-4bfb
issued
2026-06-10T04:27:02+00:00
session
2026-06-10T04:26:39.167Z
signature
Ed25519 · 47b1885c080ed8aeea7580c3df9e97fd…
public key
d267b4307118c259b6bec3cd98b233033a901d7b52fd3bb05d89134a534d4023
ledger day
2026-06-10 · leaf index 0
leaf hash
718d3c4854de83092d51f9d208e2d34728397056405b91f88c3e15364f1fa046
merkle root
4606febff14d5a566e77ada0049bda74cce2e9fb1aee36a666a6ec5856bc217a (tree size 2) · anchored publicly

Certificate JSON Verify this certificate

Verify independently at aetherneum.com/cert/verify — the signature checks out or it doesn’t.

This certificate is Aetherneum’s signed attestation of a session of The Council — AI models from different providers reviewing one item, with disagreement preserved. The cryptography proves issuance and integrity: what Aetherneum signed, when, and that nobody — including us — altered it afterwards without breaking the signature. The session content itself is vouched for by the issuer; a consistency gate rejects any session whose verdict does not add up from its votes.