Skip to content

Architecture: define contract representation layers - #24

Open
sfloess wants to merge 5 commits into
mainfrom
architecture/contract-representation
Open

sfloess wants to merge 5 commits into
mainfrom
architecture/contract-representation

Conversation

@sfloess

@sfloess sfloess commented Sep 18, 2026

Copy link
Copy Markdown
Member

Summary

  • define semantic, schema, conformance, and binding layers for Loom contracts
  • establish JSON Schema as the initial machine-readable structural representation
  • explicitly position OpenAPI as an HTTP binding, not the normative contract
  • add ADR-0007 and an initial Contract schema

Why

This makes the contract representation strategy explicit before implementing loom-python. The semantic model remains transport- and language-neutral while schemas and bindings provide concrete realizations.

Closes #2 is intentionally deferred until the full normative semantic model and conformance suite are frozen; this PR establishes the representation decision needed to proceed safely.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Architecture: freeze the minimal normative semantic model and conformance contract

1 participant