helexa/helexa
1
0
Fork 0
Code Issues 47 Pull Requests Actions Packages Projects Releases Wiki Activity

cortex: operator served-usage ledger + scheduled reconciliation + no-limit infra key #58

New Issue
Open
opened 2026-06-13 15:18:44 +00:00 by grenade · 0 comments
grenade commented 2026-06-13 15:18:44 +00:00
Owner
Copy Link

Part of #47 · Stage 4 (federation / operator compensation)

Scope

  • Persist a per-request served-usage ledger (account, key, model, tokens, timestamp) — the operator's compensation receipt.
  • Scheduled reconciliation with upstream's authoritative record; surface discrepancies (operator can only claim what upstream authorized — authorize-before-serve is the anchor).
  • Operator no-limit infra key: the operator's own key bypasses budget caps (own fleet, own use) but is still metered for visibility.

Acceptance

  • Served usage is durably logged; a reconciliation run matches cortex's ledger against upstream and reports the operator's compensable total; the infra key serves without cap enforcement.

Depends on: metering, upstream client.

Part of #47 · Stage 4 (federation / operator compensation) **Scope** - Persist a per-request served-usage ledger (account, key, model, tokens, timestamp) — the operator's compensation receipt. - Scheduled reconciliation with upstream's authoritative record; surface discrepancies (operator can only claim what upstream authorized — authorize-before-serve is the anchor). - Operator **no-limit infra key**: the operator's own key bypasses budget caps (own fleet, own use) but is still metered for visibility. **Acceptance** - Served usage is durably logged; a reconciliation run matches cortex's ledger against upstream and reports the operator's compensable total; the infra key serves without cap enforcement. Depends on: metering, upstream client.
grenade added the p3-later label 2026-06-13 15:19:13 +00:00
grenade added this to the Multi-tenant governance milestone 2026-06-16 11:36:44 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
out-of-scope
Outside helexa's constraining principles: near-frontier models on consumer hardware, served transparently and predictably
 p1-now
Active pain or unblocking work — pick up first
 p2-next
Engine levers — start once P1 baselines exist
 p3-later
Dependent on earlier work, or demand-driven
No Label p3-later
Milestone
No items
No Milestone Multi-tenant governance
Projects
Clear projects
No project
Assignees
Clear assignees
grenade
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#51 cortex: per-request token metering + per-key/account spend ledger
helexa/helexa
#57 cortex: EntitlementProvider — helexa-upstream client (authorize/reserve/settle, fail-closed)
helexa/helexa
Reference: helexa/helexa#58
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?