Why
Lentago Labs is being repositioned as a shared learning lab: a real, running estate (homelab + AWS) that a team of IT-operations professionals can explore to see modern operations patterns working end to end — everything as code, every change a PR, applies automated on merge, agents in the loop, telemetry in the open. The first colleague is aboard and more invites are pending, so the fleet's front doors — the repo READMEs and the org profile — should teach, not just describe.
What changes (every active repo)
Each README keeps its generated brand header, badge rows, and authorship disclosure, and gains three standardized blocks:
- What this repo demonstrates — the hygiene / modern-devops patterns actually practiced here, each with evidence (a workflow file, a ruleset, a terraform directory).
- Make a change yourself — the operator vectors: concrete "you edit X, open a PR, automation applies it after merge" flows, each proven with links to real merged PRs (a new dashboard via drosera, a new runner via claytonia, a new workload via solidago, a purpose-built container via kalmia, and so on per repo).
- Ask DeepWiki — the official DeepWiki badge, a short explainer of what DeepWiki is and why every public repo here is indexed, and example questions to ask this codebase.
The org profile (profile/README.md) is reframed from its consulting-practice voice to the org's actual purpose: non-critical workloads, modern-pattern demonstration, collaborating with colleagues, and sparking ideas worth adopting at work.
How
READMEs are rewritten by the claytonia fleet — one job per registered repo, one PR each, no auto-merge: every PR waits for human review. The private myosotis repo is handled by a local session.
Task list
Conventions for the PRs
- Preserve the generated brand header blocks (
brand/generate.py owns them) and the authorship disclosure at the top of each README.
- README-only scope — no workflow, settings, or CLAUDE.md changes.
- Reference this issue in the PR body (no closing keywords; this issue tracks the whole wave).
- No auto-merge on this wave — the PRs form a review queue.
Related
Companion recommendation issues (ops manual location, engagement pathways, guest readiness) will be filed and cross-linked here.
Why
Lentago Labs is being repositioned as a shared learning lab: a real, running estate (homelab + AWS) that a team of IT-operations professionals can explore to see modern operations patterns working end to end — everything as code, every change a PR, applies automated on merge, agents in the loop, telemetry in the open. The first colleague is aboard and more invites are pending, so the fleet's front doors — the repo READMEs and the org profile — should teach, not just describe.
What changes (every active repo)
Each README keeps its generated brand header, badge rows, and authorship disclosure, and gains three standardized blocks:
The org profile (
profile/README.md) is reframed from its consulting-practice voice to the org's actual purpose: non-critical workloads, modern-pattern demonstration, collaborating with colleagues, and sparking ideas worth adopting at work.How
READMEs are rewritten by the claytonia fleet — one job per registered repo, one PR each, no auto-merge: every PR waits for human review. The private
myosotisrepo is handled by a local session.Task list
.github— repo README + org profile (profile/README.md)betulabraseniaclaytoniadroserahomeassistant-configkalmiamusic-curatormyosotis(local session — private repo)reference-checkerrepo-templateshared-workflowssite-icecreamtofightwith-comsite-lentago-devsite-pondviewlane-comsolidagoConventions for the PRs
brand/generate.pyowns them) and the authorship disclosure at the top of each README.Related
Companion recommendation issues (ops manual location, engagement pathways, guest readiness) will be filed and cross-linked here.