Skip to content

docs(direction): re-baseline scope to homelab PaaS (K5)#155

Merged
astrojerms merged 1 commit into
mainfrom
docs/k5-homelab-paas
Jul 21, 2026
Merged

docs(direction): re-baseline scope to homelab PaaS (K5)#155
astrojerms merged 1 commit into
mainfrom
docs/k5-homelab-paas

Conversation

@astrojerms

Copy link
Copy Markdown
Owner

K5 — scope re-baseline: homelab PaaS

Records the scope decision K5 called for. openctl IS a bounded homelab PaaS. The deployment model (HelmRelease/Manifest/Platform/Kustomize) and the homelab-workloads epics crossed the original "infra, not workloads — stop at cluster-Ready" veto deliberately; this ratifies that on the record.

  • The bound: "what a home lab actually needs" (the "AWS console for homelab" target) — not a general cloud PaaS (Heroku/Cloud Foundry). The Tier-3 veto is retargeted accordingly (general cloud PaaS stays out; homelab workloads are in).
  • How it stays coherent: deployment methods are providers (methods-as-kinds), so breadth lives in the plugin ecosystem, not bespoke platform code; and the per-resource wedge (no global plan/state) still holds → PaaS-by-composition.

This is now the rule the next features check against, and it greenlights K4(b) (deployment-methods-as-providers) and G1 (expose-app) as first-class primitives rather than "bounded convenience."

Docs only — direction.md scope bullet + Tier-3 note, and the ROADMAP K5 entry.

Record the scope decision the roadmap's K5 called for: openctl IS a
bounded homelab PaaS. The deployment model (HelmRelease/Manifest/
Platform/Kustomize) and the homelab-workloads epics crossed the original
"infra, not workloads — stop at cluster-Ready" veto deliberately; this
ratifies that.

The bound is "what a home lab actually needs" (the "AWS console for
homelab" target), NOT a general cloud PaaS. Deployment methods are
providers (methods-as-kinds), so breadth lives in the plugin ecosystem
rather than bespoke platform code, and the per-resource wedge (no global
plan/state) still holds — PaaS-by-composition.

Rewrites the direction.md scope bullet and retargets the Tier-3 veto to
"general cloud PaaS" (still out) rather than all workloads. This is the
rule the next features check against, and it greenlights K4(b)
(deployment-methods-as-providers) and G1 as first-class.
@astrojerms
astrojerms merged commit ee4c986 into main Jul 21, 2026
6 checks passed
@astrojerms
astrojerms deleted the docs/k5-homelab-paas branch July 21, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant