Skip to content

epic(cluster): first workload - the ID app #1092

Open

Description

@dezren39

First workload - the id app

Purpose

The cluster runs something real: the ID app, deployed by FluxCD.

Scope

Deploy the ID app (pkgs/id) via FluxCD against the platform services (Postgres, object storage) from epic 8; environment config fully in git; a redeploy-from-scratch proof on the cluster.

Execution mode

Online.

Dependencies

Depends on epics 7 and 8.

Acceptance

ID app live on the cluster from committed config; scratch redeploy proven; runbook notes filed.

Structure

Part of the basement cluster program. Project home: planning/roadmaps/basement-cluster.md in this repo. Full program register: goal workspace files/idea-register-2026-10-20.md (Muse goal goal_ba17a5777c21). Detailed task issues are filed as sub-issues of this epic; dependencies use blocks / blocked-by links.

Hard rules for the whole program: no HashiCorp anything; everything bootstrappable from config, no hand-built state.

Activity

  1. added
    area/infraInfrastructure, deployment, and operations
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    epicMeta-issue grouping multiple items (org Project Type=Epic)
    effort/mMedium: expected under 1 day of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    mode/onlineFully doable remotely: design, config, code, cloud
    on Oct 27, 2026
  4. dezren39 commented on Oct 27, 2026

    @dezren39
    MemberAuthor

    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: #1092 — First workload: ID app
    Dependencies: Blocked by #1087, #1088

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

  5. added
    queue/queuedHas a queued task in the Supabase agent queue
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  6. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    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

  7. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  8. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: picked up
    task 7632 (triage, lane code-c, execution lane direct) claimed 2026-11-03T12:53Z. Revalidating epic #1092 against fresh GitHub state and current main; findings note follows in this task.

  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: triaged — blocked on dependency epics
    task 7632 triage verdict (2026-11-03, fresh checks): STILL LIVE, not handled, not superseded.

    Blockers (formal blocked-by links, both verified OPEN today):

    Evidence at current main:

    • pkgs/id exists on main (Cargo.toml, ARCHITECTURE.md, .opencode/) — the workload itself is present; only the cluster target is missing.
    • planning/roadmaps/basement-cluster.md exists on main (program home).
    • No sub-issues are filed under epic(cluster): first workload - the ID app #1092 yet, despite the epic body promising detailed task issues as sub-issues.

    Fix path once #1087 and #1088 land (file as sub-issues of #1092 at that point, not before — they cannot be worked earlier):

    1. FluxCD application definition for pkgs/id against platform Postgres + object storage, environment config fully in git.
    2. Redeploy-from-scratch proof on the cluster.
    3. Runbook notes filed.
      Until then this epic stays open and blocked; the coverage join will re-queue work when the blockers clear.
  10. added
    status/blockedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)area/infraInfrastructure, deployment, and operationseffort/mMedium: expected under 1 day of workepicMeta-issue grouping multiple items (org Project Type=Epic)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmode/onlineFully doable remotely: design, config, code, cloudsource/creatorFiled by the new-issue-creator jobstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions