---
slug: did-management/domain/update
version: "0.1"
title: DID Management — Domain Update
summary: An administrator updates the metadata of an existing hosting domain (label only — the `name` itself is immutable).
status: draft
targetFrameworkVersion: "0.5.0"
category: did-management
keywords: [did-hosting, domain, update, admin]
authors:
  - Glenn Gore (https://github.com/stormer78)
parties:
  - role: Administrator
    requirement: REQUIRED
    member: issuer
  - role: DID hosting service
    requirement: REQUIRED
    member: recipient
proofRequirement:
  requirement: REQUIRED
  rationale: An update is an admin action with audit value.
issuedAtRequirement:
  requirement: REQUIRED
  rationale: A domain update overwrites the domain's settings, so a replayed copy reverts them to an earlier revision without any part of the payload showing that it has.
sideEffects:
  level: mutating
  rationale: "Updates a domain's label metadata; the name itself is immutable."
subjectPath: /name
exposure:
  discloses: none
  actsAsSubject: false
errorCodes:
  - code: did-management:unknownDomain
    meaning: The submitted `name` does not match a known hosting domain. See [category conventions](../../../_shared/0.1/CONVENTIONS.md#2-unknown-domain-error).
    retryable: false
related: [did-management/domain/create]
---

## Abstract

The **Domain Update** Trust Task mutates the metadata of an existing hosting domain. The `name` is immutable — to rename a domain, create a new one and migrate slots manually. Today only `label` is mutable; future spec versions MAY add additional mutable fields.

## Status of this Document

Draft.

## Conformance

Admin caller emits `type: https://trusttasks.org/spec/did-management/domain/update/0.1` with `payload.name` and `payload.label`. The consumer updates the entry and returns the new `DomainEntry`.

## Authorization

*Stated in anticipation of [SPEC §7.3](/SPEC.md#73-specification-requirements) item 15, which binds specifications targeting framework 0.4; this one targets 0.1, where the declaration is not yet required.*

The authorization evidence this task presupposes is **administrator standing on this consumer**, established from the authenticated producer identity and the consumer's own records. Nothing in the payload conveys it.

The authorization decision is the *consumer*'s alone. This section describes the evidence the task assumes, not an obligation to authorize any particular party, and per [SPEC §7.2](/SPEC.md#72-consumer-requirements) item 10 verifying the `proof` establishes who asked, never that they may.

## Request

```json
{ "id": "du-1", "type": "https://trusttasks.org/spec/did-management/domain/update/0.1",
  "issuer": "did:key:z6MkAdmin", "recipient": "did:web:control.example.com",
  "issuedAt": "2026-06-11T09:00:00Z",
  "payload": { "name": "tenant-a.example.com", "label": "Tenant A (rebranded)" } }
```

## Response

```json
{ "id": "du-1-r", "type": "https://trusttasks.org/spec/did-management/domain/update/0.1#response",
  "threadId": "du-1", "issuer": "did:web:control.example.com", "recipient": "did:key:z6MkAdmin",
  "issuedAt": "2026-06-11T09:00:01Z",
  "payload": { "entry": { "name": "tenant-a.example.com", "label": "Tenant A (rebranded)",
    "status": "active", "defaultDomain": false, "createdAt": "2026-06-10T09:00:01Z" } } }
```

## Security & Privacy

Admin-only. Document is retained as audit evidence.
