Skip to content

feat(quota-plane): daily model + route audit — latest models incorporated, route rules cover all needs #1173

Open

Description

@dezren39

Priority P1 — order 9. Horizon: Week. Design: quota-plane-design-2026-10-26.md (usage-billing-hub goal files), Stage 2. Parent context: epic #1047. (§3)

Tracks the DAILY MODEL + ROUTE AUDIT (Drew, 2026-10-26): the daily measurements verify (a) the latest models are incorporated — deployed config/OpenChamber catalog vs each provider's current model list, missing or retired models are findings; (b) route rules handle all needs — every tier (scout/workhorse/specialist/summit) has a route on an existing, enabled, non-funds model, effort variants set per model, disabled providers absent from pools; (c) pool ordering matches burn-by-expiry + cheapest-sufficient, OpenAI final reserve — contradictions recorded, config changes via repo PR flow only.
Status: the stewardship-cycle block is LIVE (applied 2026-10-26 22:41 CDT by cron update, no read-back per Drew). This issue owns: the first audit run's findings, the provider-model-list comparison mechanics (automate what the block currently does by inspection), and filing/fixing what the audit surfaces.
Acceptance: first MODEL AUDIT entry in the stewardship cycle log with findings (or an explicit no-findings), each finding linked to its fix issue.

Acceptance criteria

  • The first MODEL AUDIT entry lands in the stewardship cycle log with findings (or an explicit no-findings), each finding linked to its fix issue.
  • The provider-model-list comparison mechanics are automated where the stewardship block currently inspects by hand: latest models incorporated, retired models flagged, every tier has a route on an existing, enabled, non-funds model, pool ordering matches burn-by-expiry + cheapest-sufficient with OpenAI as final reserve.
  • Config changes flow only via repo PRs.

Activity

  1. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  2. added
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/highImportant and time-sensitive
    effort/mMedium: expected under 1 day of work
    kind/infrastructureInfrastructure / host-portability work
    on Oct 28, 2026
  3. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    Intake review

    Fleet monitor intake enrichment (protocol §5) — 2026-10-28T06:27Z. This issue was filed 2026-10-27 by Drew (dezren39) from the 2026-10-26 live pm-stack review and had no priority/* label and no standard ## Acceptance criteria section; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).

    • Related: Parent context in body: epic epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047, quota-plane design Stage 2 (§3). Body states Priority P1 / Week horizon; the stewardship-cycle audit block is already LIVE per the body — this issue owns the first run's findings and the automation. No merged PR references this issue.
    • Labels normalized: one kind/* (added kind/infrastructure), source/human, status/needs-triage, priority/high, effort/m, app/pm-stack (existing), meta/enriched.
    • Still live: verified open this run; no merged PR or commit found that implements it.
    • Risks: An audit that files findings without fix links repeats the silent-failure pattern; every finding needs its fix issue in the same pass. Model lists change often — compare against providers' current lists at run time, not a snapshot.
    • Suggested approach: Run the first audit from the live stewardship block, file/link a fix issue per finding, then automate the model-list diff so later audits are mechanical.
  4. added
    mode/onlineFully doable remotely: design, config, code, cloud
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Nov 1, 2026
  5. 17 remaining items

  6. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    on Nov 4, 2026
  7. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: parked

    Queue task #7558 is parked for 30 minutes because the matching audit implementation is in open PR #4703.

  8. added
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 4, 2026
  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: claimed

    Queue task #7558 is claimed for triage of issue #1173.

  10. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 4, 2026
  11. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: parked

    Queue task #7558 is parked for 30 minutes because the matching audit implementation remains in Drew-authored PR #4703.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort/mMedium: expected under 1 day of workkind/infrastructureInfrastructure / host-portability workmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmeta/follow-upFollow-up spun out of earlier workmode/onlineFully doable remotely: design, config, code, cloudpriority/highImportant and time-sensitivequeue/parkedQueue task is parked (waiting on CI, time, or an event)source/humanFiled directly by a humanstatus/parkedDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions