Existing histories remain separate from field-history capture

Context

Existing histories serve delivery and editorial recovery. The module has no observed implementation of generalized field-history capture.

Decision

Website changes retain transition histories and content retains versions; the examined site, template and release records have no field-level history integration.

Alternatives Considered

• Adopt the platform record-history capture: No examined Websites milestone requires adopting that history mechanism.

Consequences

• Site detail changes retain last-modified metadata without a complete field-change trail.
• Template versions and their website changes provide the template’s delivery history.