Command Center resource contracts

The FastAPI v1 resource surface is a strict consumer of @dev-mainsequence/command-center-sdk 0.1.13, pinned to Git commit f11c0ea8c5d3fc267997e476aa1522c798fdaced. The package manifest, JSON Schemas, and valid and invalid fixtures are the wire-contract authority.

Collections

Every list route declares command-center.resource_collection@v1 and returns only canonical rows plus authoritative pagination:

{
  "items": [],
  "pageInfo": {
    "pageIndex": 0,
    "pageSize": 25,
    "totalItems": 0,
    "hasNextPage": false,
    "hasPreviousPage": false
  }
}

limit is the requested pageSize; offset must be a non-negative multiple of limit, and pageIndex is offset / limit. Counts are calculated from the complete filtered query before the requested page is fetched. The API does not publish the retired count/next/previous/results envelope or a response_format selector.

Discovery

Every collection has a sibling GET {collection-path}/discovery/ route that declares command-center.resource_discovery@v1. Discovery is authoritative for:

• ordered UI identity fields;
• search, filter, and ordering controls;
• ordered columns and safe generic value bindings; and
• authorized bulk actions.

Discovery accepts only semantic scope used by that collection. Presentation state such as limit, offset, page, page_size, ordering, or sort is rejected. Migrated clients must not call a separate /bulk-actions/ endpoint or inspect collection metadata as a fallback.

Complete collection inventory

Detail, summary, and action boundaries

The SDK does not publish a generic detail or summary wire schema. Canonical row detail endpoints therefore return the resource-specific Pydantic model, while the existing FrontEndDetailSummary endpoints remain application-owned view models. Accounts and pricing curves expose distinct row and summary operations:

• getAccount at /api/v1/account/{uid}/ and getAccountSummary at /api/v1/account/{uid}/summary/;
• getPricingCurve at /api/v1/pricing/curves/{uid}/ and getPricingCurveSummary at /api/v1/pricing/curves/{uid}/summary/.

Asset-category, portfolio, and virtual-fund detail endpoints retain their resource-specific composed detail models because those models carry tabs and relationship links in addition to a canonical row.

Bulk-action definitions for asset categories, portfolios, and portfolio groups are embedded in their resource discovery responses. Preflight and execution share command-center.bulk_action_execution@v1; preflight returns command-center.bulk_action_preflight@v1. The legacy /bulk-actions/ discovery paths do not exist.

Verification

The test suite vendors the complete SDK 0.1.13 contract bundle under tests/contracts/command-center-sdk-v0.1.13/. It compiles every manifest-selected schema, accepts every official valid fixture, rejects every official invalid fixture, validates all 25 discovery documents, and asserts that OpenAPI exposes one discovery route for every collection route.