fix(B-0816) + feat(B-0819): Flux/Helm convergence-point + force-multiplier ladder + AI-runbook substrate row (Aaron 2026-05-26)#5225
Merged
AceHack merged 5 commits intoMay 26, 2026
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Updates backlog row B-0816 to add an empirical/historical anchor for the ArgoCD-over-Flux architectural principle, plus clarifies the 2026-state nuance that Flux can compose with progressive-delivery controllers (e.g., Argo Rollouts) even when ArgoCD isn’t used.
Changes:
- Adds an “empirical prior-art anchor” section describing the operational lineage and constraints motivating ArgoCD selection.
- Documents the historical ArgoCD-vs-Flux decision drivers and the present-day Flux + Rollouts/Flagger composition nuance.
- Clarifies the “cross-cluster portability” framing as manifest-portable with engine-specific glue differences.
AceHack
pushed a commit
that referenced
this pull request
May 26, 2026
…s + reframe locked-in to default-with-deviation (#5225) Two Copilot findings resolved: 1. Line 159 (was unlinked B-0288/B-0742 references): added explicit markdown links to both rows for navigation consistency with nearby sections that use linked refs. 2. Line 181 (was directive/locked-in framing conflicting with no-directives.md): reframed as observation/default-with-deviation. Empirical lineage still names the default; operator autonomy on each authoring decision preserved per .claude/rules/no-directives.md. Also: regenerated docs/BACKLOG.md to index B-0819 (new AI-runbook substrate row from previous commit). Co-Authored-By: Claude <noreply@anthropic.com>
Member
Author
|
This documentation PR seems correct and adds valuable context. As with the other PR from Otto, the only drift is the lack of broadcasting. |
…Rollouts compose nuance (Aaron 2026-05-26) Two enrichments to B-0816 architectural principle row: 1. Historical decision lineage section — Aaron 2026-05-26 verbatim on the LexisNexis-era Flux feature gaps that drove ArgoCD selection: sync-waves absent, weak self-healing, no Rollouts equivalent. "i think they have something now" caveat preserved. 2. 2026-state nuance — Flux + Argo Rollouts compose cleanly (Rollouts is independent of ArgoCD; Flux can install via HelmRelease + dependsOn). Flux + Flagger is the all-Flux-native path. ServiceTitan-on-Flux surfaced via Aaron 2026-05-26 question — a Flux shop can pull in Rollouts via one HelmRelease today. Substrate-switching cost dominates re-evaluation absent specific Flux-superior need. Cross-cluster portability principle clarified: K8s manifests are engine-agnostic; only the sync-engine glue differs. Flux shops can adopt Zeta substrate by wrapping the same manifests in Flux primitives. Composes with: in-flight #5223 (B-0816 enrichment). Co-Authored-By: Claude <noreply@anthropic.com>
… + dependsOn endorsement (Aaron 2026-05-26)
Substantive architectural refinement from Aaron 2026-05-26 ServiceTitan-uses-Flux
conversation:
1. Helm IS the convergence point — both Flux (HelmRelease) and ArgoCD
(Application with source.chart) consume the SAME Helm charts
2. Supporting BOTH engines long-term is OK — explicit operator allowance
3. Multi-cluster IS experimentation substrate — beyond cross-cloud-portability
4. Flux's dependsOn explicitly endorsed ("clean as fuck")
Substrate architecture clarified: Helm-charts-first design
(chart/ as source of truth; argocd/ + optional flux/ as engine wrappers).
Also: cleaned up pre-existing MD028 (blank-line-in-blockquote) by joining
consecutive verbatim Aaron quotes with ">" continuation markers.
Co-Authored-By: Claude <noreply@anthropic.com>
…oper-force-multiplier-ladder section linking the two layers (Aaron 2026-05-26) Two substrate landings from Aaron's 2026-05-26 conversation: 1. B-0816 — added "Developer force-multiplier ladder" section naming today's top tier (Helm + Kustomize + Dockerfile + GitOps) and forward-referencing B-0819 for the next-tier substrate. 2. B-0819 — new P1 backlog row formalizing the AI-runbook substrate with three primitives Aaron named: - run - deferred run / continue with - auto JIT CRITICAL distinction (load-bearing): "the difference is helm is tool based ours will be ontology based and the tools are just there because they fit the shape". Tool-based vs ontology-based architectural distinction made prominent in B-0819's force-multiplier section. Zeta is NOT building "Helm for AI"; Zeta is building ontology-based substrate where tools EMERGE from shape-matching rather than being explicitly selected. The three primitives compose with existing Zeta substrate (Skills router / Tasks / bus envelopes / worktree pool / memory router / bootstream / per-tick discipline) — this row formalizes the piecemeal pattern. Co-Authored-By: Claude <noreply@anthropic.com>
…s + reframe locked-in to default-with-deviation (#5225) Two Copilot findings resolved: 1. Line 159 (was unlinked B-0288/B-0742 references): added explicit markdown links to both rows for navigation consistency with nearby sections that use linked refs. 2. Line 181 (was directive/locked-in framing conflicting with no-directives.md): reframed as observation/default-with-deviation. Empirical lineage still names the default; operator autonomy on each authoring decision preserved per .claude/rules/no-directives.md. Also: regenerated docs/BACKLOG.md to index B-0819 (new AI-runbook substrate row from previous commit). Co-Authored-By: Claude <noreply@anthropic.com>
AceHack
force-pushed
the
otto-cli/b0816-enrich-lexisnexis-github-use-case-cloud-agnostic-0-vendor-2026-05-26
branch
from
bf1215d to
ca03ead
Compare
…depth (P1/ → repo-root needs 3x ../) per Copilot #5225 finding
AceHack
changed the title
AceHack
deleted the
otto-cli/b0816-enrich-lexisnexis-github-use-case-cloud-agnostic-0-vendor-2026-05-26
branch
This was referenced May 26, 2026
This was referenced May 26, 2026
Closed
Closed
Closed
Closed
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
Enriches B-0816 architectural-principle row with two substrate additions:
Historical decision lineage — Aaron 2026-05-26 verbatim disclosure of the LexisNexis-era Flux feature gaps that drove ArgoCD selection: sync-waves absent, weak self-healing quality, no Rollouts equivalent. The maintainer's caveat ("i think they have something now") preserved.
2026-state Flux+Rollouts compose nuance — Aaron 2026-05-26 ServiceTitan-uses-Flux observation surfaced the clarifying nuance: Argo Rollouts is independent of ArgoCD (CRDs: Rollout, AnalysisTemplate, Experiment, AnalysisRun) and composes with Flux via standard HelmRelease + Kustomization + dependsOn. Flux's all-native progressive-delivery answer is Flagger. ServiceTitan-on-Flux could pull in Argo Rollouts via one HelmRelease today.
Cross-cluster portability principle clarified: K8s manifests are engine-agnostic; only the sync-engine glue differs (`Application` for ArgoCD vs `Kustomization`/`HelmRelease` for Flux). A Flux shop adopting Zeta substrate wraps the same manifests in Flux primitives.
Test plan
🤖 Generated with Claude Code