Skip to content

docs: rewrite the README opening and jargon walls for a first-time reader#2687

Merged
devantler merged 3 commits into
mainfrom
claude/docs-readme-human-readable
Jul 18, 2026
Merged

docs: rewrite the README opening and jargon walls for a first-time reader#2687
devantler merged 3 commits into
mainfrom
claude/docs-readme-human-readable

Conversation

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Daily AI Assistant

Why

The platform README is the page a stranger lands on, and it was written from memory rather than for
a reader. It never said who it is for, stacked six unexplained product names into one prerequisite
bullet, and buried the local-cluster instructions in a twelve-line paragraph with file paths
mid-sentence.

What

The opening now says what this is, who it is for, and honestly that it is a working system rather
than something packaged for reuse. The secrets prerequisite and the local-cluster instructions are
plain sentences and a scannable list. The templating section keeps both diagrams but stops
restating what docs/TEMPLATING.md already documents.

This is a readability change, not a trim — the component inventory, docs index, and cost table are
untouched, so overall length is about the same.

Docs-only: no manifests changed, so no cluster validation applies.

Fixes #2686
Part of monorepo#2225

…ader

State who the platform is for and that it is a working system rather than
a product. Break the OpenBao prerequisite and the local-cluster paragraph
into plain sentences and a scannable file list. Keep both diagrams in the
templating section but defer file-level mechanics to docs/TEMPLATING.md,
and drop the maintainer aside from the IMPORTANT callout.

Component inventory, docs index, and cost table are unchanged.

Fixes #2686
Reading the rendered page showed the Usage callout restating the same
SOPS/OpenBao/postBuild detail the Prerequisites section now explains in
plain words. The callout is only about what a fork must swap out, so it
says that and nothing else.

Also finish the prerequisite bullets left in the old terse style.
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Assistant

@codex review for documentation clarity: whether the rewritten README opening, prerequisites, and Usage section stay factually accurate about the SOPS/OpenBao secret flow and the local opt-in overlays, and whether any instruction present in the previous version was dropped.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a85cad57f4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Codex review found that plainer wording had made five claims wrong.
Verified each against the manifests before fixing:

- Flux does not watch this repo; the Kustomizations reference an
  OCIRepository, so say the manifests are published and pulled.
- OpenBao is not the runtime path for everything committed here.
  Bootstrap-critical values plus Dex/oauth2-proxy are still substituted
  into manifests by Flux postBuild; restore the "most secrets" split.
- CI does not boot a cluster. It runs workload validate and scan only,
  so "exercised the same way" overstated its coverage.
- The local overlay enables the CloudNativePG operator, not PostgreSQL.
  The apps overlay is resources: [], so no database exists locally.
- KEDA request-rate autoscaling is opt-in, not core. Only VPA is core.

The lesson is that simplifying prose can quietly drop qualifiers that
were load-bearing; each of these was a qualifier doing real work.
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Assistant

All five findings fixed in d642d97 and threads resolved — each verified against the manifests before changing the text, with the evidence in the individual replies. Re-requesting at the new head, since the previous pass was against a85cad5.

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: d642d97371

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@devantler
devantler marked this pull request as ready for review July 18, 2026 07:55
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Assistant

Readiness record. Promoting on all three conditions:

  • Validated — CI green at d642d973; docs-only, so no manifest validation applies. Hygiene clear: 0 unresolved threads, no conflict, CLEAN.
  • Reviewed — Codex clean pass, Reviewed commit: d642d97371, matching the current head.
  • Exercised as a user — rendered the README through GitHub's own render endpoint on this branch and read it end to end. That is how this change is consumed; there is no other runtime surface.

Confirmed merging this does not deploy prod: deploy-prod is gated on needs.changes.outputs.k8s == 'true' and this touches only README.md.

Codex's five findings on the first pass were all genuine accuracy regressions introduced by simplifying the prose — each verified against the manifests before fixing, with evidence in the individual thread replies.

@devantler
devantler added this pull request to the merge queue Jul 18, 2026
Merged via the queue into main with commit 7c25136 Jul 18, 2026
20 checks passed
@devantler
devantler deleted the claude/docs-readme-human-readable branch July 18, 2026 07:57
@github-project-automation github-project-automation Bot moved this from 🫴 Ready to ✅ Done in 🌊 Project Board Jul 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

docs: rewrite the README opening and jargon walls for a first-time reader

1 participant