Skip to content

DEN-3828: couple API/MCP operation projections to admitted data-contract IR #75

Open

Description

@ORESoftware

Tie Zed operation/API projections to the same admitted data-contract evidence instead of letting OpenAPI/MCP/RPC surfaces drift independently.

Acceptance:

  • api-docs operation/API IR records the exact TJSV Contract IR irId and declaration identities it references;
  • OpenAPI, MCP manifests, Protobuf/gRPC, Connect and tRPC generation refuse missing/stale data-contract admission;
  • operation changes cannot silently widen data shapes beyond admitted declarations;
  • public vs admin/private operation scopes remain separate;
  • compile/typecheck generated clients/servers where supported;
  • negative tests cover stale IR, missing declaration, wrong scope and mismatched generated operation artifacts;
  • keep TypeSpec and authored JSON Schema as independent data authorities; operation IR remains downstream projection evidence.

Linear parent: DEN-3828. Related: DEN-165, DEN-3959.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions