Activity

1. dezren39

   added

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   area/k8sKubernetes manifests and workloadsKubernetes manifests and workloads

   on Oct 27, 2026
2. developing-today commented on Oct 27, 2026

   

   developing-todayBot

   on Oct 27, 2026 – with developing.today

   Contributor

   More actions

   CODE-229
3. dezren39

   added

   epicMeta-issue grouping multiple items (org Project Type=Epic)Meta-issue grouping multiple items (org Project Type=Epic)

   effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-ins

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   mode/onlineFully doable remotely: design, config, code, cloudFully doable remotely: design, config, code, cloud

   on Oct 27, 2026
4. github-actions

   assigned

   dezren39

   on Oct 27, 2026
5. dezren39 commented on Oct 27, 2026

   

   dezren39

   on Oct 27, 2026

   MemberAuthor

   More actions

   Epic map — basement cluster program

   #	Epic	Issue
   1	Hardware inventory & first-node selection	#1080
   2	Firmware / BIOS / BMC audit	#1081
   3	Basement power & space	#1083
   4	Network fabric	#1084
   5	Storage assembly & validation	#1085
   6	TALM + Talos bootstrap	#1086
   7	Cozystack platform	#1087
   8	Platform services	#1088
   9	Observability, backup & recovery	#1090
   10	Cloud extension (OCI & egress)	#1091
   11	First workload: ID app	#1092
   12	ESP32 wing	#1093

   This epic: #1088 — Platform services
   Dependencies: Blocked by #1087 (+ #1085 storage); gates #1090, #1092

   Filed in the 2026-10-26 cluster seed. Project home: planning/roadmaps/basement-cluster.md.
6. dezren39

   added a commit that references this issue on Oct 27, 2026

   docs(basement-cluster): link filed epic issues in roadmap

   ...

   914043d
7. dezren39

   marked this as blocked by 2 issues on Nov 1, 2026

   • epic(cluster): storage assembly & design validation #1085
   • epic(cluster): Cozystack platform #1087
8. dezren39

   marked this as blocking 2 issues on Nov 1, 2026

   • epic(cluster): observability, backup & recovery #1090
   • epic(cluster): first workload - the ID app #1092
9. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator job

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 3, 2026
10. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/none). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03
11. dezren39

    added

    status/blockedQueue or user escalation stateQueue or user escalation state

    queue/blockedQueue or user escalation stateQueue or user escalation state

    and removed

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    on Nov 3, 2026
12. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    Queue note (triaged, task 7638): verdict — still live as an epic, and not startable. It is blocked by the entire front half of the basement-cluster program. No sub-issues exist yet, so there is nothing to claim here.

    Where it sits (from planning/roadmaps/basement-cluster.md)

    Platform services is in the roadmap's Later / proposed bucket, behind every bucket before it:

    Stage	Epics	State
    Now	#1080 hardware inventory · #1081 firmware/BIOS/BMC · #1083 power & space	all OPEN, planned
    Next	#1084 network fabric · #1085 storage assembly · #1086 TALM/Talos bootstrap · #1091 cloud extension	all OPEN, planned
    Later	#1087 Cozystack platform → #1088 platform services (this issue) · #1090 observability · #1092 ID app	all OPEN, proposed

    The issue body's "depends on epic 7 (and epic 5 for storage-backed services)" maps by content to the storage epic (#1085) and to the bootstrap/Cozystack pair; in every reading the immediate gate is #1087 Cozystack, which itself needs #1080–#1086 to land first. Nothing in this epic can be deployed before there is a cluster to deploy onto.

    Two concrete gaps this triage found

    1. No sub-issues exist. The epic's Structure section says "Detailed task issues are filed as sub-issues of this epic", but subIssues is empty and no epic(cluster) child issues exist. The work below is unscoped until epic(cluster): Cozystack platform #1087 is near — filing children now would produce specs against a cluster shape that epic(cluster): network fabric #1084/epic(cluster): storage assembly & design validation #1085/epic(cluster): TALM + Talos bootstrap #1086 have not settled.
    2. The RustFS-vs-SeaweedFS decision is unrecorded. It is listed as a scope item and an acceptance criterion ("decision recorded with reasoning") but has no decision record anywhere in the repo or issues. That decision is genuinely blocked on epic(cluster): storage assembly & design validation #1085's storage validation, so it cannot be settled here either.

    Verdict

    Keep open as an epic — it is valid roadmap content, not stale. It is not a queue-workable item, and it should stop consuming triage claims: labels now say status/blocked + queue/blocked with the blocker chain above, matching how #1087-#1092 are tracked.

    Unblock condition: #1087 Cozystack deployed on a working Talos cluster (#1086) over validated storage (#1085) and fabric (#1084). At that point this epic's first real step is Postgres via CloudNativePG, followed by NATS/FluxCD/Cloudflare tunnel/Tailscale, with the RustFS decision recorded as part of it.