Platform Governance & Evidence migration plan

This plan governs the future public product page. It records no private source location, protected filename, customer context, finding, risk detail, or original evidence.

Inventory decision

Field	Decision
Public inventory ID	platform-governance-evidence-public-product-page
Source class	PUBLIC_AFTER_SANITIZATION
Target owner	Lightning IT Documentation Maintainers
Canonical target	/platform-governance-evidence/
Target status	planned; implementation blocked by issue #38
Method	independent re-authoring and sanitization
Duplicate disposition	consolidate public product definition into the canonical target
Obsolete disposition	do not migrate obsolete taxonomy or unsupported claims
Redirect	none; no verified prior public stable route
Source deletion	not authorized

The associated machine-readable public inventory is stored at evidence/platform-governance-evidence-migration-inventory.json in the same immutable repository revision as this plan. Detailed source mapping and retention evidence remain protected.

Public-safe source classification

Only explicitly authorized product purpose, audience, assessment-target, scope, control, evidence-lifecycle, finding, review, bounded-deliverable, acceptance, taxonomy, and claim-boundary statements are candidates for re-authoring. Possible outputs, tools, standards, technologies, business models, prices, service levels, customer examples, private evidence, and operational detail are not implied deliverables.

The migration never exposes the private authority's location. Public provenance states only that the content was independently re-authored from an approved product authority and reviewed for information protection.

Transformation and sanitization

1. Extract only statements within the approved public scope.
2. Re-author in concise English using the product documentation standard.
3. After #38 explicitly accepts the integrated architecture, normalize product names and roles to that approved taxonomy; do not treat this migration plan as taxonomy approval.
4. Apply the ModuLix product-or-foundation role exactly as approved in #38.
5. Treat opaque historical source labels only as internal migration metadata; do not publish or expand them as product names or public acronyms.
6. Remove private links, paths, identifiers, infrastructure detail, customer context, evidence, findings, risk decisions, and unverified claims.
7. Use no example unless it uses the synthetic values permitted by AGENTS.md.
8. Scan source, history, assets, generated HTML, search index, sitemap, and deployment evidence.

Metadata normalization

The canonical page uses a stable identifier and slug, owner and accountable approver role, named audience, classification: PUBLIC, version, review date, and cadence. It begins as status: review-candidate and approval_status: pending. Creation provenance, implementation state, retention, review trigger, and change history remain traceable without naming the protected source.

Migration gates

Gate	Required evidence	Accountable role
Architecture	issues #28, #32, #36, #37, and integrated #38 approval	Documentation Maintainer
Semantic	every public statement matches approved scope and limits	Product Owner
Information protection	no protected source, data, link, asset, claim, or generated output	Security and Compliance Maintainer
Technical and accessibility	format, lint, type, content, links, build, Pagefind, WCAG, responsive checks	Documentation Maintainer
Licensing	public content and any asset have permitted provenance	Documentation Maintainer
Approval	exact document IDs and digest have role-authorized decisions	Authorized reviewer
Production	immutable revision is deployed and the concrete route is verified	Production approver

Any failed gate returns the migration to review without weakening the gate.

Rollback and retention

Before production, rollback is branch or pull-request closure. After production, rollback promotes the last accepted immutable artifact without changing DNS for an ordinary content rollback. Remove the new navigation entry and route only through a reviewed change that preserves the previous production evidence.

The protected original and source-to-output mapping remain under their approved retention policy until semantic, information-protection, licensing, approval, production, recovery-reference, and acceptance gates pass. This public plan does not authorize deletion. A later deletion requires a separate, authorized, protected record.

Completion criteria

Migration is complete only when the canonical page is merged, its exact digest is approved, the concrete route and deployed revision are production-verified, the information-protection review is recorded, and the private product authority is updated with the verified public URL. Until then, the inventory status remains planned or in review.