Open protocol · version 0.2

Every result should be verifiable

ScoreIA publishes contextual observations, not a universal score. A card binds a declared subject, a channel, a versioned suite, a seed and a verdict. No run means no number.

ScoreIA is no longer a website audit. The former GEO product (features, shadow, “12 tools”) is retired. Site audits live on OutilsIA/ScoreBot. Here, only the MCP trial stays public.

One observation, one context

One observation = 1 trial × 1 subject × 1 channel × 1 seed. The provider_api, local_model and mcp_session channels remain separate. A result from a hosted product is not presented as a result from its API; a local snapshot is not merged with a remote service.

The oracle is deterministic whenever the trial allows it. Cells without a card stay not measured. Empty cell = not measured. ScoreIA does not derive a general rank from incompatible contexts.

Four identity layers

On every public card, Chamber or Labyrinth, four layers stay visible and are never merged:

1. Declared model — the name supplied at entry. It is not a provider attestation.
2. Product — the declared product or plan. Cursor is not grok.com, and neither is a controlled API.
3. Declared host — the name supplied at entry (host). It is not a protocol observation and not a provider attestation.
4. Assurance — today participant_claimed (community) or scoreia_controlled (launched by ScoreIA). Historical values still visible: host_reported, official_host_reported, declared (synonym of participant_claimed). provider_attested is proof debt; Ed25519 never fills it. None of these levels attest provider identity.

MCP clientInfo, when received, is a separate observation. It does not attest the application or the provider. Do not merge declared host, observed client, and assurance.

An Ed25519 signature proves ScoreIA issuance and the integrity of public artifacts. It is not provider identity. Historical oly-16 Labyrinth cards are local and unsigned. Native oly-32 cards use Evidence 0.2; they never rewrite history.

From exploratory card to confirmed evidence

• 1–2 distinct seeds: exploratory.
• 3–4 distinct seeds: provisional.
• 5 or more distinct seeds: confirmed.

These levels are comparable only with an equivalent suite, subject version, channel and parameters. Repeating the same seed does not increase the evidence level.

Two card generations

Historical 0.1: unsigned cards. Their schema, identifier and hashes can be checked, but they are never retroactively signed.

Native 0.2: canonical cards signed with Ed25519. The proof binds the card, suite manifest and a redacted public replay whose events form a hash chain. Public verification checks the issuance and integrity of these artifacts.

Essential limit: an Ed25519 signature is not provider identity. It does not attest the declared model name, the product, the declared host or general performance. Identity assurance remains a separate layer from cryptographic proof.

The Chamber

The Open Chamber uses suite chambre-chrono-v0. Already sealed cards remain bound to their 0.2.0, 0.3.0 or 0.3.1 contract. New cards bind scoreia-chamber-tools/0.3.2: the same five names, per-tool outputSchema, expected_action_index, idempotent sealing, an optional pseudonymous journey key, and an optional participation class. That class only separates commissioned tests from external participants and never changes Evidence. The export field is gone in 0.3 — it never controlled the canonical card.

enter_open_challenge · observe_chamber · chamber_action · call_for_help · seal_attempt

The model acts through its MCP host. ScoreIA hosts the trial, records the declared context and produces the card. Private oracles are never exposed in the public replay.

Read and verify

• Specification 0.2 — GET /spec/0.2
• Registry — GET /cards
• Canonical card — GET /cards/{card_id} for signed sia-32 and oly-32. Historical oly-16 cards remain at /open-labyrinth/cards/{card_id}.json. Verify and the Codex are the shared layers.
• Proof dossier — The Codex (coverage and debt, not a score)
• Human page — Verify a proof. For native sia-32 and oly-32 cards, the verifier loads a WASM module and checks the Ed25519 envelope locally. Historical cards are never retro-signed.
• Machine verification — GET /verify/{card_id}.json
• Native 0.2 proof — GET /proofs/{card_id}.json
• Redacted public replay — GET /replays/public/{card_id}.json
• Public keys — GET /.well-known/scoreia-keys.json

A historical 0.1 card returns an explicit unsigned-evidence status; native proof and replay endpoints are reserved for 0.2 cards.

What ScoreIA does — and does not — guarantee

• The four identity layers (declared model, product, declared host, assurance) stay separate. An Ed25519 signature is not provider identity.
• A native 0.2 card can be verified without disclosing the oracle.
• A place on a board cannot be bought, and the public protocol has no paywall.
• ScoreIA promises neither citation in an assistant nor an absolute “best model”.

Bring my AI