Export Review Process

Summary

The public export review process is the gate between internal engineering knowledge and external publication. A page is published only after its audience, links, evidence, and visuals have been reviewed for external readers.

Reader Question

What has to be true before an internal engineering page can appear in the public static export?

Surface Or Workflow

The review surface is metadata and static build behavior. Public export is a projection of reviewed pages, not a separate authoring tree.

Lifecycle

An internal page is selected as a publication candidate. The author removes private details, checks links and visuals, confirms the external-reader metadata, and validates the public build. The export includes only reviewed content and excludes the full internal inventory.

Child Threads

Implementation Boundaries

This page cites the public strategy, content contract, and decision record. It does not expose internal inventories, operational examples, or private paths beyond already public-reviewed content-system files.

Tradeoffs

The metadata gate slows publication, but it prevents accidental leakage and keeps public export deterministic.

Visual

The current visual is a public-reviewed graph neighborhood. The intended visual is a checklist flow from candidate page to metadata, visual review, forbidden content scan, public build, and publish decision.

Source Evidence

  • docs/public/platform-journey-strategy.md
  • docs/engineering/README.md
  • docs/engineering/threads/public-platform-journey.md
  • docs/decisions/0005-engineering-knowledge-site.md