Skip to main content

Review Pack Export designed

Review packs are curated exports of the portal for teams that need to review GPUaaS without Git access. They should come from portal pages and generated artifacts, not from one-off copies.

Pack Types​

PackAudienceContents
ProductProduct, UX, product leadershipProduct strategy, user interactions, IA, competitive context, launch/runtime paths
ArchitectureArchitecture, development, infraSystem overview, shared services, domain ownership, API route model, state machines
SecurityCISO, security, architectureCurrent controls, readiness posture, gaps, terminal/session security, billing controls
OperationsOps, infra, SREProduction baseline, release operations, observability, incident workflow, node lifecycle
App developerInternal/partner app teamsBuild path, SDK overview, manifest, artifacts, API reference, playground rules

Export Rules​

  • Export from Docusaurus routes and generated artifacts.
  • Include source-doc inventory and page freshness metadata.
  • Preserve visibility labels and publication-track warnings.
  • Do not include internal-only pages in external/customer/partner packs unless explicitly reviewed.
  • Include diagrams as rendered assets or Mermaid source when useful.
  • Include API artifacts when the pack targets developers or architecture.

Packaging Flow​

First Implementation​

Start with static folder or zip exports generated from the built portal:

  1. Build the portal.
  2. Select routes by pack type.
  3. Include source-doc-inventory.json and generated API artifacts.
  4. Record export date, source SHA, included routes, owner, and visibility.
  5. Package as zip/PDF only after the route list and publication filtering rules are stable.
Canonical sources