Aller au contenu principal

Admission Contract Governance

Use this page when you already know the question is admission and need the exact Fabric-owned contract surfaces, template, and fail-closed review order.

Exact source surfaces​

  • POST /api/v1/tools/admission/dry-run
  • POST /api/v1/contracts/compatibility/check
  • GET /api/v1/contracts/matrix
  • GET /api/v1/contracts/docs-standard
  • GET /api/v1/contracts/admission-governance
  • GET /api/v1/identity/contracts/surface-admission

Canonical artifacts​

What is mandatory before review can go green​

  • canonical tool identity and capability class
  • repo-owned docs entrypoint plus tool-profile, integrations, capabilities, API, and OSS inventory docs
  • explicit producer and consumer declarations
  • compatibility mode and lifecycle posture
  • repo-local verify entrypoint, readiness surface refs, and live verification target
  • checklist verdicts for every mandatory review item

Why API Surface Map alone is insufficient​

API Surface Map helps a reader classify route families, but it does not carry the partner payload shape, checklist verdict grammar, or fail-closed admission order. Admission review must always return to the Fabric-owned schema, governance surfaces, and dry-run template.

Review order​

  1. Validate the completed payload against the dry-run input schema.
  2. Check compatibility posture against the compatibility-check surface.
  3. Cross-check required family usage against the producer/consumer matrix.
  4. Cross-check required docs sections against the docs standard.
  5. Execute the declared verify entrypoint and read back the readiness targets.
  6. Treat any contradiction between manifest, docs, and live surfaces as blocking drift.

Next paths​