cluster intake

AI Community

Skill notes

Why this skill exists

Anton has paid real tuition on loose intake — Rook-Ceph, the full LGTM observability stack, CloudNativePG, Dragonfly, TiDB, Scylla, Redpanda, and Harbor were all installed and later removed. But not every removal was a mistake. Some of those components (TiDB, Scylla, Redpanda) were honest learning experiments that served their purpose: tried it, learned it, moved on. Anton is partly a learning cluster, and "things that don't scale" are explicitly welcome when that's the point.

Three intents, three rubrics

Every intake decision starts with what is this for? The user must pick one: Intent · Example sentence · Rubric applied Concrete need · "I need this because right now I cannot ___." · Full production rubric — hard gates + sustainability + full soft score Honest learning · "I want to learn ___; I know it may be removed; my timebox is ___; my exit plan is ___." · Contained-learning rubric — blast-radius / reversibility / integration / secrets gates only + timebox + exit plan

Scope

Concern · Owner · Output Evaluate a candidate component · this skill · add / defer / reject + ADR summary Scaffold a new Flux app · add-flux-app · 3-file manifests Expose a service · expose-service · HTTPRoute + DNSEndpoint Secret store choice (SOPS vs ESO) · anton-repo-conventions · reference

Hard rules

Never scaffold files during intake. The rubric runs before any add-flux-app invocation. If intake passes, hand off explicitly. Never run mutating commands — no kubectl apply, flux reconcile, sops -e -i, git commit, helm install, gh pr merge. Never recommend adding anything already in the removal graveyard without the user stating an explicit delta: what changed about the component, what changed about the cluster's need, OR that the intent this time is declared learning (which is itself a valid delta from a prior concrete-need attempt).

Green-path: the 30-second heuristics

Apply the short-circuit filter first. If any fire, stop — do not run the full rubric, do not fill a matrix. Details → heuristics.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@wcygan · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Frame the candidate and declare intent

Restate in one paragraph, filling any gap by asking the user: What is it? Name, project URL, helm chart source. What intent? One of: Concrete need — "I need this because right now I cannot ___." Honest learning — "I want to learn ___; I know it may be removed; my timebox is ___; my exit plan is ___." All four blanks must be filled.

02
Step 2 — Check the removal graveyard (now in context/adrs/)

Before anything else, check if this component or its category is already in anton's removal history. The removal graveyard has been migrated into the ADR system: Then query the ADR index for prior `Reverted` decisions: `Glob('context/adrs/0[0-9][0-9][0-9]-*.md')` — list all ADRs For each, read the frontmatter and filter for `status: Reverted` Surface any whose `affects:` matches the candidate's category, *or* whose title clearly references the same component

03
Step 3 — Run the hard vetoes (any red = reject, no override)

Seven gates. Each is pass/fail, measured in ≤2 minutes. Full measurement procedure → rubric. Under learning intent, only gates 1–5 are evaluated (the containment gates — they protect the rest of the cluster regardless of intent). Gates 6 and 7 are replaced by the learning-specific checks described in rubric → Contained learning variant. License & exit cost — permissive OSS; uninstall is `flux suspend` + `kubectl delete ns` without orphaned finalizers or CRDs you still need. *(Applies to all intents.)*

04
Step 4 — Skim sustainability signals

Five-minute budget on the project's GitHub. Red flags do not auto-fail but flow into the soft score. Full signal list → sustainability-signals. Minimum skim: Commits in last 30 days Release in last 6 months More than one active maintainer

05
Step 5 — Fill the weighted soft score (concrete-need intent only)

Score `2` / `1` / `0` across 7 attributes, weighted. Reject if total < 22/34. Full matrix → rubric. Under learning intent, skip this step and instead fill the contained-learning checklist → rubric → Contained learning variant. The focus is containment (namespace isolation, Tier-0 non-interference, predictable blast radius), not sustainability — it's fine if the project has two stars and one maintainer, as long as the user is going into it with eyes open and a timebox.

06
Step 6 — Do-nothing tiebreaker (concrete-need intent only)

Score "do nothing" on the same matrix. If the candidate is within 4 points of do-nothing, reject — the intake tax is worth ~4 points by itself. Under learning intent, the tiebreaker does not apply. Learning has value that do-nothing doesn't — the whole point is the user wants to touch it.

07
Step 7 — Known-bad pattern check

Cross-check against well-known homelab landmines. → known-bad-patterns. Any match that is not a declared learning intake is an auto-reject. Several patterns (HA Postgres on 3 nodes, full LGTM observability, self-hosted email) have an explicit "learning-intake variant is okay if…" carve-out; read the pattern's learning note before auto-rejecting.

08
Step 8 — Return a structured recommendation, then hand off to adr

Every verdict — Add, Defer, or Reject — is recorded by handing off to the `adr` skill (`/adr new`). That skill owns the canonical anton ADR template (`.Codex/skills/adr/references/template.md`), allocates the next NNNN, and writes the ADR file under `context/adrs/`. Do not stop at "ADR-ready" — the verdict must land in `context/adrs/`. The four verdict shapes: Add (concrete need) — all 7 hard gates pass, soft score ≥22, do-nothing clear, no known-bad match. Hand off to `adr` skill with `status: Accepted`, `intent: concrete-need`. Then hand off to `add-flux-app` to scaffold manifests.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.