Compliance

Every request resolves a ServiceProfile whose RoutePolicy hard-filters providers, regions, trust tier, ZDR and maximum data classification before scoring.

Principal, project, profile, policy snapshot, route plan, attempts, usage and cost are recorded on a single generation record — the join point across security, operations and finance (memo §14.1).

Routable supply is provider APIs, cloud service identities and provisioned capacity under contract. Named-user subscriptions are never converted into shared API credentials (memo §2.4, §6.4).

Admin mutations require the platform-admin principal plus a step-up assertion (X-Fabric-Step-Up); every action writes an AdministrativeAuditEvent (memo §16.6, §20.1).

Canonical models carry capabilities, context window, lifecycle (approved/testing/restricted/deprecated/blocked) and per-task-family quality scores; non-approved models are filtered out of candidacy.

The task signature derives a risk level per request; route policies cap the data class they accept and can force ZDR endpoints and Tier A/B egress for confidential traffic.

Every attempt names the provider account and the egress node that carried it; nodes carry a trust tier from enrollment and a health score from heartbeats (memo §12.4).

Golden datasets are replayed through the real pipeline into versioned scorecards; catalog quality scores change only via a rollout that reaches full (shadow → canary → full, memo §7.6).

PRE_ROUTE / PRE_MODEL / POST_MODEL / PRE_RETURN decisions (allow, flag, redact, block, require_approval, restrict_route) are attached to the generation and never bypassed by cache or fallback (memo §10.7).

Provider failures are normalized into a single FabricErrorClass union, which drives the fallback graph, circuit breakers and incident fingerprints rather than provider-specific strings (memo §9.1).

POST /v1/feedback attaches a ±1 rating and optional comment to a ledgered generation, feeding the runtime evidence layer alongside retries, JSON validity and latency.

A safety or DLP block terminates the request — it is never retried on another model — and only output-approved content is written to cache (memo §8.4, §10.7).

Per-provider / account / node circuit breakers, retry budgets and an error-conditioned fallback graph remove failing supply from candidacy; operators can open or reset a circuit and drain or quarantine a node.

Hierarchical budgets reserve estimated cost before the provider call and settle actuals afterwards; a request exceeding the profile ceiling is rejected with budget_exceeded (memo §15.2).

Evidence bundles carry the generation, its full timeline, the policy versions in force and a SHA-256 hash chain over the audit events, so any alteration breaks every subsequent link (memo §14.3.6).