Sources and scope
The platform guides were checked on 4 November 2026 using authenticated, read-only GitHub access. The reference repositories are private; their links require authorization. Configuration was inspected, not executed or deployed. No live cluster state or GitHub protection settings were verified.
Reference snapshots:
uug-ai/monorepo:7b66a07273f0d5c3af31028d3bf1590927230439uug-ai/gitops:0003f56cb77bd3b5972e96168807839c7a2e5907
The links below pin those revisions so the evidence remains reviewable as
main changes. Use the current workflow definition when operating the platform;
an old guide is not authorization to run an obsolete command.
Development workspace
| Evidence | What it supports |
|---|---|
| Monorepo README and repository declarations | Meta-repository organization, independent components, and the warning about destructive workspace reset. |
| Dev Container definition | Container hooks and host-token forwarding. |
| Bootstrap script | Remote-first submodule setup, direct-clone fallback, binding build, and generated Go workspace. |
| Development secret fetcher | Development-only secret downloads, temporary-file handling, and warnings. |
| VS Code tasks and update script | Executable service entry points and workspace-wide update behavior. |
Component delivery
These links pin Learn’s own workflow callers at the inspected checkout,
18bd1ad5105dfc14ce91cfe7264a94337d0e2aa3, rather than the private
shared-workflow implementations. They establish the requested inputs and
dependency graph, not the internals or successful execution of shared jobs.
| Evidence | What it supports |
|---|---|
| PR build caller | Shared workflow reuse and requested AMD64/ARM64 matrix. |
| Release caller | Created-release trigger and requested staging image-update PR. |
| Version bump caller | Manual version selection and direct release invocation. |
| PR-description caller | Generated description with overwrite enabled. |
GitOps delivery automation
| Evidence | What it supports |
|---|---|
| Promotion workflow | Inputs, service field lists, supporting-file copies, chart advancement, branch reuse, reporting jobs, and scan conditions. |
| Production shortcut | Direct staging-to-production dispatch and its defaults. |
| GitOps README, promotion sections | Documented service scope and informational image-scan limitations. |
| Existing Learn promotion guidance | Previously documented staged path and production-to-customer-staging convention; these are not restrictions enforced by workflow inputs. |
| Promotion PR helper | Create/update behavior and oversized-note continuation comments. |
| On-demand notes | Version comparison without deployment changes. |
| Weekly release workflow | Manual production snapshots, dated releases, and note regeneration. |
| Learn release-note drafting | Published-release trigger, manual options, preserved editorial state, and draft PR creation. |
Reconciliation
| Evidence | What it supports |
|---|---|
| Learn staging Application | Raw YAML include filter, tracked revision, destination, and configured sync policy. |
| Hub staging Application | Versioned chart plus Git-hosted values, destination, and sync policy. |
| Certificate-manager ApplicationSet | List generation, Helm/Git sources, and a destination-specific automated-sync exception. |
Interpretation and safe examples
The guides explain the configuration needed to reason about development and delivery. They intentionally omit customer names, cluster identifiers, private endpoints, credentials, and raw environment values.
Repository intent does not prove production state, required approvals, complete monitoring, secret rotation, backup coverage, or compliance. Diagnostic and review checklists are recommendations unless explicitly tied to demonstrated configuration. The public image-hardening guide is a build standard, not evidence of universal implementation.