[Feature]: Compliance: default workflow templates (Data Contract + Data Product Compliance)

Parent PRD

#125

What to build

Ship two built-in process workflows in default_workflows.yaml that serve as the default compliance check templates:

1. "Data Contract Compliance" workflow:

• Step 1: policy_check -- SCHEMA_DRIFT check
• Step 2: policy_check -- SLA_COMPLIANT check
• Step 3: policy_check -- ACCESS_AUDIT check
• Step 4: policy_check -- DQ_SCORE check (threshold from config, default 80%)
• Step 5: validation -- Native DSL: ASSERT HAS_TAG('owner') AND HAS_TAG('domain')
• Chained via on_pass/on_fail; overall result = all steps pass

2. "Data Product Compliance" workflow:

• Step 1: policy_check -- CONTRACT_LINKED check
• Step 2: policy_check -- Cascading contract compliance check
• Step 3: validation -- Native DSL: ASSERT obj.owners.length > 0
• Step 4: validation -- Native DSL: ASSERT obj.status IN ['active']

Wire both as system-wide defaults (entity_type=data_domain, entity_id=system) so all new contracts/products get them unless the domain overrides.

Acceptance criteria

• Both workflows defined in default_workflows.yaml with correct step types and chaining
• Workflows reference the check functions implemented in earlier slices
• Workflows registered as system-wide defaults in entity_compliance_checks on app startup
• New contracts/products receive these workflows as default bindings (via domain defaults / system fallback)

Blocked by

• Blocked by #126 (entity_compliance_checks data layer)
• Blocked by #129 (SCHEMA_DRIFT)
• Blocked by #130 (SLA_COMPLIANT)
• Blocked by #131 (ACCESS_AUDIT)
• Blocked by #132 (DQ_SCORE)
• Blocked by #133 (CONTRACT_LINKED)

User stories addressed

• User story 26

Start with default_workflows.yaml and review the entity_compliance_checks data layer plus the earlier check implementations in issues #126 and #129–#133. Define both workflows with the specified steps and chaining, then trace app startup and domain fallback registration. Done means system-wide defaults are registered and new contracts and products receive them unless overridden.