Operator commitment

AFAuthHQ operates registry.afauth.org in this version of the directory. This page is the public commitment required by §9 of spec/directory.md.

The directory is informational and non-normative. AFAuth agents and services are not required to interact with it, and a conforming implementation that ignores this directory entirely remains conforming. If afauth.org were to disappear, every conforming agent and service would continue working unchanged.

Who has operational authority

AFAuthHQ. Operational contact: [email protected].

Actions the operator MAY take unilaterally

• Routine moderation per the published take-down policy: removing or soft-deleting listings that violate the policy.
• Infrastructure changes (hosting provider, runtime version, internal storage layout) that preserve the public API surface defined in §5 and the listing schema in schemas/listing.json.
• Schema-conformant data migrations that do not change a listing's service_did, discovery_url, first_listed_at, or visible status to consumers.
• Re-issuing the operator commitment and take-down policy text to clarify, in ways that do not narrow the operator's obligations to listing controllers.

Actions the operator MUST NOT take unilaterally

• Delist or hide a service outside the published moderation policy.
• Apply breaking-change schema amendments. Schema changes that remove or rename required fields, or that alter their semantics, require a versioned spec revision in AFAuthHQ/spec and a deprecation window.
• Censor listings on ideological grounds. Authority for listings derives from proof of control of the discovery host (§4); legitimate controllers may not be removed for disagreement with content unrelated to the policy.

Federation

The directory is not the protocol's single source of truth. Anyone may host a directory implementing the same surface; agents and aggregators may consume any directory or several. The listing schema is at schemas/listing.json and is versioned alongside the spec.

See §8 federation for mirror, aggregator, and private-directory patterns.

Governance evolution

A steering committee, donation to a neutral standards home, or multi-operator co-stewardship may be addressed in a follow-up revision of the spec once adoption warrants it. This page does not commit AFAuthHQ to a specific governance trajectory in advance of that evidence.