docs: raise console documentation to hyperscaler standard - #800
Merged
Conversation
jason931225
commented
Aug 18, 2026
jason931225
left a comment
Collaborator
Author
There was a problem hiding this comment.
Bars pass at 58e8923.
- Existing owner files only. The extra
docs/program/ci-gates-historical-narrative.mdpath is deleted and unseeded. Live inventory stays indocs/CI-GATES.md. - After edit: CI-GATES.md 78, DESIGN-DOCTRINE 12, PLATFORM-ROADMAP 45, DELIVERY 45, HANDOFF 16, DESIGN/SPEC tombstones 7. Manifests are existing inventory tables (unseed only).
- One capability (raise console docs to one live source of truth)
- No leftover new-path
oya-name; net −1200 docs dump - No new required check or N+1 workflow
Not APPROVE. Hold until required CI is green.
jason931225
commented
Aug 18, 2026
jason931225
left a comment
Collaborator
Author
There was a problem hiding this comment.
Bars pass at c27eca2 (rebased onto post-#796 main / eee8107).
- Existing owner files only. Extra
docs/program/ci-gates-historical-narrative.mdstill deleted and unseeded. Live inventory stays indocs/CI-GATES.md(78). - After edit: DESIGN-DOCTRINE 12, PLATFORM-ROADMAP 45, DELIVERY 45, HANDOFF 16, DESIGN/SPEC tombstones 7. No new top-level
docs/*.md. - One capability (one live docs source of truth)
- No leftover new-path name; net shrink vs base
- No new required check. Merge from
mainonly absorbs #796 unused-gate deletions.
Not APPROVE. Hold until required CI is green.
jason931225
force-pushed
the
docs/hyperscaler-standard-2
branch
from
August 18, 2026 12:16
c27eca2 to
15e3590
Compare
jason931225
commented
Aug 18, 2026
jason931225
left a comment
Collaborator
Author
There was a problem hiding this comment.
PASS at 15e3590 (rebased onto current main 8b17bb9). Docs-only. Extra docs/program/ci-gates-historical-narrative.md still gone and unseeded. Live inventory stays in docs/CI-GATES.md (~78). Existing paths only; no new top-level docs/*.md; no new required check.
Bars checked: existing file, size, no third path, recorded shrink of the essay into history, docs-only. Inherited/old pin is not this PR. Not APPROVE.
Drop the new docs/program/ci-gates-historical-narrative.md path. Live inventory stays here; the 69KB per-gate essay remains in git history at main:docs/CI-GATES.md.
`check:doc-manifest` and `check:doc-links` bind each entry to the exact Git index-tree blob OID, not to file content, so both went red after the rebase: docs/documentation-manifest.seed.json: docs/CI-GATES.md blob_sha does not match the exact Git index-tree blob OID Regenerated AFTER staging. Regenerating before staging computes OIDs the index does not hold yet, passes locally, and fails in CI -- the same order-of-operations that broke #807. Verified: check:doc-manifest -> OK (457 files); check:doc-links -> OK (457); check:doc-citations -> exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jason931225
force-pushed
the
docs/hyperscaler-standard-2
branch
from
August 19, 2026 03:06
15e3590 to
746ee3b
Compare
jason931225
enabled auto-merge
August 19, 2026 03:06
…ropped `check:production-hardening` requires docs/CI-GATES.md to contain the exact string CONSOLE_NETWORKPOLICY_PREFLIGHT=require npm run check:k8s:networkpolicy Main carries it twice; the restructured inventory carried it zero times, so the gate failed with "CI gates document required NetworkPolicy enforcement preflight". That surfaced as a red "Trivy — IaC / manifest misconfig" job, which is misleading: Trivy reported 0 misconfigurations across every target, and the job died on the production-hardening step that runs after the render. This is the gate working. `check:k8s` only RENDERS manifests and CI merely warns when no live cluster is reachable; enforcement of the rendered NetworkPolicy is a separate opt-in preflight. A deployment checklist that omits it reads as though rendering were sufficient, which is why the string is pinned rather than left to prose. Restored as its own "Deployment gates" section rather than smuggled into a list, and it says why the line is pinned so the next restructure does not drop it again. Documentation manifest and index regenerated AFTER staging. Verified: node scripts/check-production-hardening.mjs -> passed (239 checks); check:doc-manifest -> OK (457); check:doc-links -> OK (457); check:doc-citations -> exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raise first-party docs to a hyperscaler reading standard: one live source of truth, current vs historical labeled, short pages, no aspirations as shipped. Docs-only. Does not fight open PR 796.
Verified 2026-08-17 findings against
mainat7705578eand fixed what was still true:README.mdanddocs/current/DELIVERY.mdnow share one new-clone sequence (npm ci, install DotSlash, exportPATH,npm run verify). A clone without DotSlash onPATHfails Buck2-backed steps as environment errors.docs/current/PRODUCT.mdso existing links resolve. They do not revive as architecture or spec authority.docs/current/*only..omx/plans/reasoning-lens-contract-execution-handoff.jsonis explicitly not live authority.package.json/.github/workflows/ci.yml. Inventory lists remain the machine-checked contract forcheck:foundation-gates.docs/CI-GATES.md(~4KB). Historical per-gate prose moved todocs/program/ci-gates-historical-narrative.md(not a new top-leveldocs/*.md).docs/current/ROADMAP.md.docs/*.md.Honest ADR-0020 note
ADR-0020Verification namescheck:korean-institutional-connectivity. The script exists inpackage.json. No workflow invokes it. Open PR 796 records the same fact and leaves the script in place pending an ADR amendment. This PR does not delete or rewire that gate.console-gate-vendor-lockinexists in-tree and is not in the CI-run inventory.Test plan
npm run check:doc-manifest— OK (458 markdown files)npm run check:doc-links— OK (458 markdown files)npm run check:reasoning-lens-manifest— OKgit diff --check— cleannpm run check:foundation-gatesafternpm ci(local worktree lackedjs-yaml; CI will run it)docs/CI-GATES.mdinventory headings still matchci.ymlif that workflow moved after7705578e