Creatidy/scarcity-router
5
0
Fork 0
Code Issues 13 Pull requests Projects Releases Packages Wiki Activity Actions

M1: Freeze normalized capacity contract v1 #1

New issue
Closed
opened 2026-09-02 08:57:11 +00:00 by creatidy · 0 comments
creatidy commented 2026-09-02 08:57:11 +00:00 (Migrated from github.com)
Copy link

Resolve U-002 by defining the first versioned, provider-independent normalized capacity contract for M1 provider parsers.

Scope:

  • freeze the serialized M1 snapshot, status values, quota-window semantics, percentages, timestamps, local runtime facts, safe metadata and diagnostics;
  • critically assess the Z.ai used-oriented percentage evidence without leaking provider wire concepts into the core;
  • model-check OpenAI, Z.ai, schema drift, authentication failure, Ollama local availability, and missing-versus-zero scenarios;
  • update the authoritative capacity model and resolve U-002 in the decision log.

Out of scope:

  • provider parsers or collectors;
  • CLI, REST, MCP, selector, capability, scarcity policy, caching, history or execution.

Acceptance: two independent subscription adapters can target the contract, Ollama can be represented without fake quota, unknown semantics survive normalization, timestamps are canonical, secrets/raw responses are excluded, and the change is documentation-only.

Resolve U-002 by defining the first versioned, provider-independent normalized capacity contract for M1 provider parsers. Scope: - freeze the serialized M1 snapshot, status values, quota-window semantics, percentages, timestamps, local runtime facts, safe metadata and diagnostics; - critically assess the Z.ai used-oriented percentage evidence without leaking provider wire concepts into the core; - model-check OpenAI, Z.ai, schema drift, authentication failure, Ollama local availability, and missing-versus-zero scenarios; - update the authoritative capacity model and resolve U-002 in the decision log. Out of scope: - provider parsers or collectors; - CLI, REST, MCP, selector, capability, scarcity policy, caching, history or execution. Acceptance: two independent subscription adapters can target the contract, Ollama can be represented without fake quota, unknown semantics survive normalization, timestamps are canonical, secrets/raw responses are excluded, and the change is documentation-only.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
issue-246-authorized-receipt
issue-245-mi-startup
issue-226-administrator-ux
issue-183-observer-access
issue-183-event-acceptance
issue-183-internal-events
issue-183-resource-state
issue-242-secure-bootstrap
issue-238-mi-server
issue-239-architecture-reconciliation
issue-224-certificate-lifecycle
issue-224-origin-bound-worker
issue-224-worker-ca-trust
issue-234-evidenced-resources
issue-186-installed-lifecycle
issue-186-ghcr-distribution
issue-225-cancel-paths
issue-228-backlog-disposition
issue-222-active-mi
issue-176-mi-consumer
issue-185-contract-conformance
issue-219-project-security-audit
issue-181-responses-subset
issue-214-claude-subscription
issue-205-review-result-recovery
issue-174-executable-contract
issue-215-conversational-review
issue-210-d069-review-governance
issue-212-d069a-bootstrap
issue-202-dependency-eligibility
issue-184-strict-no-payg
issue-175-kernel-requirements
issue-180-native-authority-boundary
issue-182-readable-status
issue-195-post-selection-gates
issue-179-catalog-effort
issue-178-exact-target-pin
issue-190-workflow-self-remediation
task/168-capacity-controlled-home
fix/143-scenario11-cancel-race
policy/zai-model-governance-campaign
main
No results found.
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
P1
Owner-declared highest explicit implementation priority (loop ordering rank)

  
P2
Required product and integration work

  
P3
Deferred or producer-dependent work

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Creatidy/scarcity-router#1
No description provided.