Colorado AI Act in · EU AI Act high-risk obligations in · Editable AI governance implementation evidence for SMEs and technical teams
Version discipline

Move78 Changelog

Public record of Move78 website, methodology, and ACT product-page updates. The purpose is transparency, not certification.

Current changes

DateAssetChangeNote
2026-04-28Buyer landing pagesAddedFounder, compliance, CISO, and vCISO/consultant buyer paths.
2026-04-28Methodology pageAddedPublished evidence mapping methodology and claim-control boundaries.
2026-04-28Core commercial pagesUpdatedAdded buyer-path routing and evidence-first positioning.
2026-04-28Sitemap / llms.txt / robots.txtUpdatedAdded new public pages and AI-readable discovery files.
2026-04-28Download referencesPreservedHostinger-hosted standalone download links remain untouched by this patch.
Boundary: This changelog does not validate legal compliance, audit readiness, security effectiveness, or regulatory acceptance. It records material content and product-surface updates only.

Frequently Asked Questions (FAQs)

Why publish a public changelog?

A public changelog gives buyers a visible record of material website, product-surface, methodology, and resource updates. AI governance artifacts depend on source review and version discipline. A changelog does not prove compliance, but it helps show that the product surface is maintained rather than abandoned.

Does the changelog prove legal or audit compliance?

No. The changelog supports transparency and maintenance discipline only. It does not prove legal compliance, ISO certification, audit readiness, regulatory acceptance, safe harbor, or security effectiveness. Those outcomes depend on actual controls, evidence, legal interpretation, and independent review where required.

What types of changes are recorded?

The changelog records material changes to public pages, methodology statements, buyer pathways, product positioning, AI-readable files, and major resource updates. Minor grammar edits, styling adjustments, and non-substantive formatting changes may not be listed unless they affect buyer understanding or site reliability.

How should buyers interpret version history?

Buyers should treat version history as a trust signal, not as an assurance statement. A maintained changelog shows what changed and when. It does not confirm that a buyer’s implementation is correct, complete, lawful, or accepted by regulators, auditors, customers, or certification bodies.