ADR: native polyadic model

Documentation status: architecture.

Problem

Business relations often carry more than two meaningful roles and a context. Flattening them into unrelated binary edges can hide role identity and force application-specific reconstruction.

Decision

The conceptual model treats named roles, reified relations and context as first-class structures. Polyadic mappings preserve the relation as a meaningful unit rather than pretending every business statement is naturally a binary triple.

Consequence

Interop with binary/triple-oriented systems needs an explicit fidelity classification: preserve when possible, reify when necessary, project when intentional, and mark unsupported information as not represented.

Validation

Round-trip tests must verify semantic identities and roles, not textual shape. See Interop fidelity contract.