architecture-diagram

# Architecture diagram ## Contract | Field | Bound contract | |---|---| | Trigger | The user asks to visualize an architecture as a self-contained HTML artifact with a hash-bound receipt, or supplies two architecture snapshots for delta comparison. | | Authority | Reversible local: writes only the HTML artifact and JSON receipt or sidecar; rollback is deleting those files. No remote mutation. | | Side effect | One HTML artifact and one JSON receipt or sidecar written to disk. | | Done | Single: frozen schema-validated specification, self-contained interactive HTML artifact, and evidence receipt with all render checks passing. Delta: every comparable element classified into exactly one category, self-contained Before/Delta/After HTML artifact, and sidecar receipt written. | ## Mode Two render modes, discriminated by input count: - Single (default): one architecture question or scope → schema-validated specification + interactive HTML artifact + evidence receipt. - Delta: two already-authored architecture snapshots → classify every comparable element as added, removed, changed, or unchanged; render a Before/Delta/After HTML artifact + machine-readable sidecar receipt. Pick delta when the user supplies both a before and an after snapshot and asks what changed. Otherwise single. ## Refusals - No remote, credential, publish, deploy, or irreversible mutation in either mode. - No risk assessment, blast-radius estimate, runtime causality claim, or merge recommendation in delt...