# Illustration for an Ariesnet engagement; hand-authored; not produced by CoreModels.
# Shape of the boundary-check configuration an engagement leaves in the customer's repo.
# https://ariesnet.com/resources/governed-definition-end-to-end

# The Core Model export in force, by version. Renders are produced from this, never
# edited beside it.
model_export: ./conformance/core-model.v3.schema.json

# The shape the boundary validates a mapping against.
shex: ./conformance/core-model.v3.shex

# Refuse is the default: a request resolving to a mapping not agreed in the export
# above is refused, and the refusal is recorded.
default: refuse

# Warn is permitted only for non-binding internal use, and only for mappings listed
# here. Empty means no mapping is exempt from refuse.
warn_allowlist: []

# The person who signs this file. Not a vendor default, not set by a merge.
control_owner:
  name: <named control owner>
  role: <role, e.g. Head of Data Governance>

# Fields every refuse or warn record carries.
record:
  - mapping_approver_and_date
  - freeze_record_timestamp_and_mapping_id
  - checked_by
  - timestamp_utc
  - core_model_project_schema_version
  - element_version_in_force
  - shex_shape_and_failed_mapping
  - answer_refused_or_warned

# Where records are written. Retention is the period set in the engagement letter.
log:
  destination: <customer audit log sink>
