FORGE-did-web-identity

⚒️ did:web Identity — Decentralized Identifier

DITEMPA BUKAN DIBERI — Forged, Not Given.

Purpose

Implement and maintain /.well-known/did.json for federation organs under arif-fazil.com. Support did:web resolution, key management (verification methods), service endpoints, and rotation patterns.

When to Use

• Setting up did:web identity for a new federation organ subdomain
• Updating verification methods (key rotation, addition, revocation)
• Adding service endpoints (MCP, A2A, WebMCP) to the DID document
• Resolving did:web identifiers from external agents or systems

When NOT to Use

• Non-DID identity (API keys, JWTs) — use organ auth middleware
• Governance metadata — use governance-jsonld
• Federation topology — use federation-manifest

Constitutional Floor Alignment

Commands & Patterns

// /.well-known/did.json — canonical structure
{
  "@context": ["https://www.w3.org/ns/did/v1"],
  "id": "did:web:arif-fazil.com",
  "verificationMethod": [{
    "id": "did:web:arif-fazil.com#key-1",
    "type": "Ed25519VerificationKey2020",
    "controller": "did:web:arif-fazil.com",
    "publicKeyMultibase": "z6Mkr..."
  }],
  "authentication": ["did:web:arif-fazil.com#key-1"],
  "assertionMethod": ["did:web:arif-fazil.com#key-1"],
  "service": [{
    "id": "did:web:arif-fazil.com#mcp",
    "type": "McpServer",
    "serviceEndpoint": "https://arifos.arif-fazil.com/mcp"
  }]
}

# Serve did.json via Caddy
# /etc/caddy/conf.d/did.conf
well-known {
    @did path /.well-known/did.json
    handle @did {
        root * /var/arifos/did
        file_server
    }
}

Refusal Surface

• ❌ Using did:key or did:eth when did:web is the federation standard
• ❌ Hardcoding private key material in the DID document or source
• ❌ Multiple controllers per did:web — keep it single-controller
• ❌ Removing verification methods without verifying no active references