Skip to main content

Portal Build Metadata evidence

Use this page to answer a simple question: what version of the portal am I looking at?

Commit9725f0e5236d
Full SHA9725f0e5236dc0f3f14d9a5c89d15ecd5a64dc1b
Build timestamp2026-06-18T02:31:05.632Z
Published timestamp2026-06-18T02:31:03Z
Publication trackinternal
Public URLhttps://docs.aicloud.core42.dev

Interpretation​

  • Commit is the git revision used to build this portal.
  • Build timestamp is when the Docusaurus build was generated.
  • Published timestamp is present only when the publish wrapper or CI publish job set it during the deployment build.
  • Publication track distinguishes internal/customer/public variants when the portal later splits by audience visibility.

Operational Rule​

When the portal content or deploy path changes, the build metadata must move with it. Operators should not need to infer version from deployment logs alone.

First Internal Publication Target​

The first protected internal publication target is:

docs.aicloud.core42.dev

Current operating assumptions:

  • publication track: internal
  • hosting path: Cloudflare Pages static deploy
  • protection model: Cloudflare Access one-time email passcodes
  • current coarse allowlist: @core42.ai, @g42.ai, and subahsram@gmail.com

This page is intentionally explicit about the first hostname so reviewers can tell whether the portal they are looking at matches the intended internal publication path.

Operator Prerequisites For A Real Publish​

The repo-side publish path is implemented, but a real upload still requires the external deployment runtime:

  • wrangler available in PATH
  • CLOUDFLARE_ACCOUNT_ID
  • CLOUDFLARE_PAGES_PROJECT
  • CLOUDFLARE_API_TOKEN
  • DOCS_PORTAL_HOSTNAME
  • DOCS_PORTAL_PUBLICATION_TRACK

Without those values, the repo can prove the preflight and build path, but not an actual Cloudflare Pages deployment.

Canonical sources