Start
Read CURRENT_STATE.md, SESSION_LOG.md, latest session report, top of TODO.md, and latest fleet health report. Present the likely next work before changes unless the user asks for an urgent fix.
Governance
Operating rules
These rules keep the lab recoverable and make future sessions resume from recorded state instead of rediscovering from scratch.
Safety
Non-negotiables
- Do not print secrets, kubeconfigs, kubeadmin passwords, pull secrets, PAT values, or full Secret manifests.
- Do not modify live clusters unless the user explicitly asks for remediation.
- Use read-only checks before remediation so actions are based on current state, not stale notes.
- Treat
lab-gitops-full/as platform desired state andlab-workloads/as non-platform workload desired state. - Never revert unrelated user changes in local repositories.
Session memory
Start and close routine
Close
Update CURRENT_STATE.md, TODO.md, SESSION_LOG.md, and a timestamped report after live checks, live changes, or file edits. Update assessment, runbook, or changelog when their scope changes.
Wiki upkeep
When to update this site
- Cluster role, topology, or DR semantics change.
- A platform service is added, removed, or materially remediated.
- A roadmap gate moves from blocked to passing or starts active execution.
- The Java/JBoss app architecture, Kafka dependency, or service mesh onboarding path changes.
- A session discovers a risk that a project reader should see without reading raw session logs.