# auth.md — aio-registry.ai (GreenCore Solutions Corp.)

## Posture

This directory is **open by design** — no authentication, no payment. Every page and machine file is a public read. Anything that creates obligation leaves the estate through the human-signed doors; nothing transactional lives on this surface.

## Enforcement posture — the sign (declared 2026-08-24)

These endpoints are open by design. When the buy side's credential standard reaches GA — expected Q4 2026-Q1 2027 — transactional methods migrate to OAuth 2.1 challenge per the MCP 2025-11-25 specification. Read access stays open. That is not pending work; that is the published plan.

```json
{
  "enforcement_posture": "open-by-declaration",
  "migration_standard": "OAuth 2.1 + PKCE challenge (401 + WWW-Authenticate) on mcp:transact methods, per MCP spec 2025-11-25",
  "migration_trigger": "ecosystem GA of credentialed counterparties (enterprise A2A/MCP buy-side GA)",
  "migration_window": "Q4 2026 - Q1 2027",
  "declared": "2026-08-24",
  "operator": "GreenCore Solutions Corp.",
  "duns": "24-336-6774"
}
```

## Protected resource

- Resource: https://aio-registry.ai
- Protected Resource Metadata (RFC 9728): [/.well-known/oauth-protected-resource](/.well-known/oauth-protected-resource)
- Authorization server (Microsoft Entra): https://login.microsoftonline.com/54939635-2f2e-465a-8526-a907cb3c8ebd/v2.0
- AS metadata mirror: [/.well-known/oauth-authorization-server](/.well-known/oauth-authorization-server)
- Bearer tokens are presented in the Authorization header.

## Scopes (resource scopes — not human-login scopes)

- `registry:read` — Read the GSC AIO Agent Registry directory (market pages, index, records).

## PKCE and resource indication

- Authorization-code requests use **PKCE** (`code_challenge_methods_supported`: S256).
- **RFC 8707 resource indication**: at the Microsoft Entra v2 endpoint the resource travels as the scope prefix (`scope=<resource>/.default`).
- **No token passthrough**: tokens presented to this surface are never forwarded upstream.

## Agent registration (self-contained flow)

- **Agent audience:** AI agents and operators reading the AIO Agent fleet directory.
- **Registration endpoint:** https://gsc-navigator.ai/ — the GSC Trading Desk (human-reviewed; no self-serve dynamic client registration). Intake: POST https://formspree.io/f/mppannbj with fields name, email, message — human-reviewed by the GSC Trading Desk.
- **Supported method — verified email:** GSC verifies the operator's email, then provisions credentials after review.
- **Credential use:** Microsoft Entra OAuth 2.0 client credentials; Bearer token in the Authorization header. Revocation on request via the same endpoint.

```json
{
  "agent_auth": {
    "skill": "https://aio-registry.ai/auth.md",
    "register_uri": "https://gsc-navigator.ai/",
    "identity_types_supported": [
      "identity_assertion"
    ],
    "identity_assertion": {
      "assertion_types_supported": [
        "verified_email"
      ],
      "credential_types_supported": [
        "oauth2_client_credentials"
      ]
    },
    "claim_uri": "https://gsc-navigator.ai/"
  }
}
```

Operator: GreenCore Solutions Corp. · D-U-N-S 24-336-6774 · Microsoft AI Cloud Partner.