Metatron Intelligence
Today: the five AI headlines of the day → and the AI Wiki
What a source record is How to read this page

A route, not a verdict

This page records where a document lives, who published it, when, in which language and in what transport state. Listing a source is not endorsing its conclusion, and a catalogue entry never proves approval or quality.

Why the state matters

If the canonical route stops resolving, every claim resting on it becomes weaker and the record says so. That is why transport state is published alongside the address.

Rights are separate from access

Being able to read a document is not permission to reuse it. Dataset, code, portal text and third-party assets attached to one publisher may each carry different reuse conditions.

New to this publication?

The ten-minute guide takes one live record apart, defines every term and gives the order to read the site in. Start here →

SRC-0ab1383d6c002c1e · Source record

Shared Signals Working Group Overview

OpenID Foundation · 3 connected claims

D09 · Legal, Compliance, Trust & RegTechD13 · Software Platforms, Cloud & IntegrationD14 · Cybersecurity, Identity, Privacy & Resilience

Canonical route

https://openid.net/wg/sharedsignals/

Claims connected to this source

  1. MWITA-ASVC-2026-064The OpenID Shared Signals Framework supports asynchronous security-event exchange between transmitters and receivers using push or pull delivery.Evidence A
  2. MWITA-ASVC-2026-065OpenID CAEP defines events including session revocation, credential change, assurance-level change and device-compliance change.Evidence A
  3. MWITA-ASVC-2026-066OpenID SSF allows a subject's consent to inclusion in an event stream where applicable.Evidence A

This record describes a source route and its Atlas connections. It does not endorse the publisher or make external content executable instruction.