Conversation
Splits the single "final state" GitOps showcase into six isolated, self-contained tiers that each peel back one capability from tier-5 (today's main): raw manifests -> Flux GitOps -> Helm chart/platform-app split -> OCI-published app values -> SpiceDB ReBAC -> full governance and supply-chain verification. Every tier has its own kind cluster, OpenTofu stack, and README explaining what it demonstrates and what changes on the way to the next tier. Root README and new TIERS.md act as the landing page and tier index; CI workflows stay at the repo root (a GitHub Actions requirement) but are noted as relevant from a given tier onward. Also adds a status-matrix infographic (docs/) showing how developer, platform, and security friction points resolve across the tiers. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
TIERS.md and README.md covered overlapping ground now that the repo is tiered; converge on a single root README with a "Tiers" section, and repoint every cross-reference (tier READMEs, CLAUDE.md, CI workflow comments) at it. Also documents the tier-0..tier-5 restructure as a new phase in TIMELINE.md, consistent with how prior architectural decisions are recorded there. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Old tier-0 (raw manifests, hand kubectl-applied, no Flux) didn't match the real starting point in our environment, where Flux already reconciles a cluster repo and a custom deployer tool already templates manifests and commits them on merge. Collapse old tier-0 and tier-1 into a new tier-0 that reflects that baseline (Flux + deployer-tool commits, no platform/app split yet), and renumber everything else down by one (tier-2..tier-5 -> tier-1..tier-4). tier-4 is now the final, full-governance tier. Updates every cross-reference accordingly: root README's Tiers table and throughline, CLAUDE.md, the three CI workflows' hardcoded paths and "relevant from" comments, the team-conflicts infographic (6 columns -> 5, tier-0 statuses re-derived for the new baseline), and a new addendum bullet in TIMELINE.md's existing restructure entry documenting the renumbering and why. Co-Authored-By: Claude Sonnet 5 <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
1 participant
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
tier-0throughtier-5), each with its own kind cluster, OpenTofu stack, and manifests, peeling back one capability at a time fromtier-5(which matches today'smain): raw manifests → Flux GitOps → Helm chart/platform-app split → OCI-published app values → SpiceDB ReBAC → full governance and supply-chain verification.TIERS.mdandREADME.mdinto a single rootREADME.mdwith a "Tiers" section, and repoints every cross-reference (tier READMEs,CLAUDE.md, CI workflow comments) accordingly.docs/team-conflicts-infographic.html) showing how developer/platform/security friction points resolve across the tiers.TIMELINE.md, consistent with how prior architectural decisions are documented there.CLAUDE.mddocumenting the tiered layout for future agent sessions.Test plan
cd tier-0/kind-cluster && ./cluster.sh up && ./cluster.sh check && ./cluster.sh downcd tier-1/kind-cluster && ./cluster.sh up && ./cluster.sh check && ./cluster.sh downcd tier-2/kind-cluster && ./cluster.sh up && ./cluster.sh check && ./cluster.sh downcd tier-3/kind-cluster && ./cluster.sh up && ./cluster.sh check && ./cluster.sh downcd tier-4/kind-cluster && ./cluster.sh up && ./cluster.sh check && ./cluster.sh downcd tier-5/kind-cluster && ./cluster.sh up && ./cluster.sh check && ./cluster.sh down(full original showcase runbook)🤖 Generated with Claude Code