Skip to content

Add enterprise compute quota governance#201

Open
yyswhsccc wants to merge 5 commits into
SCIBASE-AI:mainfrom
yyswhsccc:bounty-radar/issue-19-compute-quota-governance
Open

Add enterprise compute quota governance#201
yyswhsccc wants to merge 5 commits into
SCIBASE-AI:mainfrom
yyswhsccc:bounty-radar/issue-19-compute-quota-governance

Conversation

@yyswhsccc
Copy link
Copy Markdown

@yyswhsccc yyswhsccc commented May 17, 2026

/claim #19

Summary

  • adds a distinct Enterprise Tooling slice for institutional compute and storage quota governance
  • evaluates lab/project GPU and storage forecasts into normal/warning/critical/blocked risk bands
  • produces admin dashboard metrics, approval queue decisions, CSV quota risk register exports, export manifest targets, compliance evidence, and HMAC-signed webhook events
  • adds a deterministic REST API catalog with service-token scopes for dashboard, review queue, project detail, decision, and export manifest routes
  • includes synthetic sample data plus docs/demo.svg and docs/demo.mp4 for review

Differentiation

I reviewed the existing open Issue #19 PRs (#30, #33, #69, #72, #86, #119, #127, #143, #150, #159, #161, #163, #164, #175, #176, #200, #202). Those cover broad dashboards, schema/API contracts, export pipelines, trust/compliance packets, interoperability, audit routing, webhook replay, identity drift, retention/legal hold, grant compliance, data residency, SLA monitoring, lab inventory, secret rotation, and API contract-change governance. This PR focuses specifically on compute/storage quota governance and chargeback-ready admin review workflows.

Validation

  • npm run check
  • npm test
  • npm run demo
  • git diff --check

Bounty issue: #19

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant